evdevhook VS linuxmotehook2

By default, evdevhook currently has an axis inverted on the DualSense, which you can fix with a simple config file change.

As suggested at https://github.com/FrogTheFrog/steam-gyro-for-cemuhook/issues/47 you could try out using https://github.com/v1993/evdevhook. My Steam Deck arrives Q2 so I can't tell you if this works at all - would be cool if you/someone could tell us :).

Motion controls work. For emulators that need a cemuhook-style DSU protocol server, check out the evdevhook project.

I'm on POP OS and my dualsense controller works fine. I followed this guide though (https://christitus.com/ultimate-linux-gaming-guide/) to install the xanmod kernel which might have the dualsense drivers in it. When I finished setting up everything I just pressed the Share + Playstation button the dualsense controller then searched for devices on the bluetooth device manager. Besides that evdevhook (https://github.com/v1993/evdevhook) is good for motion controls on CEMU and Dolphin.

Joaorb64's joycond-cemuhook and v1993's evdevhook are probably your best options. I can't speak on either since I've used neither.

After some effort I managed to get my real WiiMote detected by Cemu (Lutris version running on Linux) as a DSUController using linuxmotehook2. I went into Mario Kart 8 with all default settings and the motion controls were unplayable. I tried messing around with the deadzone and range values and clicking Calibrate, but I still can't get the controls right. The motion seems to be random. They don't seem to inverted and I can't figure out the pattern. I'm a little confused as well. What does deadzone and range mean exactly? I know what Axis and Rotation are, but what is Trigger?