Search Issue Tracker
Active
Under Consideration for 2022.3.X
Votes
6
Found in
2022.3.33f1
6000.0.6f1
Issue ID
UUM-73855
Regression
No
The non-zero value is changed to 0 when entering it for the first time into the IntegerField with showMixedValue set to true
How to reproduce:
1. Open the user-attached project “SampleProject”
2. Open the “SampleScene” scene
3. Enter the Play Mode
4. Enter a non-zero value to the field and press the Enter key
5. Observe the field
Expected results: The entered value is set
Actual results: The value is changed to 0
Reproducible with: 2022.3.33f1, 6000.0.6f1
Can’t test with: 2021.3.39f1 (IntegerField is not supported)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Notes:
- Reproducible only when entering the non-zero value for the first time
- When reproducible, the Console reports the two values simultaneously, the entered non-zero value and 0
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
- “Property offset falls outside of range for type in GetPropertyData” errors are thrown when using MaterialPropertyBlock.CopySHCoefficientArraysFrom
- Texture 2D reference links to missing documentation
- [Search] Help (?) does not work as a Search Filter
- Quest apps lose head and controller tracking
- Double separation lines are present in a kebab dropdown menu
IDKMC002
Jun 12, 2024 00:16
This occurs not only with IntegerField, but also with FloatField and other inputs.