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
{{ message }}
This repository has been archived by the owner on Nov 29, 2022. It is now read-only.
In networking when you implementing rollback, you need to tick physics only networking objects and skip simulation for other visual only entities. I would add a component which freezes the entity. Like Visibility in Bevy. If such component present with boolean field is_frozen, then the object won't move, but still collide with other objects.
Naive approach would be lock translation and backup velocity for entities until this component is present. But is this the right way of doing it? Maybe Rapier have something for it?
The text was updated successfully, but these errors were encountered:
In networking when you implementing rollback, you need to tick physics only networking objects and skip simulation for other visual only entities. I would add a component which freezes the entity. Like Visibility in Bevy. If such component present with boolean field
is_frozen
, then the object won't move, but still collide with other objects.Naive approach would be lock translation and backup velocity for entities until this component is present. But is this the right way of doing it? Maybe Rapier have something for it?
The text was updated successfully, but these errors were encountered: