I've just confirmed unplugging the keyboard does not resolve the issue.
@rudi4463 did you find a solution?
@PATAPOsha if you're still struggling, try using
SteamDeck=0 %command% on game properties
I have the same issue
@PATAPOsha if you're still struggling, try using
SteamDeck=0 %command%on game properties
This fixed it for me!
Hi folks - if anyone is still seeing this issue and needs to use SteamDeck=0 to "fix" it - could you please give me some more details? We tested the game on a Linux desktop with a mouse+keyboard and a Xbox1 controller plugged in, and the game is behaving exactly how it does on Windows. Could you please:
I'm having this issue on Steam Deck.
Issue happens every time I play while docked.
Issue occurring both with a ROG Ally dock and a Green dock.
Issue occurring both with Xbox controller connect over Bluetooth and 8bitdo controller connected via 2.4g usb dongle.
Suggested fix did not work. Deleting the config.txt file from the game files for this game usually makes it work as normal temporarily but issue will reoccur next time game is launched.
Deleting and reinstalling game did not help.
Changing controller order in steam input did not work.
Issue occurs when launching game as normal by pressed A on controller.
SteamDeck=0 %command% on game properties
This option helped (Bazzite in HTPC mode on mini PC)
Thank you
@alasky17 I've experienced this issue with various versions of SteamOS and Bazzite. Usually I have no keyboard connected, only the Xbox 360 USB dongle for wireless gamepads and sometimes a couple of BT gamepads.
It doesn't seem to be 100% deterministic to me (but close): At one family gathering (before learning about the SteamDeck=0 fix) we kept rebooting the Deck and our controllers many many times, and sometimes the game worked. I've also run into a variation of this bug on Windows once, but there it seems to be the absolute exception.
I love this game to death, especially its coop mode. If there is anything I can do to debug this, please let me know.
I've just encountered the same issue again. I've tried the latest SteamOS recovery image with all preview/beta updates, on an AMD HTPC (I know, not yet supported). The only connected peripheral was an Xbox 360 wireless controller dongle.
Sackboy showed player 1 with the keyboard icon. The two controllers then controlled player 2 and 3, with no way to start the game.
I have applied the SteamDeck=0 workaround, restarted the game, and the first player was properly controlled by the gamepad.
Probably already tracked internally by Proton devs, but just in case, DualSense audio-based haptics do not work. Furthermore, performances gradually decline over time when playing with DualSense, most probably due to how the game repeatedly tries to connect to the DualSense's audio output.
@ClearlyClaire Thank you for mentioning this one! If you know of any other games where the DualSense haptics are still broken, feel free to @ me in your comment. And thank you for your work to help implement this feature :D
@alasky17 off of the top of my head: Ratchet & Clank: Rift Apart, Death Stranding: Director's Cut, and Monster Hunter: Wilds are all games in which the DualSense audio-based haptics don't work through Proton. MH: Wilds may be significantly different because it relies on Steam Input? But you more likely know more than me in that regard. Also, Deathloop can be made to work by preventing it from using XAudio2. Would be good if it worked out of the box, but this sounds like massively more work.
@ClearlyClaire Thank you so much for the list and details! 🙏 We will look into those and see what we can do :)
_SteamDeck=0 %command%x1 2024-09SteamDeck=0 %command%x2 2024-05
Compatibility Report
System Information
I confirm:
Symptoms
When launching the game there is always a default Keyboard and Mouse player 1 so there is no way to play player 1 with a controller effectively making the game for single players keyboard and mouse only and in koop one has still to play with the keyboard. I haven't tried this yet but unplugging the keyboard might fix this... naturally just unplugging the keyboard to play a game is not the way it should be intended to be. (This might also be the reason why steam deck users to not encounter this issue since they do not have a keyboard that could be detected and/or unplugged)
Inside the settings there is a button for the keyboard to change it's user slot and therefore theoretically switch the first position with a controller making it playable with a controller but the button is set to none and it cannot be changed neither ingame nor in any configuration file.