Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2020.2
2020.2.0a8
Issue ID
1243185
Regression
No
[Editor Constraints] ScaleConstraint gets ignored on axes that are set to zero on parent GameObject
How to reproduce:
1. Open the attached project "1243185.zip"
2. Open the "SampleScene" Scene
3. Select GameObject "Parent (0.5 X Scale)" in Hierarchy window and Scale it on X-axis to zero
4. Select GameObject "Parent (0 X Scale)" in Hierarchy window and Scale it on X-axis
Expected result: scaling GameObjects "Parent (0.5 X Scale)" and "Parent (0 X Scale)" - does not scale their child GameObjects
Actual result: scaling GameObjects "Parent (0.5 X Scale)" to zero or scaling "Parent (0 X Scale)" - scales their child GameObjects
Reproducible with: 2018.4.22f1, 2019.3.13f1, 2020.1.0b8, 2020.2.0a9
Note:
- Scaling "Parent (0 X Scale)" only scales its child GameObject if the scale was locked when a parent GameObject had a scale of zero on that specific axis
- This only happens with ScaleConstraint and does not reproduce with RotationConstraint and PositionConstraint
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
- AssetReferenceAtlasedSprite creates a copy of the Sprite during Addressables.LoadAssetAsync<TObject> which does not release when Addressables.Release is used
- Crash on TryToRegisterMonoScriptToHashMap when importing a specific .unitypackage
- Transparent GameObjects are not visible behind other transparent GameObjects when "Receive SSR Transparent" material property is enabled
- Shader is missing when "Strict shader variant matching" is enabled in the Player settings
- [Android][UaaL] Custom Frame Layout causes Unity to render over native Android UI when the App is backgrounded and foregrounded
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0b1 and above