Steam Input doesn't work with some games in Big Picutre mode #1369
Comments
|
I don't see anything useful with journalctl, but I share what I get. journalctl |
|
Heroic Games Launcher had the same issue with 24.08, (Lutris probably as well) |
|
OK. I detected the problem with the native version for Linux of Huntdown. https://store.steampowered.com/app/598550/HUNTDOWN/ If downgrading to freedesktop 23.08 solves the problem, I hope to see this version of Steam following the same steps. EDIT: |
|
@bbhtt friendly ping because it's a rather serious issue imo |
|
Downgrading is not a solution, we can't permanently keep it on a runtime that will be EOL in an year without any solution. This was reported to the runtime as well https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/1818 but none of us has access to controllers or steam decks to debug the issue. I'd defer to @smcv for insights on this, since they are involved with valve. |
|
If it helps I can make master 23.08 for now and beta with 24.08 but switching master to 24.08 is an inevitability. |
bbhtt
added a commit
that referenced
this issue
Dec 30, 2024
|
There should be some controller log files called |
Is only wireless controllers affected? |
It was an issue with every controller wired or wireless when I tested it with heroic, with WINEDEBUG=+hid it seemed that wine was receiving bad HID packets for some reason, and only when I was using it with steam input. in a normal kde session, it worked properly |
I will install flatpak steam on my other machine soon to test |
|
I'm interested to test this, because my DualShock 4 controller still works just fine with the few Steam games I have installed. Unfortunately, I don't own any of the games mentioned here that are broken, so is there a known free to play game (preferably lightweight too), that also has the issue for me to test it? My DS4 controller (connected via USB) still works as expected with the following games (24.08 runtime + Big Picture):
|
|
yeah it was working in my testing too, I will try heroic on 24.08 soon and see if it works there. I dunno what happened |
|
1738026274 version of the Steam Client and the bug is still there with Fedora Silverblue 41 fully updated. I recently bought a GuliKit KK3 Pro that is identified as a generic Xbox 360 controller with its official dongle, so now I can disable Steam Input to play all compatible games with a controller, but with Steam Input the problem even is getting worse because games like #DRIVE Rally (native Unity) also doesn't work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I detected that Steam Input doesn't work with some games if Big Picture is enabled, but it works with the Steam client in desktop mode.
Some of the games affected are the native version for Linux of BallisticNG and Split/Second (this one is only for Windows). I use Proton 9.0-3 and the Steam version is 1731433018 obtained from the Flatpak launcher. My operating system is now Fedora Silverblue 41 with the Wayland session on GNOME 47.1.
I tried a DualShock 4 and an 8Bitdo Ultimate 2.4G Wireless and I have the same result. This is my first the day with the 8BitDo controller, but I'm very sure that I could use my DualShock 4 with Steam Input in Big Picture mode previously with BallisticNG and Split/Second. I prefer to use Big Picture because I usually play with a controller.
I see that the version of steam-devices provided by RPM Fusion is 1.0.0.82, while the Flatpak launcher is in the version 1.0.0.81.
The text was updated successfully, but these errors were encountered: