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

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

Open
U1trabot opened this issue Apr 14, 2024 · 0 comments
Open
Labels
A-Dynamics A-Integration very bevy specific D-Medium P-High arbitrary important item S-not-started Work has not started

Comments

@U1trabot
Copy link

Similar to #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.

@Vrixyz Vrixyz added D-Medium P-High arbitrary important item S-not-started Work has not started A-Dynamics A-Integration very bevy specific labels May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Dynamics A-Integration very bevy specific D-Medium P-High arbitrary important item S-not-started Work has not started
Projects
None yet
Development

No branches or pull requests

2 participants