You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2023. It is now read-only.
Using a Wii remote (with attached MotionPlus, and nunchuk).
I've successfully made Windows 10 recognise the wiimote as a games controller, and can access the controller properties. Buttons all register, nunchuk stick controls one set of X/Y axes. X rotation responds to rotating the wiimote about the long axis; Y rotation to tipping it up and down.
But nothing reacts to "Yawing" the remote (rotating it about a vertical axis passing through the home button) - the Z axis and Z rotation bars never move.
Is this expected?
The text was updated successfully, but these errors were encountered:
It is currently by design. The driver doesn't support MotionPlus (as in doesn't use any of its sensors). So for the positional tracking of the Wii Remote, it is only using the Wii Remote build in accelerometer. That accelerometer picks up gravity (downward force, when idle on a flat surface). Using that downward vector you can give a rough position on the two orthogonal axes while not in quick motion. However you are unable to track any rotation round that downward vector itself.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using a Wii remote (with attached MotionPlus, and nunchuk).
I've successfully made Windows 10 recognise the wiimote as a games controller, and can access the controller properties. Buttons all register, nunchuk stick controls one set of X/Y axes. X rotation responds to rotating the wiimote about the long axis; Y rotation to tipping it up and down.
But nothing reacts to "Yawing" the remote (rotating it about a vertical axis passing through the home button) - the Z axis and Z rotation bars never move.
Is this expected?
The text was updated successfully, but these errors were encountered: