Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0a6
2018.1.4f1
Issue ID
1049530
Regression
Yes
Physics.ComputePenetration not working as expected when used with a capsule collider and a convex mesh collider
How to reproduce:
1. Open attached project "ComputePenetration Bug.zip" and scene "scene"
2. Enter Play mode
3. With WASD keys move and collide with red objects from all sides
4. In Game View, observe player colliding with red objects
Expected result: the player collides normally (just like with green objects)
Actual result: the Physics.ComputePenetration returns wrong directions (usually parallel to object's local Z-axis)
Reproducible with: 2018.1.0a6, 2018.1.5f1, 2018.2.0b9, 2018.3.0a2
Not reproducible with: 2017.1.4p1, 2018.1.0a5
Notes:
-Red objects are Unity objects ("cube 1", "wedge 1")
-Green objects are exported from blender ("cube 2", "wedge 2")
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Add comment