Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4
2020.2
2020.2.6f1
2021.1
2021.2
Issue ID
1317454
Regression
No
OverlapCapsule falsely detects an overlap with a nearby MeshCollider when the start and end points of the capsule are very close
How to reproduce:
1. Open the user's attached project
2. Open the Main Scene
3. In the Hierarchy focus the OverlapTester GameObject
4. Observe the sphere gizmo
Expected result: The sphere gizmo is green
Actual result: The sphere gizmo is red
Reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.7f1, 2021.2.0a7
Notes:
- The issue doesn't reproduce when the Convex property of the Quad's Mesh Collider is set to true
- The issue reproduces with both OverlapCapsule() and OverlapCapsuleNonAlloc()
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
Using degenerate capsules raises a condition in PhysX where distance is computed to a zero length linear segment. To avoid this, always prefer OverlapSphere and OverlapSphereNonAlloc for degenerate capsules with endpoints closer than epsilon (~1e-5)