Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2020.2.0b11
2021.1
Issue ID
1293052
Regression
No
The CPU Usage chart does not scale up to show any values higher than 66ms (15FPS)
How to reproduce:
1. Open the user's attached project
2. Open 'SampleScene'
3. Open the Profiler window (Window > Analysis > Profiler)
4. Make sure that the CPU Module is enabled (drop-down Module list in the top left of the Profiler window and check the CPU Module)
5. Enter the Play mode to capture some data
6. Observe the CPU Usage chart
Expected result: The CPU Usage chart scales up to show any frame times less than 500ms (2FPS)
Actual result: The CPU Usage chart does not scale up to show any values higher than 66ms (15FPS)
Reproducible with: 2018.4.29f1, 2019.4.15f1, 2020.1.14f1, 2020.2.0b13, 2021.1.0a7
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- 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
Resolution Note:
This is currently By Design, albeit questionable Design.
The reasoning is: if the Profiler automatically adjusts to spikes, surrounding frames become unreadable in the chart.
That said, we are taking this as feedback to improve the UX here and likely introduce an option on how the scaling should work/ be applied. We're tracking this feedback outside of the Issue Tracker