I have lutris-0.5.8.4-1.fc34.x86_64 and recently installed the Epic Games Store from Lutris's GUI. Inside the Epic Games Store I have Oddworld: Soulstorm. (Unfortunately this game is not available on Steam.)
I'm trying to play this game using a PS5 controller that is connected to my computer via Bluetooth.
With both wine versions lutris-6.13-3-x86_64 and lutris-6.14-x86_64 the controller doesn't work properly with Oddworld: Soulstorm, it feels as though some button is stuck. Lutris's "Autoconfigure joypads" setting is enabled (by default, I didn't change it).
After some googling I found a whacky environment variable that works around this issue. SDL_GAMECONTROLLERCONFIG needs to be set to the following value:
I'm not sure what the actual problem is but reporting it here in case it can be fixed. Perhaps the above environment variable could be used by default when this type of controller is detected?
Upstream wine-staging: This is what's installed by my distro (Fedora 34), and I tried to set Lutris to use that but it was stuck forever at updating my wine prefix. How do I get it to work?
Proton: I tried to add the game's executable as a non-steam game to Steam (enabled the compatibility option to run with Proton) and it worked fine there. I didn't try to run Proton from Lutris because I read on the Internet this is discouraged.
I have
lutris-0.5.8.4-1.fc34.x86_64
and recently installed the Epic Games Store from Lutris's GUI. Inside the Epic Games Store I have Oddworld: Soulstorm. (Unfortunately this game is not available on Steam.)I'm trying to play this game using a PS5 controller that is connected to my computer via Bluetooth.
With both wine versions
lutris-6.13-3-x86_64
andlutris-6.14-x86_64
the controller doesn't work properly with Oddworld: Soulstorm, it feels as though some button is stuck. Lutris's "Autoconfigure joypads" setting is enabled (by default, I didn't change it).After some googling I found a whacky environment variable that works around this issue.
SDL_GAMECONTROLLERCONFIG
needs to be set to the following value:I'm not sure what the actual problem is but reporting it here in case it can be fixed. Perhaps the above environment variable could be used by default when this type of controller is detected?