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
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms Unite 2023 - Ask the Experts Online

Profiling webplayer not working

Discussion in 'Editor & General Support' started by perlohmann, May 8, 2014.

  1. perlohmann

    perlohmann

    Joined:
    Feb 12, 2009
    Posts:
    221
    I am having some problems profiling a webplayer I have built.
    I have followed the instructions here with regards to the build options, but I have not been able to successfully profile the running webplayer build.

    I have set the webplayer mode to be development and I have opened up both udp and tcp ports in the range 54998 to 55511 as suggested (although it does not state which protocol is used anywhere).

    The web player can connect to the profiler in the unity editor (I can select it as active profiler), but it is not showing any data.

    My last idea of what this could be is that I am using unity 4.0.1 editor while the webplayer version used according to the log file is 4.3.6f1 (4.3.5f1), but upgrading to 4.3 editor and have everything working would be a massive amount of work (mainly due to the incompatibility of the assetbundles) so I wanted to hear if anybody could chip in with ideas why it is not working or confirm my version incompatibility hypothesis.

    EDIT: Win 8.1 and chrome 34
    EDIT2: and yes I have clicked the "record" button =)

    //perlohmann
     
    Last edited: May 9, 2014
    perlohmann, May 8, 2014
    #1

  2. perlohmann

    perlohmann

    Joined:
    Feb 12, 2009
    Posts:
    221
    bump anyone?

    In other words. Does the editor version have to be the same as the webplayer version in order for it to work correctly (or are there an incompatibility point such as 4.3 with assetbundles)?
     
    Last edited: May 9, 2014
    perlohmann, May 9, 2014
    #2

  3. Graham-Dunnett

    Graham-Dunnett

    Unity Technologies

    Joined:
    Jun 2, 2009
    Posts:
    4,287
    I think if I was in your shoes I'd revert back to the exact same development web player that shipped in the editor installer. Maybe prevent the web player from auto-updating, so you know you have a solution that was known to work back in the 4.0.1 days. (Note that the docs only talk about web player profiling from 4.2, but I guess that's the docs being improved rather than the version where this feature appeared.)
     
    Graham-Dunnett, May 9, 2014
    #3

  4. luciferhaha

    luciferhaha

    Joined:
    Aug 8, 2014
    Posts:
    1
    Have you solved the problem?How?Thx!
     
    luciferhaha, Aug 8, 2014
    #4