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
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
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)