Open NyaomiDEV opened 1 month ago
@NyaomiDEV Could you list some specific game(s) where you are seeing this issue? Are you using the Steam beta client or stable client?
@NyaomiDEV Could you list some specific game(s) where you are seeing this issue? Are you using the Steam beta client or stable client?
@alasky17 Steam stable on both computers. I am testing it with Rivals of Aether mainly because it's quick to launch. TEKKEN 8 has the exact same bug. Vampire Survivors under Proton has the same bug (actually I then discovered that they recently updated their Linux version so I also know that native Linux games are not affected now, thanks to them and to me unchecking the compatibility tick box for that game). I do have other games to test with, but I didn't think it's important to check the game as literally the joystick control panel under the Proton prefix doesn't recognize anything but physically connected controllers (yep, tested a mix of those too)
The setup: Arch Linux host PC, with an AMD 5950x and a 6900 XT. Kernel is 6.11.4; streaming via Steam Remote Play to a Framework 13 AMD for coziness' sake. This has the same distro installed. An Xbox Series controller is attached via USB to the Framework 13.
The symptom: There's no way to get the input to the games running in the host PC if the game is ran using Proton Experimental.
All the evidence I could find: Proton 9.0-3 works, so I wondered if this was a thing that I could easily diagnose. The thing is,
uinput
is loaded, and viaevtest
I could see the virtual X360 pad appearing and also properly sending inputs to the system. I then employedprotontricks
to open up the Wine Game Controllers control panel window, and there I found that Proton Experimental wasn't even listing the virtual gamepad. At this point I wonder if the recent builds have something that is off about them, and I fear this issue eventually getting into the stable branch as well; and this leads me to write about the bug.