Search Issue Tracker
Fixed in 0.7.0-preview.4
Votes
0
Found in [Package]
preview.1 - 0.6.0
Issue ID
1235880
Regression
No
[Profile Analyzer] Top markers from median frame showing negative level numbers when Depth slice is between 1 and 16
How to reproduce:
1. Open the Profile Analyzer
2. Go into the compare tab
3. Load 'editorcapture.pdata' into 1st data slot
4. Load 'Profile Analyzer - Capture (2019.3.6f1).data.pdata' in the 2nd data slot
5. Ensure 'Auto Right' is checked
6. Change Left Depth Slice to '1'
7. Now look underneath the 'Top 10 markers on median frames' section
9. Notice it says 'Top markers from median frame, depth filtered to levels 1 and -16 only'
Expected result: No negative level numbers are displayed
Actual result: Negative level numbers are displayed
Reproducible with - 2018.4.21f1, 2019.3.10f1, 2020.1.0b5, 2020.2.0a7
Package reproducible with - preview.1 - 0.5.0, preview.1 - 0.6.0
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.4):
Top markers from median frame no longer show negative level numbers