Linux Gaming

15831 readers

40 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago

MODERATORS

poVoq@slrpnk.net

Quintus@lemmy.ml

mudle@lemmy.ml

Wooting Analog Switches not working via Proton (lemmy.ml)

submitted 3 months ago* (last edited 3 months ago) by Epzillon@lemmy.ml to c/linux_gaming@lemmy.ml

5 comments fedilink hide all child comments

Hey, I've just received and built my first custom key board using the Wooting 60HE module and Lekker L45 Switches.

I tried testing them out in Trackmania and I've run into an issue. The analog inputs aren't registered in the game. I'm running the game via Steam through Proton GE 9.7 and it just simply does not register the input.

I read somewhere as the keyboard emulates controller input you had to set the input device in the in-game controller settings to "xinput controller" but since there is no actual controller connected the only available devices are "xinput keyboard" and "xinput mouse".

I'm curious if anyone has had or solved this issue or if anyone could bring some tips on how to possibly solve this.

SOLVED: Apparently there's specific gamepad settings inside of Wootility under Settings > Gamepad. There you have to select what type of controller the software will emulate. I just took the recommended (Xbox Controller) and now it works as expected.

you are viewing a single comment's thread
view the rest of the comments

[–] Epzillon@lemmy.ml 2 points 3 months ago (1 children)

The keyboard itself is fine if I use regular mappings, however in the wootility software they provide (yes they have an official linux version) you can map controller inputs to your keys. So for example I can map (emulate) controller joystick left input to my A key to emulate the analog signal. These does not seem to register in-game. Other key inputs work fine.

[–] just_another_person@lemmy.world 3 points 3 months ago

Ah, okay. If that's the case, then I bet the management software is confusing input mapping. Rather, I'm assuming the management software gets in between the keyboard input, and what proton wants to see. If all other inputs work fine, then it's the management software with a pesudo-device that is causing the issue.

Found these: https://www.reddit.com/r/WootingKB/comments/11zm736/anybody_tried_the_wooting_kb_on_linux/ https://github.com/ValveSoftware/Proton/issues/6032

So it sounds specifically like what I said above, and disabling the analog functions puts everything back to normal working order. So, I guess check with their support folks to find a workaround. I'm sure they have one with proton startup flags or something.