You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using Parry3d for a couple months now to detect collisions without any issue. Yesterday I discovered an edge case where cast_shapes_nonlinear does not report a pretty obvious collision however... Unfortunately I'm not experienced enough with the code to properly debug this issue, it would be very much appreciated if someone who does could take a look.
Description
cast_shapes_nonlinear incorrectly returns no collision between two cuboids that clearly intersect. The contact function correctly reports penetration between the same objects, confirming they do intersect.
I've been using Parry3d for a couple months now to detect collisions without any issue. Yesterday I discovered an edge case where cast_shapes_nonlinear does not report a pretty obvious collision however... Unfortunately I'm not experienced enough with the code to properly debug this issue, it would be very much appreciated if someone who does could take a look.
Description
cast_shapes_nonlinear
incorrectly returns no collision between two cuboids that clearly intersect. Thecontact
function correctly reports penetration between the same objects, confirming they do intersect.Reproduction
Repository with minimal reproduction case: https://github.com/kalmjasper/parry_collision_bug
Visualisation of the situation:

Steps:
cast_shapes_nonlinear
returnsNone
(no collision)contact
correctly reports penetration depthEnvironment
The text was updated successfully, but these errors were encountered: