Repository navigation
Fix: projectile trajectory drift at high simulation rates - #61
Merged
elyosh merged 3 commits intoNov 7, 2026
Merged
Conversation
Reset the carried fraction through one function instead of four copies, and wrap the step lines at the column limit.
Contributor
Author
|
Merged current main (no conflicts). Small cleanup: the fraction reset is one function now instead of four copies. |
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
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.
Steps to reproduce issue - launch T1M1 (Y-wing tutorial), bank and come to a stop. fire torpedoes, observe that the torpedoes drift away from reticle center.
Cause: At high simulation rates, projectile movement is calculated in smaller increments. The Q15 fixed-point multiplication truncates each axis independently, discarding fractional displacement every step. This causes cumulative directional drift, especially for slower projectiles.
Solution: preserve each axis's fractional remainder between updates, carrying it into subsequent movement calculations. The remainders are reset when projectile slots are reused, preventing movement state from carrying over to new projectiles.