[Bug] Gyroscope Detected As Right Stick When Plugged Into USB On Linux

[Jazztache]

Hello!

When I plug my Nintendo Switch Pro Controller into a USB port, and start JoyShockMapper, moving the controller registers the inputs as RLEFT, RRIGHT, e.t.c. This means that the controller is somehow using motion data as the right stick. I am not sure what causes this.

I am running joycond on Arch Linux. I primarily use JSM on KDE Plasma.

Note that I am on the latest commit in this pull request: https://github.com/Electronicks/JoyShockMapper/pull/162/files. However, this should be fine. This commit was made to fix a bunch of Linux-specific issues. I am not sure if this issue occurs on Windows or not.

Any directions on further diagnosing the issue will be appreciated. I can compile and build debug versions of JSM if need be.

Thankyou!

[Jazztache]

Just to provide some additional information: I got this occurring over Bluetooth if the program was ran without sudo permissions. I usually always run with sudo perms, but since there are issues with JSM via sudo on Hyprland, I tested it without.

Separate cause, same outcome, related enough to be in the same issue report. Might be the same fix as well.

[Electronicks]

Check what GYRO_OUTPUT is set to. If you have a virtual controller set up, it can be RIGHT_STICK.
The bindings should be called MUP, MDOWN, MLEFT and MRIGHT.

[fanser3c]

Using JSM 3.5.5 and later versions on Windows with virtual Xbox controller mapped and gyro as RIGHT_STICK, I remembered I had the issue which JSM registered RLEFT, RRIGHT, RUP, RDOWN, ... even both joycons were steady placed, making gaming impossible. Because of this, I only use JSM 3.5.4 and earlier versions with my pair of joycons on windows. I don't know whether my issue relates to your issue.

On Linux, JSM has no virtual game controller support yet and I had no issue on that even I used the pull request build of JSM 3.6.1.
I have no experience on joycond. Maybe it created a virtual game controller and had something connected to JSM.

Maybe you can try out JSM 3.5.4 Linux to see if your issue still exists.

[Jazztache]

Strangely, I haven't had this issue recently. Keep this open for now, I still need to test this. I will update to the latest main commit on both my laptop and desktop, and try this soon.

[Jazztache]

Whoops. Accidentally closed it. My bad. That being said, I am testing it on my laptop, which still has the same commit as before, and its working perfectly over USB C to USB C.

If something more specific comes up, I might just make a separate issue request and reference this one.

For now, ignore my previous remark about not closing the issue.