Search Issue Tracker
Fixed in 1.0.0
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1233077
Regression
No
Frame values do not fit in the Profile Analyzer Summary fields when they have 6 or more digits
How to reproduce:
1. Create a new project
2. Import the Profile Analyzer package from the Package Manager
3. Open the Profile Analyzer window (Window -> Analysis -> Profile Analyzer)
4. Open the Profiler window (Window -> Analysis -> Profiler)
5. Enter the Play Mode
6. Pull the Data into Profile Analyzer after the Profiler records more than 99999 frames (6 or more digits)
Expected result: all frame values fit into Profile Analyzer Summary fields
Actual result: 6 or more digit frame values do not fit into Profile Analyzer Summary fields
Reproducible with: 0.4.0 - preview.5 (2018.4.20f1), 0.4.0 - preview.6 (2019.3.7f1), 0.5.0 - preview.1 (2020.1.0b3), 0.6.0 - preview.1 (2020.2.0a5)
Could not test with package versions: 0.4.0 - preview.3 (could not load the data)
Notes:
This issue does not occur when loading already saved .pdata files
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 1.0.0):
Large Frame Values not fit inside the box