Skip to content

Conversation

@Zarithya
Copy link
Contributor

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.

@Zarithya Zarithya force-pushed the wiimote-nunchuk-calibration branch from 30d5570 to 88149c9 Compare November 29, 2025 08:13
@DacoTaco
Copy link
Member

is this something you verified and checked to have the correct values now?
@mardy : is this something you can test since you noticed it?

@Zarithya
Copy link
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.

@mardy
Copy link
Contributor

mardy commented Nov 30, 2025

Hi! I'll try to test this ASAP, but indeed it looks very related.

@mardy
Copy link
Contributor

mardy commented Nov 30, 2025

It does fix #166 indeed! Thanks for your work, @Zarithya!

@DacoTaco DacoTaco merged commit 77075c9 into devkitPro:master Dec 1, 2025
1 check passed
@Zarithya Zarithya deleted the wiimote-nunchuk-calibration branch December 1, 2025 06:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants