Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.44f1
2022.3.48f1
6000.0.22f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
Issue ID
UUM-83530
Regression
No
Modifying ints with short ranges via property name in Inspector leads to skipping values
Steps to reproduce:
- Open a Unity project
- Add a new GameObject to the scene (GameObject > Create Empty)
- Add the attached IntInspectorTest.cs script to the project. This script has a serialized Int value with a very short range (0 - 4)
- Drag the IntInspectorTest.cs script onto your new GameObject
- Select the GameObject
- In the Inspector, modify the 'Test Int' value by dragging on the Property Name (not the slider)
Actual results: It is very difficult to set the value to specific values in the range. Even if you only move the mouse slightly, the value will often skip numbers and sometimes even go straight from 0 to 4 and vice versa
Expected results: It is possible to set the value of the int to specific values in the range, without it snapping past values.
Reproducible with versions: 6000.0.22f1, 2022.3.48f1, 2021.3.44f1, 7000.0.0a3
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS): Windows 10/11
Notes:
- This issue occurs with small ranges (in the IntInspectorTest script, the range of the int is 4).
- Using the slider (instead of the property name) to change the value works as expected.
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.