Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.0f3
Issue ID
961760
Regression
No
OverlapCapsuleNonAlloc is detecting Mesh Collider where the capsule is not physically overlapping with the mesh
Reproduction steps:
1. Open the attached project "961760.zip";
2. Open the CSGErrorExample scene;
3. Make sure that the Gizmos are drawn;
4. Enter a Play mode;
5. Observe that the Capsule Collider is animated to move around the FBX model and when it moves, red and green crosses appear.
Expected results: When Capsule is moving, we should see only green crosses, which mean that ComputePenetration gives back a penetration distance.
Actual results: We can observe that red crosses also appear, which mean that OverlapCapsuleNonAlloc returns a collision when there clearly isn't one.
Reproduced on: 5.6.3p4, 2017.1.2p1, 2017.2.0p1, 2017.3.0b7. 2018.1.0a2.
Fixed in PhysX 3.4.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
Add comment