Search Issue Tracker
Fixed
Fixed in 2022.3.64f1, 6000.2.0b8, 6000.3.0a1, 7000.0.0a35
Votes
0
Found in
2022.3.62f1
6000.2.0b4
6000.3.0a1
Issue ID
UUM-107394
Regression
No
The Frame value field does not update when using the increment/decrement arrows in the Frame Debugger if the value has been manually inputted
Reproduction steps:
1. Open the attached “IN-102553.zip” project
2. Open the Frame Debugger (Window > Analysis > Frame Debugger)
3. Enable the Frame Debugger
4. In the frame input field, input any number (e.g. 5)
5. Use the arrow buttons to change the value of the frame
6. Observe the frame value in the input field
Expected result: The frame value in the input field changes
Actual result: The frame value in the input field does not change
Reproducible with: 2022.1.0a1, 2022.3.62f1, 6000.0.50f1, 6000.1.4f1, 6000.2.0b3
Reproducible on: Windows 11, macOS 15.4.1 (M4 Max)
Not reproducible on: no other environment tested
Notes:
- Does not reproduce if Enter is pressed after inputting the number
- The frames are still correctly changed in the Output window
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment