Search Issue Tracker
Fixed in 2021.3.21f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a1
Votes
0
Found in
2021.3.16f1
2022.2.2f1
2023.1.0a25
2023.2.0a1
Issue ID
UUM-24640
Regression
No
Grid Size Field snapping to lowest possible value when the number begins with zero
Reproduction steps:
1. Open the attached project “GridSizeBug“
2. Set Tool Handle Rotation to Global
3. Navigate to the Grid Snapping Menu
4. Change Grid Size of any axis to 0.1
Expected result: Grid Size Field is 0.1
Actual result: Grid Size Field is 0.10001 because when the first number is zero, the field immediately assigns the lowest possible value (0.00001)
Reproduced with: 2021.3.16f1, 2022.2.2f1, 2023.1.0a25
Not reproduced with: 2020.3.44f1 (Grid Size Field not implemented)
Reproduced on: macOS 13.0.1, Windows 10 (User reported)
Note: Bug only reproduces when the first number is 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
- 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 (fix version 2022.2):
Fixed in: 2022.2.5f1