Search Issue Tracker
By Design
Votes
1
Found in
5.3.1f1
Issue ID
762846
Regression
No
When an object has a parent and physics were initiated collider is misplaced
Reproduction steps:
1. Open attached project (ReproProject.zip)
2. Open and play the "test" scene
3. Notice that the red plank doesn't touch the ground
4. In the hierarchy click on the "ObjPlank" under level 16 -> Button(Plank) -> ObjectAffector -> ObjPlank
5. Notice that the collider is misplaced (check error.jpg)
Actual result: Collider is misplaced.
Expected result: Collider borders should be the same as the MeshRenderer borders.
Note: When the plank falls on a flat surface the collider isn't misplaced.
By Design: The basePlank object has unsupported skew transform on it, so physics and graphics won't be in sync. As a matter of fact, it's only the physics collider that is placed correctly. The graphics plank overlaps the pillars since it takes skew into account.
Reproduced on: 5.1.4p1, 5.2.4p1, 5.3.1f1, 5.3.1p4, 5.4.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment