Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1234846
Regression
No
Profile Analyzer "Frame Range" summary becomes misleading when ordering frames by duration or inverting a Frame Range
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. In the Profile Analyzer window load the data (Capture (2019.3.6f1).data.pdata)
5. Right-click on the Frame Control and toggle "Order By Frame Duration" on
6. Select any Frame Range that would have more than 1 frame
7. Right-click on the Frame Control and toggle "Order By Frame Duration" off
Expected result: the "Frame Range" Summary shows an explanation/ tooltip about the meaning of it
Actual result: the "Frame Range" Summary has no explanation and it becomes misleading
Reproducible with: 0.4.0 - preview.3 (2020.2.0a7), 0.4.0 - preview.5 (2018.4.20f1), 0.4.0 - preview.6 (2019.3.7f1), 0.5.0 - preview.1 (2020.1.0b4), 0.6.0 - preview.1 (2020.2.0a7)
Notes:
1. Even in this scenario "Frame Range" Summary provides useful information (showing the first and the last selected frames but saying nothing about those in-between). However, it should be clear how to interpret it
2. Similar issue occurs when selecting a Frame Range and then inverting it
3. Package versions 0.4.0 - preview.6 and below have "Order By Frame Time" instead of "Order By Frame Duration"
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 0.7.0-preview.1):
If range is not consecutive then a * is shown next to the range to make it clear