Search Unity

  1. Unity 2019.1 beta is now available.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We're looking for insight from anyone who has experience with game testing to help us better Unity. Take our survey here. If chosen to participate you'll be entered into a sweepstake to win an Amazon gift card.
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Unity 2018.3 is now released.
    Dismiss Notice
  6. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Worst performance yet of OnGUI in 2018.2.9 build + script debugging

Discussion in 'Extensions & OnGUI' started by mgto, Nov 14, 2018.

  1. mgto

    mgto

    Joined:
    May 30, 2013
    Posts:
    21
    Hi everyone,

    I noticed that my development builds with enabled script debugging are getting an extensive performance hit. A lot more then I'm used to. The Profiler tells me it's primarily bc of OnGUI related unity code (BeginGUI() EndGUI())

    I build with .Net 4.x, IL2CPP, C++ Release

    I use OnGUI a lot for my debug GUI. An older build I did with 2018.2.6f1 does not show this behavior.

    My release builds (stripping out all OnGUI methods) are running at about 60fps , my debug builds formerly did run at about 30fps but now around 3fps.
    I didn't change anything related to the GUI nor does anything else show a significant performance drop in the Profiler.

    Is this known / does a work around exist?

    ps. currently I'm building with 2018.2.15 with the same result.

    Edit: to make it clear: as soon as I disable script debugging in the build settings the speeds are up again.
     
    Last edited: Nov 14, 2018
  2. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    3,174
    Could you file a bug report, please?