-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wiimote tilt support? #21
Comments
Right now the configuration files are essentially "make them as you need them", with everything falling back to defaults when not set via a file.
You'll want something like the following:
Those commands can be typed into MoltenGamepad directly, or you put them in a file inside the profiles directory for easy loading later. Notice how the accelerometers are enabled, and I mapped the relevant wiimote axis onto the x axis of the virtual controller's left joy stick. This corresponds to steering-wheel-esque tilting.
Oh, and a fair bit of warning: |
Lots to try there. Now I get how to issue commands. I was trying to send them via the I'll try the Regards battery drain, was this the same when used with the Wii officially, or did they manage reads differently perhaps? Thanks very much for getting back to me on this. |
You said you installed as Single User, so that means you wrote your own service files, yes? You should check how your environment is set up when run via your service files. I think MoltenGamepad might have been unable to find a sensible location from your environment variables, so it bailed out of trying to create its directory. Writing to the FIFO should be acting as equivalent to just typing things directly into MoltenGamepad, assuming MoltenGamepad is listening to it. Sounds like something went wrong, and I'd appreciate more details on how you were running MG and how you were writing to the FIFO. I'm pretty sure it is the same as the Wii. The linux kernel is using the protocol reverse-engineered from the Wii. The wiimote supports configuring different reporting styles, and by not opening those sensors we can stick to the simpler reports. I haven't actually done any tests to see how much a difference it makes. Looking back at the kernel wiimote module, I see they do mention the IR feature being power costly (a camera + tracking). No mention about the accels. Perhaps sending the accel data isn't much of a drain. Another reason for disabled accels by default is that they'd create a lot of spurious events inside MoltenGamepad even if they end up ultimately being ignored. |
Changing to help wanted: How should we process tilt values to be most usable? The code is already able to get the raw accelerometer data. We just need a smarter way of using those numbers. |
Opening separate issue for improving tilt and Wiimote pointing. |
Hi,
I've followed the build and installation instructions for SingleUser as I'm running a Retropie install on OSMC (Rpi3). All appears to have been successful, apart from having to manually connect the controller each time through
bluetoothctl
and the Wiimote's sync button.Emulationstation detects the controller and I can configure all of the buttons. But i can't set up the analog axes. This I anticipated would come from the Wiimote accelerometers (I'm doing all this to let my daughter use a Wiimote and steering wheel for N64 MarioKart as her hands are too small for handling analog sticks on a joypad and the first thing she tried to do was intuitively steer by tilting the controller).
I tried to diagnose using
jstest
from the commandline but that doesn't even register the button presses that are already proven to work, let alone the axes, so that's not been helpful at all.So is tilt support actually a part of the driver? I wondered if it was a configuration issue, but I can't find any config files. The installer didn't create anything under
~/.config/
or in/etc/
as I was expecting so I can't see anything to be tweaked.Many thanks.
The text was updated successfully, but these errors were encountered: