Search Unity

Question Standalone Build opens a TCP port for no apparent reason

Discussion in 'Windows' started by PhaneV, Jan 13, 2023.

  1. PhaneV

    PhaneV

    Joined:
    Aug 3, 2015
    Posts:
    9
    Hello.

    I'm working on a single player, full-offline game, using Unity 2021.3.11f1. We make use of no online features.

    On standalone builds (non-development, script debugging off), when I open the game I get a Windows Firewall prompt asking the user to allow the app to open a port.

    From netstat, it seems the application opens a random port (e.g. 0.0.0.0:9264)

    I would like to track down what opens that port and disable it, since it sends the wrong message to our player base and it's annoying.

    Any leads?
    Thanks!
     
    PhaneV, Jan 13, 2023
    #1

  2. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,674
    Hi,

    probably the easiest way to do it would be to attach a debugger and then set a breakpoint on the "bind" windows API to get the offending callstack.
     
    Tautvydas-Zilys, Jan 17, 2023
    #2

  3. PhaneV

    PhaneV

    Joined:
    Aug 3, 2015
    Posts:
    9
    Thank you. Found out it was FMOD Live Update, for posterity.
     
    PhaneV, Mar 8, 2023
    #3