Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1231228
Regression
No
[Profile Analyzer] Marker Details revert to ordering by "Median" column when clicking "Analyze"
Reproduction steps:
1. Open attached project "ProfiAnalyze2020.2.zip"
2. In Profile Analyzer window, Load "capture1.pdata"
3. In "Marker details for currently selected range" window, click on the "Count Frame" column name
4. Click "Analyze"
Expected result: The "Marker details <...>" window remains sorted by "Count Frame"
Actual result: The "Marker details <...>" window reverts back to being sorted by "Median"
Reproducible with: 2018.4.20f1, 2019.3.8f1, 2020.1.0b4, 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)
Note:
Issue also reproduces when selecting a frame instead of clicking "Analyze"
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 0.7.0-preview.1):
Now preserve columns sorting when Analyze is clicked