Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.1.1p2
Issue ID
951920
Regression
No
[Physics] Physics.ComputePenetration calculates depth incorrectly for some collider combinations
The Scene contains a capsule collider and a non-convex mesh collider that are slightly overlapping. Physics.ComputePenetration should report that the penetration depth is quite small but instead it is reporting a very large value. If you slightly change the rotation/position/size of the colliders then the issue no longer occurs.
To repro:
1) Open attached project
2) Open Test Scene and enter play mode
3) Press S Key and see that depth is printed in console and on screen as 743.8444
Reproduced both in Editor and Standalone testing on OS X. Unity 2017.1.1p2.
Comments (1)
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
richie-greene
Feb 12, 2018 17:15
Does disabling pcm in physics manager solve this?
Im having collision issues and thats a workaround