Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2017.3.0a1
2017.4.7f1
2018.2.0a1
2018.3.0a1
2019.1.0a1
Issue ID
1089827
Regression
No
World scale of the child GameObject is not properly computed when parent GameObject has rotation applied
Steps to reproduce:
1. Open user attached project
2. Open the scene provided
3. Drag and drop the object "CubeToMove" as a child of Cylinder
Expected result: "CubeToMove" GameObject world scale stays the same.
Actual result: The world scale of the GameObject is stretched in the Z axis.
Reproduced in: 2017.4.16f1, 2018.1.9f2, 2018.2.17f1, 2018.3.0b11, 2019.1.0a10
Note:
1. If you do the same operation without rotation, the cube keeps it's world scale as expected.
2. If you repeat step 3 (unparent "CubeToMove" from "Cylinder" and then parent it again) " CubeToMove" GameObject keeps expanding. (Video 2 attached)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Debugger stops at commented lines of code when using ECS
- Asset preview doesn't update on changing shader's _GlobalColor property when the shader uses global uniforms
- Crash on GetSpriteAtlasDependenciesFromBinary when opening specific project
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
Add comment