Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Connecting to the profiler

Discussion in 'PSM' started by Issam, Apr 21, 2014.

  1. Issam


    Dec 18, 2012
    Was anyone able to connect to the profiler? I can't seem to get it working, I build the game with "development build" and "Autoconnect profiler" but nothing happen. When i try to connect to the IP address directly unity hang for a little while and than give up. My laptop is on the same wifi as the Vita, so in theory the network is fine.
  2. eriQue


    Unity Technologies

    May 25, 2010
    The PSM device should announce itself shortly after launching with 'Build&Run' - the 'Autoconnect Profiler' checkbox is not necessary for profiler to work (only when you want the profiler to start from the first frame).
    The device announces itself under the 'Active Profiler' drop-down menu in the Profiler window (Ctrl+7). It's also possible to connect manually if you know the IP address of the PS Vita device (see #3 below)

    If the device doesn't show up under the 'Active Profiler', or if the auto-connect times out, please make sure the following is correct:

    1. Make sure the host PC and the PS Vita are on the same subnet (wifi).
      The profiler uses multicast packets to announce itself, and these are only sent on the local subnet.
    2. Make sure multicast packets are allowed between wifi peers (no wifi peer isolation enabled)
      Some WIFI access points have a setting to disallow direct access between WIFI clients, as a security measure.
    3. In the PsmDeviceForUnity -get_log locate the output regarding player connection
      It should look something like:
      Multi-casting "[IP] [Port] 32457 [Flags] 3 [Guid] 1048231623 [EditorId] 4140157589 [Version] 1048832 [Id] PSM( [Debug] 0" to []...
    4. Verify that the IP address / port can be reached from host PC (e.g. "telnet <ip> <port>")
      In the example above:
      C:\>telnet 32457
      NOTE: when using telnet to test the connection the connection isn't terminated properly afterwards. This will most probably cause the VITA to hang when terminating the telnet session.

    Hope that helps.