Consider using PreUpdate or similar custom schedule instead of PostUpdate by default #450
Labels
A-Integration
very bevy specific
C-Enhancement
New feature or request
D-Medium
P-Medium
S-not-started
Work has not started
When RapierPhysicsPlugin systems are added to PreUpdate schedule - custom user systems "just work" out of the box.
This reduces the need to mess around with ordering inside PostUpdate but before TransformPropagation.
Alternatively, introducing custom schedule before Update schedule should work as well.
Otherwise pretty much every project had to be set to run this way to ensure adequate domain logic systems ordering.
Adding Rapier to the PostUpdate makes systems that do for example camera logic to skip a frame and cause a stutter if not ordered correctly. Moreover, logic that relies on GlobalTransform will miss two frames.
The text was updated successfully, but these errors were encountered: