Search Issue Tracker
By Design
Votes
0
Found in
2021.3.50f1
2022.3.60f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
Issue ID
UUM-101912
Regression
No
ScaleConstraint fails to maintain child GameObject scale when parent's scale is set to zero
How to reproduce:
1. Open the “IN-98244_TestScaleConstraint“ project
2. Open the “SampleScene”
3. In the Hierarchy window select the “Parent (0.5 X Scale)” GameObject
4. In the Inspector window change the Transform Scale X value to 0
5. Observe the child GameObject
Expected result: The child GameObject scale does not change
Actual result: The scale changes
Reproducible with: 2021.2.0b1, 2021.3.50f1, 2022.3.60f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Reproducible on: macOS 15.3.2 (M1 Max)
Not reproducible on: no other environments tested
Notes:
- This issue also reproduces if the GameObject Scale is initially 0 and is set to 1. This can be reproduced with GameObject “Parent (0 X Scale)”.
- In 2021.2.0b1 the issue reproduces only be scaling the Parent who is initially non-zero scale to zero.
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note:
Unfortunately, this is not possible for the ScaleConstraint to adjust a game object scale when the parent game object scale is set to zero. The constraint adjusts the scale based on the values of the transform hierarchy, and multiplying any scale compensation with zero will always result in a zero scale.