Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1230548
Regression
No
[Profile Analyzer] Not enough room to display large Frame Ranges when Comparing two sets of Profiler data
Reproduction steps:
1. Open attached project "ProfileAnalyzer.zip"
2. Enter Play Mode
3. After the frames reach 4-digits, in Profiler window, stop the recording
4. Exit Play Mode
5. In Profile Analyzer window, go to Compare mode
6. For the first set of data, load "capture1.pdata"
7. For the second set of data, Pull Data
8. In Frame Summary window, observe second Frame Range
Expected result: The text does not cut off
Actual result: The text cuts off
Reproducible with: 2018.4.20f1, 2019.3.7f1, 2020.1.0b3, 2020.2.0a5
Could not test with: 2017.4.38f1 (package version unavailable)
Reproducible with package versions: 0.4.0-preview.5, 0.6.0-preview.1
Could not test with package versions: 0.4.0-preview.3 (console errors)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 0.7.0-preview.1):
Start and end now displayed on separate lines