Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.6.0b3
Issue ID
866670
Regression
No
Physics.ComputePenetration returns incorrect results with off-center rotated capsules
How to reproduce:
1. Open attached project
2. Open the scene test.unity
3. Play the scene
4. Set the X rotation of the gameobject TestGroup/TActor to 15 (any number works)
5. In the Game view, move the object using the A key until it collides with the Cube gameobject
- Note the distance between the cube and the TActor gameobject
6. In the Collision/CollisionDetector.cs script, comment out the 2nd line (#define HACK_CENTER)
7. Continue from step 3
- Note that when the TActor collides with the cube, it is slightly further away
- Reproduced in 5.6.0b3 (358ff4ed3952)
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
hippocoder
Jul 02, 2017 13:47
Not fixed for me in 2017.1 beta
oscarlosu
Mar 13, 2017 09:59
I have encountered a similar issue in 5.6.0b9, not only with capsule colliders, but also with box colliders when they are not centered on their game object's origin and the game object has rotations and/or scales. Did you find a solution? How was this fixed?