Search Issue Tracker
By Design
Votes
0
Found in
5.4.0f2
Issue ID
816395
Regression
No
FPS and ms provided by statistics window doesn't match profiler's measurements
This issue has no description.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
Resolution Note:
It is not a bug.
FPS in Editor show actual frame counts in a sec.
But profiler shows accumulated time of every process in a frame.
Unity divides render process from the main thread and run it in a different thread.
Render thread is simultaneously rendering while the main thread is working.
These threads wait each other until other thread finish their work.
So time to make 1 frame is maximum between main and render Thread.
---------------------------------------------------
code.. ( GameviewGUI.cs )
m_MaxTimeAccumulator += Mathf.Max(frameTime, renderTime);
---------------------------------------------------
But profiler accumulate every process time in on one graph.
It doesn't mean exact processing time of one frame.
It is sum of every processing times in a frame.