You are not logged in.
Hi everyone, since like a month ago I'm having issues on Steam with my controller, an Hori HORIPAD S (official third party Nintendo Switch Pro controller). Both in the UI and in the games opened through steam I'm having double input that, from what I'm seeing, it seems to be recognized as a controller AND a keyboard. The fact is that the double input does not correspond to that of the controller. The issue appears with both Steam Input on and off.
Is anyone having the same issue? Does anyone have a solution to this problem? The only things I found on the internet are all old guides that do not apply anymore (I tried them, they do nothing).
Let me know ^^
DE: KDE Plasma 6 on Wayland
CPU: AMD Ryzen 5 5500U (4.06GHz)
GPU: AMD Lucienne [Integrated]
RAM: 16 GB
Offline
Wish I could help. I suspect this is driver related. I find if I use my switch controller while playing a game on lutris that it sees my controller as 2 controllers if I don't first turn off steam. Could be related to what you're seeing, not that anything I just said helps anything.
Offline
Idk, the problem arises only on steam, it is not an emulated controller kind of thing. When I play outside of it (unless steam input is on), both the system and the games give me no issue whatsoever. It specifically is a Steam bug, and even if I reported it a couple weeks ago it still doesn't seem for them to fixing it. What I think might have happened is that the way they use SDL is universal across all controllers or smth like that, and that when they patched the double input issue a month ago circa on the steam deck, it broke something with the switch's controllers. Does it make sense?
Either way I only found a couple recent posts here and there on reddit or other forums, and the only thing we all are sharing is that we use a third party controller, so there's also that.
All of this wouldn't be an issue if I could play on keyboard but it's impossible for me, I tried too many times (plus I play mostly games with a gamepad in mind)
Last edited by shiny_mew (2024-12-06 17:39:50)
DE: KDE Plasma 6 on Wayland
CPU: AMD Ryzen 5 5500U (4.06GHz)
GPU: AMD Lucienne [Integrated]
RAM: 16 GB
Offline
Steam Input is a big whole mess (sometimes) AND a big life saver (sometimes).
Anyway, lots of things you can test:
1_ "DisableHidraw"=dword:00000001 (https://selfmadepenguin.wordpress.com/2 … -problems/)
2_ disable Steam Input both globally both per-game
3_ Also disable Steam Input inside Proton (the Steam's app)
4_ remove /usr/lib/udev/rules.d/70-steam-input.rules
5_
If you experience problems with the rumble feature not working in games, it may be necessary to set the environment variable
SDL_JOYSTICK_HIDAPI=0
6_
SDL_HIDAPI_DISABLE_LIBUSB=1
I'd start by only trying 4_ alone, at first.
(sorry for being so vague and sorry for providing such uncertain solutions)
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
Thank you, but sadly none of these things fixed the problem.
Here's a list of other things I tried:
- Following the arch wiki gamepad configuration;
- Adding an udev rule to the steam input file;
- Adding a kernel parameter to the boot manager;
- Turning steam input on and off;
- Emulating an xbox controller (it's even worse);
- Running steam on both xorg and wayland;
- Uninstalling the client and all the cache;
- Changing the configuration directly via SDL;
- Trying steam with the native runtime on and off;
- Trying both the beta and the stable client.
Furthermore, I think it should be mentioned that I tried 2 other controllers: a ps3 and a ps4 one both cabled and via bluetooth. The same problem arises.
It's really driving me mad, and what makes me even angrier is that they probably aren't going to fix this soon cause only I and a few other people are having this issue.
Last edited by shiny_mew (2024-12-11 08:48:52)
DE: KDE Plasma 6 on Wayland
CPU: AMD Ryzen 5 5500U (4.06GHz)
GPU: AMD Lucienne [Integrated]
RAM: 16 GB
Offline
Enter X11 session and check your mappings ( https://aur.archlinux.org/packages/controllermap or https://gitlab.com/ryochan7/sdl2-gamepa … 0.9.tar.gz ) with and without /usr/lib/udev/rules.d/70-steam-input.rules.
Remember to reload rules with:
# udevadm control --reload && udevadm trigger
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
the problem arises only on steam, it is not an emulated controller kind of thing. When I play outside of it (unless steam input is on), both the system and the games give me no issue whatsoever. It specifically is a Steam bug, and even if I reported it a couple weeks ago it still doesn't seem for them to fixing it. What I think might have happened is that the way they use SDL is universal across all controllers or smth like that, and that when they patched the double input issue a month ago circa on the steam deck, it broke something with the switch's controllers.
I have had this same issue (with STEAM and Heroic Games Launcher using a PS5 DualSense), you can use STEAM with "Big Picture Mode" to get around this issue. STEAM's Big Picture Mode makes "gamescope" the windowing system for STEAM (just like the STEAM Deck's UI), and it captures most system inputs (volume wheels, keyboard and mouse, controllers, etc) in a sane way for use with a gaming setup. I hope this will help in your case as well!
According to my anecdotal experience, this issue is most prevalent in older versions of KDE Plasma 6 if you set the "Remote control requested" modal menu's "Allow restoring on future sessions" option (for using a controller as a mouse). You have to both restart the system and unplug the controller to fix it.
See: KDE Discuss > Remote Control Requested,
Reddit post reply and Reddit r/kde > How to REMOVE Remote control request prompt plasma 6.1
Last edited by Nyctfall (Yesterday 18:16:36)
Offline