The controller LED lighting up blue is possibly a Steam client issue, since it also happens when the client (not the game) starts up. See https://github.com/ValveSoftware/steam-for-linux/issues/8019.
In some cases you need to exit game and launch it again, notably after Proton version has changed (such as 6.3 -> 7.0).
I had been launching the game multiple times, the controller wasn't working every time. I haven't tested with Proton 7.0 though.
I had been launching the game multiple times, the controller wasn't working every time. I haven't tested with Proton 7.0 though.
I know there are games where it just doesn't work for some reason, but I was making a note that something in the launch of a newer version might need improvement. Some games with Uplay have issues where you need to disable Steam input to get gamepad working so there are some rough edges somewhere.
Thief (2014) works fine with Proton 7.0 for me.
This problem still persists. With Proton 7.0 too.
Any updates or fixes?
Having this issue as well, it works wired but not over bluetooth.
my controller lits up blue and it worked fine for a couple of titles I tried: brotato, ys viii and deep rock galactic. Is the controller recognized by the system when connected through bluetooth? Something like antimicrox can be used to confirm the controller itself and its input is being recognized by the system.
Another factor could be bluez, I tried with 5.79 and git and both worked fine.
Is the controller recognized by the system when connected through bluetooth?
As I wrote in the bug description, the controller works other than in Proton games.
@Lastique yes, but recent reports didn't specify, so it can be hard to determine what is currently affecting users. As far as the led goes, mine remains blue while it's connected to my computer, with or without a game being open. Tested thief 4 just now and it worked as expected.
What do your steam input settings look like? Is playstation support enabled?
The only other thing I could think of possibly interfering is some udev rule, they are usually at /usr/lib/udev/rules.d/
What do your steam input settings look like? Is playstation support enabled?
I don't have access to that system at the moment, but AFAIR I didn't enable any Steam Input functionality. That is, Steam Input should be disabled and the controller input should be interpreted as is, without any transformation by Steam.
BTW, the blue LED light seems to be a generic Wine+Linux kernel issue as I see the blue LED light up even when running apps under Wine, and it started happening after an upgrade to some Ubuntu version. Looks like Wine initializes the controller on startup and at some point the kernel started initializing the LED on that event.
I'm having the same issue here, on borderlands 4 it dont work, also on The last of us 2 remake.
Compatibility Report
System Information
I confirm:
Symptoms
Upon launching the game, the controller LED lights up blue (normally it is turned off on my system after connection). In the game, buttons or stick movements are not recognized. The touchpad area acts as a mouse touchpad.
The gamepad is working correctly in native games running from Steam, as well as Windows games running under vanilla Wine 7.0-rc6.
Reproduction