v1993 / linuxmotehook2 Goto Github PK

I'm interested in an improvement of motion control in the retro-gaming distribution batocera. The Cemuhook protocol seems to be the best choice currently, because some emulators lack SDL motion support (e.g. Cemu - thanks for your active support). I've thrown together a working proof-of-concept, available as batocera-extra; there's a lot of work left, but linuxmotehook2 is a helpful part for the integration of Wimotes (documentation).

batocera is based on buildroot and does not contain a build toolchain or package manager. Thus, linuxmotehook2 binaries are built separately and bundled with batocera-extra. To simplify this procedure, I wrote a little script which may be run on any Debian-compatible architecture, having Docker as its only dependency. Once you re-enable CI, it could possibly save you some work.

Thanks for linuxmotehook2 and your efforts in making motion control for Wiimotes work on Linux!

P.S.: this issue is meant as notification only, feel free to close it anytime.

Hi! Today I just installed linuxmotehook2 on my computer to play on Cemu with a Wiimote. But when I run the program, it tells me this "No config file specified - call with `--help' for usage information." How can I create a config file?

I have built linuxmotehook2 on my laptop and want to access the wiimote controller input from the DSU Client. My goal is to write a bash script that makes the wiimote pointer my desktop's mouse and maps the wiimote buttons to other keys.

The question is how can I access the data in localhost:26760 to make this happen.

Hello, I am trying to use this on my steam deck. I am having trouble getting it to compile. Can you provide prebuilt binaries please?

I'm not sure of the setup process of this software and pairing the Wii Remote.

It is able to communicate the orientation of the controller, but it is really slow (5 seconds of lag more or less). (Tested in yuzu). Reducing the amount of data sent by the UDP communication might fix it.

how to like connect my classic controller coz like after plugging it in and opening cemu (lutris) it dosent recognize . like it recognizes the buttons on the wiimote itself just fine (dsu) but for any extention like nunchuck or classiccontroller it dosent get recognized. like when i press the buttons to map the input it is not recognized

I've been using linuxmotehook2 for some time with Cemu. Thanks a lot for this job, I greatly appreciate it.

It works well but I had to make a modification to the source code of gcemuhook/src/Server.vala so that the movement of my wiimote is correctly taken into account.

In the "normal" case, I had to modify the accelerometer consideration in this way (l. 449 of gcemuhook/src/Server.vala):
"""
case NORMAL :
//retour accel;
retourner MotionData() {
x = -accel.x,
y = -accel.y,
z = accel.z
"""

Without this modification, I have to flip my wiimote in order to be able to play Mario Kart 8 but I didn't quite understand why.

Despite these changes, there is still a problem and that is why I am sending you an email.

When I hold my wiimote flat (in this way: ---), I notice while playing Mario Kart 8 that the kart does not go straight but turns slightly.And to go straight, I have to turn my wiimote a little bit. I think there is a calibration problem.

I would like to know if it is possible to somehow calibrate the accelerometers with linuxmotehook2. I couldn't find anything in the .ini file or the source about this.

Hello. I am really happy that this software exists. Thank you.

I am having some trouble with the latency of the wiimotes. It takes anywhere from about a half a second to 2 seconds for my inputs to register. On average it is about 1 second for every button press. My nintendo switch pro-controller works just fine and feels the same as playing on real hardware but the wiimotes are very laggy. Sometimes the inputs also hold down even after I let go. All of these issues do not occur when connecting wiimotes to dolphin via bluetooth or wiimote passthrough.

As for the motion controls, only shaking works. Tilting or rotating has no affect on the game.

Again thank you for making this software and let me know if you need anything from me.

Here are my system and what version of the code I compiled:
Code commit version: e0b61c9
OS: Kubuntu 22.04.4 LTS x86_64
Kernel: 6.5.0-28-generic
AMD Ryzen 5 1600 (12) @ 3.200GHz
AMD ATI Radeon RX 470/480/570/570X/580/580X

EDIT:
Just tested the Wiimote with SDL plugin in CEMU without using linuxmotehook2 and there is no button lag. This is not a full solution seeing as there is no native support for Motion controls with a wiimote or nunchunk in CEMU. This was just to test if it was CEMU that was introducing the lag.

I compiled CEMU from source using gcc
I am using gcc: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
and CEMU commit: cf41c3b136ab7272e6801991d081c9d2c69c7143

Hi everyone, recently I bought an third party wiimote. It gets paired with my PC, but Dolphin doesn't pick it up. So is there an way to use this with an third party wiimote?? This software is my last hope.

Hi,
I've just started emulating Wii U Games on my Linux system. Since the motion controls don't work on Linux, I'm trying this program. After a while I got cemu to pick up my linuxmotehook controller. But now when I try to play a game like for example Mario Kart 8, the player just randomly moves left to right and doesn't follow the motion of my WiiMote Controller...

https://user-images.githubusercontent.com/67727916/235292611-ede309a0-f8a2-4b38-917b-01937d51f4fc.mp4
In this Video I didn't move the controller at all, except pressing 1 and 2 to go back and forth...
(Yes, the Buttons work)

My Config File:

[Linuxmotehook]
Port=26760
Orientation=sideways-left
SendButtons=false
GyroNormalizationFactor=50

[0x001B7AD595F4]
GyroCalibration=235,1395,223
Orientation=sideways-left
SendButtons=true
NunchuckStickCalibration=0,2,95,83
ClassicControllerStickCalibration=0,0,25,25,0,0,25,25
ProControllerStickCalibration=0,0,1000,1000,0,0,1000,1000

My CEMU Config:

I have the same problem with multiple controllers.
Did I miss something during setup?