Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1244407
Regression
No
[Profile Analyzer] The Marker is not refocused in the Marker List when selecting "Select Frames that contain this marker"
How to reproduce:
1. Open the project "case_1244407-ProfileAnalyzer"
2. Open the Profile Analyzer (Window->Analysis->Profile Analyzer)
3. Click on the button "Load" in the Profile Analyzer window
4. Select the file "case_1244407-capture.pdata" in Assets folder and select "Open"
5. Click on the name of the column "Marker Name" to order the columns by Marker Name
6. Find 'PhysX.PxsDynamics.createForceChangeThresholdStream' in the Marker List
7. Right-click on it and select "Select Frames that contain this marker (within whole data set)"
Expected results: the position of the Marker changes in the Marker List but it refocuses automatically and the selected Marker is seen in the list
Actual results: the position of the Marker changes in the Marker List but it does not refocus automatically and the selected Marker is no longer seen in the list
Reproducible with: 0.4.0-preview.3 (2018.4.23f1, 2019.3.14f1, 2020.1.0b8, 2020.2.0a11), 0.6.0-preview.1(2018.4.23f1, 2019.3.14f1, 2020.1.0b8, 2020.2.0a11)
Notes:
1. It is reproducible when selecting "Select Frames that contain this marker (within whole data set)" or "Select Frames that contain this marker (within current selection)"
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
- The type selector in the UI Builder does not display primitive types when trying to select one in the "Select Type…" window
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
Resolution Note:
The issue is qualified as a feature request and might be worked on depending on priorities