Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.3
2022.1
2022.2
2022.2.0a13
Issue ID
1429694
Regression
No
"Expanding invalid MinMaxAABB" errors thrown in the Console window when inserting lange values in Transform component
Reproduction steps:
1. Open the attached Unity project "Project.zip"
2. Go to the Scene folder and open "SampleScene.unity" Scene
3. In the Hierarchy window select Cube GameObject
4. In the Inspector window Transform section click on the Scale X value
5. Change the value manually with the keyboard (for example: "55555555555555555555")
6. Observe the Console window and the Scene view
Expected result: Errors are thrown in the Console window, Cube GameObject disappears from the Scene view
Actual result: No errors are thrown in the Console window, Cube does not disappear from the Scene view
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.3f1, 2022.1.2f1, 2022.2.0a15
Not reproducible with:
Reproducible on: macOS 12.3.1 (Apple M1 Max) Editor, Windows 10 (Intel(R) Core(TM) i9-10980XE CPU 3.00GHz) Editor
Notes:
- The issue is reproducing when changing Scale and Position values, no errors are thrown in the Console window when changing Rotation values
- When inserting large values in Position, the error is thrown: "Invalid worldAABB. Object is too large or too far away from the origin."
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2022.2.X):
The expected behaviour in cases where invalid input is entered to the transform inspector is to show an error explaining what is wrong.