dimforge / dimforge/bevy_rapier

Removing ColliderDisabled component does not re-enable collisions (again)

Open
#494 0 comments 0 reactions 0 assignees View on GitHub
A-Dynamics A-Integration D-Medium P-High S-not-started
Dominant language
Rust
Stars
1.6k
Forks
282
PR merge metrics
No merged PRs in 30d

Description

Similar to https://github.com/dimforge/bevy_rapier/issues/435 I am finding that when I add the ColliderDisabled component and then later remove it the collider remains non-collidable. I've debugged and proved that the code is indeed always removing the component so I can only assume there's some bug in (bevy-)rapier. Additionally it seems that this issue is not always present (it starts off working as expected) but once it has occurred once it will then occur seemingly every time.

Since the linked issue above was supposedly fixed in the version of bevy rapier I am using (0.24.0, 3d, with `serde-serialize` and `enhanced-determinism` features {although I have tested without `enhanced-determinism` and it still occurs}) I assume this is caused by something different. No idea if this is an issue with rapier3d as a whole or just the bevy version, but thought I'd post the issue here as this is the version I am directly using.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.