Unity profiler cannot account for drop in framerate

Bovine · May 2013

Hi There

So I was profiling an issue we have - large particle effect covering screen, alpha and additive, so expensive. In game when I step towards this effect I see the in-game FPS on our noddy in-game counter drop to ~18fps, probably fill-limited, but in the Unity Profiler there is no meaningful spike period that can explain it?

Anyone else seeing this?

Any other means of profiling?

Thanks

Ian H

Bovine · May 2013

Or maybe.... it's this StackTraceUtility I am seeing spike within the OuyaGameObject.onKeyDown() and similar methods?

Sometimes spikes of, well 10-240ms. Does't seem right but if this a side-effect of profiling it makes profiling a bit difficult :o/

Hmmm, all of these are marked:

Obsolete("No longer needed in the next version 1.0.3.13")

So.... what gives?

tgraupmann · June 2013

If you follow the ShowUnityInput example there's a faster, low-latency input approach that uses the Unity Input API.

That obsolete attribute means what it says. In a future update this old code will be gone...

Bovine · June 2013

Roger that, will take a squiz

Howdy, Stranger!

Categories

Unity profiler cannot account for drop in framerate

Comments