Search Issue Tracker
Fix In Review
Fix In Review for 6000.5.0b2, 6000.6.0a2
Under Consideration for 6000.4.X
Votes
0
Found in
6000.4.0b12
6000.5.0a9
6000.6.0a2
Issue ID
UUM-136943
Regression
No
Entering non-numeric values in Grid and Snap Settings works inconsistently
Steps to reproduce:
1. Create new Unity project
2. Open Grid and Snap Settings in the Scene view window
3. In Grid Size > X value enter “NaN”
4. Observe the X, Y, Z fields
5. In Grid Transform > X value enter “NaN”
6. Observe the X, Y, Z fields
Actual results: Entering “NaN” in Grid Transform Position, value goes back to 0, meanwhile entering “NaN” in Grid Size, “NaN” stays in the field
Expected results: Fields in Grid and Snap Settings should work consistently, if Position fields resets to 0, Grid Size and Increment Snap fields should reset to 0
Reproducible with versions: 6000.4.0b12, 6000.5.0a9
Can’t test with versions: 6000.3.9f1 and lower (Grid and Snap Settings not available)
Tested on (OS): macOS Silicon Tahoe 26.3.1 (M1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.5.0b2):
Fixed in 6000.5.0b2