Search Issue Tracker
Fixed in 1.0.0
Votes
0
Found in [Package]
0.6.0
Issue ID
1231989
Regression
No
Profile Analyzer keyboard commands affect only the last modified Frame Range when 'Pair Graph Selection' is disabled
How to reproduce:
1. Create a new project
2. Import the Profile Analyzer package from the Package Manager
3. Open the Profile Analyzer window (Window -> Analysis -> Profile Analyzer)
4. In the Profile Analyzer window click the Compare tab and load the data (capture.pdata and capture2.pdata)
5. Make sure 'Pair Graph Selection' option is disabled
6. Select a frame in the upper data and then in the lower data
7. Using the keyboard commands (+, -, <, >) change the Frame Range
Expected result: there's a way to choose which Frame Range gets modified
Actual result: keyboard commands affect only the last modified Frame Range
Reproducible with: 0.5.0 - preview.1 (2018.4.20f1, 2019.3.6f1), 0.6.0 - preview.1 (2020.1.0b2, 2020.2.0a5)
Could not test with package versions: 0.4.0 - preview.3 , 0.4.0 - preview.5, 0.4.0 - preview.6 (keyboard commands not introduced)
Workaround: right-click on the Frame Range and change it from there or reselect the Frame Range and then use the keyboard commands
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
- Meta Quest System Keyboard does not render text in its input field when typing
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
Resolution Note (fix version 1.0.0):
FrameTime graph now shows border when selected to make it clearer when it has keyboard focus.
Keys 1 and 2 select the first or second frame time graph to take keyboard focus.