Merged
Conversation
Zarithya
force-pushed
the
wiimote-nunchuk-calibration
branch
from
30d5570 to
88149c9
Compare
Member
|
is this something you verified and checked to have the correct values now? |
Contributor
Author
|
@DacoTaco I'm not sure what the "correct" values are, but at rest, the axes are close to 1.0 where they weren't before, which makes sense if it's meant to be correlated to gravity. This is also how the Wiimote's g-force values look/act. |
Contributor
|
Hi! I'll try to test this ASAP, but indeed it looks very related. |
Contributor
DacoTaco
approved these changes
Dec 1, 2025
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
3 participants
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.
Not sure if this is a real fix to #166 , but I noticed that the cal_g data wasn't getting offset by cal_zero like the Wiimote itself was doing. Doing this makes the g-force values look a lot closer to the Wiimote's.