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
When ColliderDisabled component is removed collision detection is not getting effectively re-enabled (collider does not affect rigid bodies etc.).
Please see attached code for a minimal reproducible example: rapier-bug-enable-collider.zip
I tried to debug it for a moment and it seems that ColliderDisabled component removal is properly detected so it may be a bug in the Rapier itself.
The text was updated successfully, but these errors were encountered:
rafalh
added a commit
to rafalh/rapier
that referenced
this issue
Oct 18, 2023
If collider was enabled and no other attributes were changed its collisions
were not detected. This was the result of `needs_broad_phase_update` function
not handling case of changed enabled status.
Fixesdimforge/bevy_rapier#435
This issue is fixed by dimforge/rapier#538
Workaround until new version is released: modify transform component (can be set to the same value, it's only important to trigger change detection)
When
ColliderDisabled
component is removed collision detection is not getting effectively re-enabled (collider does not affect rigid bodies etc.).Please see attached code for a minimal reproducible example: rapier-bug-enable-collider.zip
I tried to debug it for a moment and it seems that
ColliderDisabled
component removal is properly detected so it may be a bug in the Rapier itself.The text was updated successfully, but these errors were encountered: