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
7000.0.0a35
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
- UI Toolkit Editor Window Creator becomes deformed and stretched when the “Enter” key is pressed
- “Assertion failed on expression: 'IsFinite(distanceForSort)’” is spammed in the Console when changing Trail GameObject position to a very high number
- VFX Graph Node documentation icon is pixelated
- Cutout box is covered in a shadow when the object that houses the cutout is casting shadows
- “Metal: Fragment shader missing texture binding at index 0 (_MainTex / Hidden/Preview Alpha)” warnings are thrown when selecting some TextMesh Pro Font Assets
Add comment