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
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
- “ReferenceError: Pointer_stringify is not defined” error is thrown when downloading a file
- GameObjects are not rendered when using a fragment shader with RWStructuredBuffer in URP
- [Profiler] The GPU Highlight module flags the frame before the spike when using DoInference in a coroutine
Resolution Note (fix version 0.7.0-preview.1):
Fixed overlapping start/end numbers when zoomed in