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

Consider using PreUpdate or similar custom schedule instead of PostUpdate by default #450

Open
VergilUa opened this issue Nov 18, 2023 · 0 comments
Labels
A-Integration very bevy specific C-Enhancement New feature or request D-Medium P-Medium S-not-started Work has not started

Comments

@VergilUa
Copy link

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.

@VergilUa VergilUa changed the title Consider using PreUpdate or similar schedule instead of PostUpdate by default Consider using PreUpdate or similar custom schedule instead of PostUpdate by default Nov 18, 2023
@Vrixyz Vrixyz added C-Enhancement New feature or request D-Medium P-Medium S-not-started Work has not started A-Integration very bevy specific labels May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Integration very bevy specific C-Enhancement New feature or request D-Medium P-Medium S-not-started Work has not started
Projects
None yet
Development

No branches or pull requests

2 participants