Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2020.1
2020.1.0a23
Issue ID
1218187
Regression
No
Rotated and scaled parent distorts child object Mesh Renderer or Collider
How to reproduce:
1. Open attached project and scene "repro"
2. Select Cube(2) on hierachy
3. Observe sceneView -> you should see the mesh and green colliderbox is already not aligned, the Cube(2) is distorted (wrong)
4. Drag Cube(2) on hierachy to same level as Cube (so that Cube is not Cube(2)'s parent)
5. Observe sceneView -> you should see the mesh and green colliderbox is aligned. the Cube(2) is not distorted (correct)
Expected result: the renderer is aligned with the box collider
Actual result: either renderer or box collider is distorted
Reproducible with: 2017.4f.37f1, 2018.4.17f1, 2019.2.21f1, 2019.3.1f1, 2020.1.0a23
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Our physics integration doesn't support skew transform (=rotation in the non-uniformly scaled subspace), as it turns primitives into general type shapes. For instance, a simple box may become a parallelogram - this becomes costly from the computation cost point of view, and it's a hidden cost kind of thing as well.