Add extrapolated prediction to drift compensation #1184
Merged
Conversation
This file contains 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
nekomona
requested review from
ButterscotchV,
Eirenliel,
Erimelowo,
ImUrX and
loucass003
as code owners
ButterscotchV
added
Type: Enhancement
ButterscotchV
approved these changes
Oct 7, 2024
loucass003
approved these changes
Oct 9, 2024
loucass003
force-pushed
the
drift-prediction
branch
from
eca3e8e
to
e8a9cf0
Compare
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.
Previous drift compensation only interpolates between current yaw and the inverse of recorded drifts. This limits the compensation effectiveness as the drift would spin the tracker continuously, moving beyond the recorded drift angle.
This PR would keep rotating the compensation angle at the speed averaged from recorded drifts. It would give better compensation result at the presence of continuous drifting for a longer period of time.
Depending on SlimeVR/SolarXR-Protocol#148