Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0a20
Issue ID
1341972
Regression
Yes
[Profiler] Loading data from file 2018.3, or 2018.4 does not produce correct results
How to reproduce:
1. Create a new project
2. Open the Profiler Window (Window -> Analysis -> Profiler)
3. Load the saved Profiler data (attached in FPSSample - EnterPlayMode - warm.zip)
Expected result: All the profiler data is loaded correctly
Actual result: Some data is missing and/or it is not shown correctly
Reproducible with: 2019.4.28f1, 2020.3.13f1, 2021.1.13f1, 2021.2.0b1
Not reproducible with: 2018.4.36f1
Could not test in: 2019.1, 2019.2, 2019.3, due to project crashing when loading the profiler data
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 in: 2021.1.21f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.31f1