HikariKnight
Published
Game work flawlessly after the latest update which fixed the only Proton specific bug (unresponsive controller input in the menus only)
If your session is a window manager only, then you will need to press your hotkey to put applications into fullscreen to get proper fullscreen working without an offset, this is not an issue in traditional Desktop Environments
You must tell the game to not load their GameCube Controller library to avoid crashing, see the customizations for how to do that.
The developers use a libusb library for C# (in order to make GameCube controllers work) that is not compatible with Proton/Wine, they have made an option to disable it by making a file named "nogcc.setting" and place it inside the game folder (the one that contains UnityPlayer.dll) They might make it into a launch parameter in the future
The game (in earlier pre-alpha stages) has been hit and miss if it worked in proton/wine for people on different systems, our small linux community has not been able to nail down why, but it might be because of some missing packages, drivers or minor configuration differences between distributions. I have personally not been able to reproduce the issue on my 4 test machines.
As long as you do not want to use a Nintendo Gamecube or Steam Controller, you will be pleased with this game
Open Alpha accidentally pushed a non existent "linux" version, there is no linux version (at least not now, not sure if devs will make one later) so you need to force the game to run in proton (go to properties and force a specific version of proton in the compatibility section) NOTE: you only need to do the above if you are told the game is missing an executable.
The game also requires you to turn off its custom Nintendo Gamecube Controller support, as it breaks the game in proton (devs added this as a workaround for us linux users).
- Go to the Local Files tab and browse the game files.
- Create an empty file and name it
nogcc.setting - Start the game (using proton) from steam
Only the steam controller had issues.
xbox360/xbone, PS3/PS4, etc controllers worked fine and had no issues
Disclaimer: all controllers tested in wireless mode
VKD3D_FEATURE_LEVEL=12_0 SteamDeck=0 XKB_DEFAULT_LAYOUT=no gamescope -f -w 2560 -h 1440 -W 2560 -H 1440 -e -- %command%
If you like using Steam Input, the game forces you to use the official layout (or a layout based on it) that uses ingame actions instead of controller buttons, which the developers commonly forget to update, running the game through nested gamescope (gamescope in desktop mode) for some reason lets you utilize normal Steam Input layouts that are based on normal gamepads instead which work a lot more reliably.
SteamDeck=0 will disable steamdeck/BPM detection when in desktop mode, it will not work in gamescope-session/gamemode-session, only in desktop mode and lets you freely switch between keyboard+mouse and controller as it disables all the Big Picture Mode integration
XKB_DEFAULT_LAYOUT=no will let you set the physical keyboard layout for gamescope (mine is set to norwegian) however on some layouts not all keyboard levels work YMMV
