dimforge / dimforge/parry

Bug: cast_shapes_nonlinear fails to detect collision between cuboids

Open
#317 2 comments 1 reaction 0 assignees View on GitHub
C-Bug D-Difficult P-High
Dominant language
Rust
Stars
867
Forks
157
Avg merge
7d 13h
Merged PRs (30d)
2

Description

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.

### Reproduction
Repository with minimal reproduction case: https://github.com/kalmjasper/parry_collision_bug

Visualisation of the situation:
![Visualization showing collision](https://raw.githubusercontent.com/kalmjasper/parry_collision_bug/refs/heads/main/visualisation.png)

Steps:
1. Run the example code
2. Observe that the red cuboid visibly intersects with the static gray cuboid
3. Note that `cast_shapes_nonlinear` returns `None` (no collision)
4. While `contact` correctly reports penetration depth

### Environment
- parry3d version: 0.18.0

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.