Search Issue Tracker
By Design
By Design in 6000.3.X
Votes
0
Found in
2021.3.56f1
2022.3.66f1
6000.0.57f1
6000.2.3f1
6000.3.0b1
Issue ID
UUM-116118
Regression
No
GameObject cannot be resized with Scale Tool when axis scale is 0
Steps to reproduce:
1. Create a project
2. Create a Cube GameObject (GameObject > 3D Object > Cube)
3. Set one of the axis Scale values to 0 in the Inspector
4. Select Scale Tool in the Scene window
5. Scale the Cube with the Scale Tool on the same axis that was set to 0
Actual results: GameObject does not get scaled
Expected results: GameObject gets scaled
Reproducible with versions: 2021.3.56f1, 2022.3.66f1, 6000.0.57f1, 6000.2.3f1, 6000.3.0b1
Tested on (OS): macOS Sequoia 15.4 (M4), Windows 11
Note: Issue is also reproducible when scaling all axis at once with the Scale Tool
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:
When setting the scale of an axis to 0 in the inspector, it's not possible to change it using the tools in the scene view (as it is not possible to set the scale to 0 with the tools). This is an expected behavior, as you don't want that value to be changed when manipulation all axis for instance (0 must remain 0). This is also an behavior used by other DCCs such as Blender for instance.
Resolution Note (6000.3.X):
When setting the scale of an axis to 0 in the inspector, it's not possible to change it using the tools in the scene view (as it is not possible to set the scale to 0 with the tools). This is an expected behavior, as you don't want that value to be changed when manipulation all axis for instance (0 must remain 0). This is also an behavior used by other DCCs such as Blender for instance.