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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
The issue is qualified as a feature request and might be worked on depending on priorities