dimforge / dimforge/bevy_rapier

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

Open
#450 0 comments 0 reactions 0 assignees View on GitHub
A-Integration C-Enhancement D-Medium P-Medium S-not-started
Dominant language
Rust
Stars
1.6k
Forks
282
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.