Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2019.4.5f1
2021.1
Issue ID
1283344
Regression
No
[Profiler] The CPU Frame chart doesn't scale with the data when the data is loaded in
How to reproduce:
1. Create a new project
2. Open the Profiler (Window->Analysis->Profiler)
3. 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)
4. Load in the attached "Data01.data" into the Profiler (load from a file button at the top right of the Profiler window)
Expected results: The CPU Frame charts scale with the loaded in data
Actual results: The CPU Frame charts do not scale with the loaded in data
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.11f1, 2020.2.0b9, 2021.1.0a2
Notes:
- Pressing on the elements in the Module details panel (Hierarchy, Timeline, and Raw Hierarchy all give the same effect) will fix the CPU Frame chart to show as it supposed to, after every press the Frame chart will move a bit closer to the correct size
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 (fix version 2021.1):
Fixed issue with wrong chart scale after profiler capture load
Fixed in 2021.1.0a9