Search Issue Tracker
Fixed
Fixed in 2021.3.21f1, 2022.2.5f1, 2023.1.0b3, 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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2022.2.5f1):
Fixed in: 2022.2.5f1