Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate colliders have worse perf than compound #730

Open
JulianKnodt opened this issue Sep 5, 2024 · 0 comments
Open

Separate colliders have worse perf than compound #730

JulianKnodt opened this issue Sep 5, 2024 · 0 comments

Comments

@JulianKnodt
Copy link
Contributor

I was testing out rapier on a number of primitives acting as a single collider, and from the docs it would appear that using a single compound collider versus multiple individual colliders is identical, except for the fact that using multiple would provide the collider which hit the object. What I found is that with many colliders (a few hundred), the performance slowly becomes worse and worse over time. I'm not sure what's causing this or if it's intended, but it was certainly unexpected.

If it's intentional, then it would be good to make a note of what causes it and to be wary. Otherwise, I was testing it in my own test in the testbed app. I'm not currently able to make that available, but I essentially had a large number of boxes, cylinders, and capsules and was testing collisions by dropping 5k balls on top of them. In the tail of the simulation (i.e. after the first 500 frames), the frame duration slowly creeps up.

After switching to a compound collider, the performance was stable through the whole simulation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants