Open sjp761 opened 1 week ago
Proton enables both SDL and evdev/hidraw backends and chooses the most appropriate backend depending on the device. I don't think you should or need to disable hidraw for anything. Is hidraw causing problems for some devices?
I disable for games that don’t support the ps5 controller when using heroic games launcher
Okay, in any case SDL should still work, even with that setting. The changes are only related to the Steam Input virtual controller, so I'm not sure why it's breaking anything in your use case.
Just to make it clear, I’m not using steam input at all. I launch the game with heroic, not steam. Proton 9.0 makes it work fine, but experimental (regular and bleeding edge) causes the issue to pop up. GE does not have the issue either.
steam-976730.log Here is a log if it helps. Steam Input is disabled through steam. Hidraw is disabled through reg file.
Thanks, could you add +hid to the debug channels too?
Just PROTON_LOG=+hid?
Yes, that should work.
steam-sdl-issue.log Here. Steam Input and hidraw are still both disabled.
steam-976730.log Here is a log for a previous proton version where the issue did not occur
Can this be related to the issue I have with a VKB Gladiator joystick really badly recognized unless I disable SDL and xinput as told in https://www.reddit.com/r/linux_gaming/comments/xil6ra/joystick_axes_missing_in_games/ for all previous versions of proton but doesn't work at all in experimental and 9.0 after patch ?
note : joystick became unusable, buttons are not recognized or seen as weird combinations
Probably not as as my issue does not happen on Proton 9, only experimental.
With the newest bleeding edge of proton experimental, sdl based input (disabling hidraw) does not work anymore so an xbox controller is not emulated
Reg file used to disable
Issue is probably the winebus commits on July 3rd https://github.com/ValveSoftware/wine/commits/bleeding-edge/