26
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Jul 2024
26 points (100.0% liked)
Linux Gaming
15842 readers
25 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
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.
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.