Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1228906
Regression
No
[Profile Analyzer] Single frame selection is displayed with overlapping Frame Start and Frame End when zoomed in
Reproduction steps:
1. Open attached project "ProfileAnalyze.zip"
2. In Profile Analyzer window, Load "case_1229216-capture.pdata"
3. Drag-select 10 frames, right-click -> "Zoom Selection"
4. Click on any frame
Expected result: The selection displays the selected frame's number and the selection count
Actual result: The selection displays overlapping Frame Start, Frame End numbers as if selecting multiple frames
Reproducible with: 2018.4.0f1, 2019.3.7f1, 2020.1.0b3, 2020.2.0a4
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)
Note:
The exact number of frames you have to select to reproduce the issue varies. At a certain zoom-in distance, a single frame will begin to show Frame Start and Frame End, though not necessarily overlap - the overlap occurs at the upper limit of the transition.
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):
Fixed overlapping start/end numbers when zoomed in