Search Issue Tracker
Fixed in 0.7.0-preview.4
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1244633
Regression
No
[Profile Analyzer] Frames without selected marker stay selected when selecting frames that contain that marker
How to reproduce:
1. Open attached "ProfileAnalyzer" project
2. Open Profile Analyzer (Window->Analysis->Profile Analyzer)
3. In Profile Analyzer go to the Compare tab
4. Load in user's attached "Profile Analyzer - Capture (2019.3.6f1).data.pdata" in the first slot
5. In the second slot load in the user's attached "Profile Analyzer - Capture (2020.1.0b2).data.pdata" data
6. Uncheck Pair Graph Selection if it's checked (found under the frames)
7. In the first data select 1 through 20 frames
8. In the second data select 21 through 40 frames
9. Under Filter section in Name Filter option type in "PhysX.DirtyShapeUpdatesTask"
10. Right-click on "PhysX.DirtyShapeUpdatesTask" marker and select "Select frames that contain this marker (with current selection)"
Expected result: First data frames are unselected as there are no frames that contain that marker
Actual results: First data frames stay selected implying that all of the frames contain that marker
Reproducible with: 0.5.0-preview.1, 0.6.0-preview.1 (2018.4.23f1, 2019.3.14f1, 2020.1.0b9, 2020.2.0a11)
Could not test with: 0.4.0-preview.3, 0.4.0-preview.5, 0.4.0-preview.6 because couldn't load in attached data (Incorrect file version), 2017.4.40f1 because could not install Profile Analyzer
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 0.7.0-preview.4):
Added support for selecting zero frames when marker is not present