Search Issue Tracker
By Design
Votes
0
Found in
2017.1.1p4
Issue ID
958672
Regression
No
Physics.ClosestPoint with convex MeshCollider returns MeshCollider's pivot point, when given location is on the collider
To reproduce:
1. Open attached project "Justins_TestClosestPoint.zip".
2. Open and Play "TestScene".
Expected result: Blue cube is always showing the "closest point" from the yellow cube, to the mesh.
Actual result: Closest point is shown as the pivot of the mesh, when given position is on the edge or the center.
Reproducible: 5.6.4f1, 2017.1.2p2, 2017.2.0f3, 2017.3.0b6, 2018.1.9f2, 2018.2.18f1
Note:
ClosestPoint added only in Unity 5.6.
Workaround:
Make sure the location point is not on a meshCollider, when checking for ClosestPoint.
Fixed in: 2018.3.0b2, 2019.1.0a8
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in: 2018.3.0b2, 2019.1.0a8