Search Issue Tracker

Third Party Issue

Votes

1

Found in

2020.3.35f1

2021.3.5f1

2022.1.6f1

2022.2.0a17

2023.1.0a2

2023.2.0a1

Issue ID

UUM-7394

Regression

No

SphereCast doesn't detect mesh collision at certain angles even when starting outside the mesh

--

-

Reproduction steps:
1. Open the attached project ("case_1239413-SphereCast.zip")
2. Open the repro scene ("SphereCast")
3. Enter Play Mode
4. Inspect Console and rays inside the scene

Expected result: No logs are shown (OverlapCapsule and SphereCast finds same info)
Actual result: SphereCast doesn't detect mesh collisions even though OverlapCapsule over the same region founds them

Reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a15

Notes:
1. Almost any change in parameters one way or the other will trigger the expected behaviour.
2. Similarly, increasing or decreasing the spherecast radius by a tiny amount will both produce hits, showing the issue is related to the angle/location of where the first hit would have been.
3. Setting the custom mesh to Convex mode produces a hit, so this issue might only be present in concave mode.

  1. Resolution Note:

    This is a defect in PhysX, sphere sweeps cannot handle completely co-planar cases. The sweep direction has to be in the plane of the triangle within +/-0.1 degrees for this to happen.
    https://github.com/NVIDIAGameWorks/PhysX/blob/4.1/physx/source/geomutils/src/sweep/GuSweepSphereTriangle.cpp#L60

    At the moment, closing this as "Won't fix" due to low user pain but it should be reconsidered if the problem becomes more widely encountered.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.