Do physics in fixed update, do visuals in update - #58
Merged
Conversation
This was referenced Jan 2, 2026
Closed
qhdwight
marked this pull request as ready for review
January 2, 2026 06:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This was a pretty glaringly big issue which is kind of embarrassing.
Before we were doing physics in
Updatewhich is not good since it is essentially the render loop and does not run in a fixed time step.Now we do physics in
FixedUpdatewhich is where Rapier/Avian update internally. And then for visuals we interpolate.There is a great explanation here that is less terse than the above: https://github.com/bevyengine/bevy/blob/main/examples/movement/physics_in_fixed_timestep.rs
Closes #54