Unity 5.4 Performance hit: Profiler FPS not agreeing with actual FPS

Upon upgrading to Unity 5.3.4 to 5.4, each of our group got a bit of a performance hit (as well as messing up the lighting again, but we’re getting used to that), but on our Macintosh in particular the Editor went from running from 30-60 fps to 7-12 fps. The status window give us these numbers, and the game certainly feels like it runs this slow.

The strange thing is the profiler still asserts that the project is running 30-60 fps!
It doesn’t have the “WaitForGFX” function that has been known to slow down the game sometimes, if you were only looking at the profiler you’d think the game was running fine.

Builds run a bit faster, but still on the slow side.

This is most noticeable on the Macintosh. It could be happening on the PC, but the fps difference isn’t enough to be as obvious (although as I mentioned we seemed to take a hit of 5-15 fps there).

Any advice or ideas on what might cause this would be appreciated!

I count 6 different issues you mentioned in this thread, so I’m not sure what the actual question is you’re asking.
But for the discrepancy with the reported FPS:
I always ignored the FPS displayed in the profiler and stats window. I don’t know how Unity determines these values, but they’ve always been incredibly misleading. Verifying about 60 FPS with numerous FPS calculation programs, the stats window reports 150 FPS. Just attach the FPS display script on the camera:
Standard Assets / Utility / FPSCounter.cs

I trust the value reported by this script. I don’t trust what is reported on the stats window or profiler.

1 Like

While the FPS in the stats and profiler might not have been always 100% accurate, it at least semi-reflected performance in previous versions. Here it just looks broken, thinking it’s running happily at 60fps instead of the 7fps we’re playing it at. Before we were at least able to use the profiler to figure out slowdown, here it seems to be coming from nowhere, which might mean it might be coming from some external element we can hopefully find and get rid of…

I’ll be posting a few other threads on issues we’ve had upgrading to 5.4 - between lighting and added draw calls, it’s been a huge setback.

Here is why I don’t even look at the FPS in the stats window:

In the top portion, I have certain gameobject selected with many custom editor fields. The editor reports about 63 FPS.
Then when I select a near-empty gameobject in the second screenshot, the editor stats reports the frame rate has gone down.
What is shown in the stats is the exact opposite of what is actually happening. The frame rate has gone up, not down.
SO the FPS shown in the stats is useless in certain circumstances.

j