PlayableShow Details
Unknown
gamescope -f -W 2560 -H 1440 -w 2559 -h 1439 -r 144 --force-grab-cursor --mangoapp --backend sdl -- env LD_PRELOAD="$LD_PRELOAD" %command%
As others have already pointed out: Without running the Game in windowed mode or through a very specific gamescope setup, the game freezes either directly after compiling shaders at startup, or when a single key on the keyboard is pressed or the mouse is moved by even a pixel.
Explenation for my commandline arguments:
gamescopeRun the game through gamescope-fThe gamescope window is fullscreen-W 2560 -H 1440The resolution of my monitor - replace this with your values-w 2559 -h 1439The target resolution of the game window - **always use-1of the previous values--force-grab-cursorDoes what it says it does--mangoappOptional, for the mangohud FPS / Performance overlay--backend sdlRequired on my system for some reason, otherwise gamescope itself does not start--End of the gamescope parameters, next is the command for the actual gameenv LD_PRELOAD="$LD_PRELOAD"Avoid this bug%command%The actual game
Any keyboard or mouse input crashed the game. Gamepad use only
The game runs perfect on my pc, and runs just as well on my secondary one after the command workarounds. Just a small annoyance really.
gamemoderun mangohud %command% -ResX=<Monitor Res - 10> -ResY=<Monitor Res - 10> -refresh=<Monitor Refresh Rate> -windowed
On some hardware the game will run fullscreen but freeze when you use your mouse. The only way to make it work is by using -ResX= -ResY= -refresh= -windowed.
On my main pc I did not need this but i did in another.
Mouse freeze on fullscreen game.
Runs well OTB
Borked on Intel Arc B580
Game doesn't start; shows error message: "Your graphics card - Intel(R) Graphics (BMG G21) - does not support all the necessary features to run TheAlters. The following features are missing: - 64-bit atomic"
gamescope -f -W 2560 -H 1440 --force-grab-cursor -- %command%
Any attempt using Keyboard and/or Mouse can freeze the game entirely. input is limited to Xbox Controller, as my testing goes.
Any attempt using Keyboard and/or Mouse can freeze the game entirely.
while Xbox Controller works, the slight bump on Keyboard and Mouse will crash the game, and without running game under Gamescope session, I couldn't make the game work, at all.
prime-run gamescope -f -W 2559 -H 1439 --force-grab-cursor --disable-layers --expose-wayland -- %command%
When my second monitor was active, the mouse would escape out of the game to that monitor when hitting the screen border. Deactivating the monitor while playing fixed that problem.
The game worked with gamescope, but that currently has a bug with hybrid graphics with a dedicated NVIDIA GPU. I adapted a fix from the issue thread detailing the bug in the Github repo (https://github.com/ValveSoftware/gamescope/issues/1590#issuecomment-2825722470) These are the steps if you want to try it (with some explanation for non-techies):
- Clone the gamescope repository, enter the folder and init (basically downloading the gamescope code, entering its folder and updating the metadata, and git is a program used to manage code versions and distribution, and a "repository" is basically a database of code including past versions)
git clone https://github.com/ValveSoftware/gamescope.git
cd gamescope
git submodule update --init
- IMPORTANT: check out commit 1ab8009, since the patches don't work on later commits (a commit is like a version of the code)
git checkout 1ab8009
create the file gamescope_fix.patch in the current folder, paste the script found here: https://gist.github.com/peterambos/f834f42280f5bede44a57c22e869c9b5
same for the file gamescope_meson_fix.patch, found here: https://gist.github.com/peterambos/bc40e77b8f9a60408eee67d945eaa2c3
These patch files basically tell git "hey, please find these lines of code and replace them with the script I have here" so git knows where to put the code in the next step.
- apply the patches to the code
git apply gamescope_fix.patch
git apply gamescope_meson_fix.patch
- build the new code (convert the code into an actual program your computer can run)
meson setup build/
ninja -C build/
- test it (use
nvidia-smito see if the program "vkcube" is actually run by your dedicated GPU, if it isn't look into DRI_PRIME/DRI offloading or commands likeprime-runif your distro has them)
build/src/gamescope -W 1920 -H 1080 -- vkcube
- install it
sudo install -t /usr/bin build/src/gamescope build/src/gamescopestream build/src/gamescopereaper build/src/gamescopectl --strip
This is running an older version of gamescope that is not automatically getting updates! Make sure to check if the bug is fixed in later versions, and if yes, go back to the official version! The best place to check is probably the link to the issue thread I posted at the top.
The game is perfectly playable without issues as long as you are not running it in fullscreen mode.
I use KDE's Window Rules to disable the window borders and 'almost' set the window resolution to fullscreen. This is a workaround for the crashing on fullscreen with keyboard/mouse issue.
When the game is running in fullscreen mode and you use keyboard/mouse input, the game will freeze.
This game really does not like keyboard/mouse input in fullscreen mode.
This game requires some tinkering. Unless you are not touching your keyboard/mouse (not even by accident) you can play this game without tinkering. Most people on PC probably won't though, so I cannot recommend playing this game in fullscreen.
Borked ( Crashes/Freezes on Title Screen ) :(
Game seems to have Issues with mouse movements, it Crashes/Freezes on the title Screen when moving the Mouse. Tried different Proton Versions including Proton Hotfixes, Proton Experimental, Proton 9.0-4 and Proton-GE 10-4.
gamemoderun %command% -ResX=2559 -ResY=1430 -force-grab-cursor -expose-wayland -windowed
Crashes the game
Mouse or KB movement crashes the game when fullscreen
gamemoderun %command%
Fresh Arch install with zen kernel, manually installed nvidia drivers for kernel, configured and game runs flawless. No lock ups with mouse or keyboard, fullscreen straight from the start.
%command% -ResX=2520 -ResY=1420 -windowed
Windowed Fullscreen does not work, tinkering enables Fullscreen
After a while game becomes laggy
Game somehow causes steam to crash after a while, getting an achievement then crashes game
Had to start the game initially as windowed with -windowed, then change to fullscreen and restart, on every next startup alt + enter is needed to switch to fullscreen
Maybe ensure your swap file is big enough to handle shader caching or be prepared to delete the shader cache from time to time.
Could play for a few hours, then game started freezing. Some times the game continues after a few seconds, some times I had to kill the game and start again. After many hours of swapping proton versions and jumping between my Manjaro PC and the Bazzite handheld, I found that deleting shader cache folder fixes it for a few hours.
%command% -ResX=2559 -ResY=1439 -windowed
Any KB/Mouse input makes game freeze completely in fullscreen and even windowed fullscreen. Need to start game with your resolution minus 1 for each dimension
Playing with Proton 10, minor artifacts sometimes but works great OUTB.
gamescope -f -W 1920 -H 1080 --force-grab-cursor -- %command% -windowed
Gamepad works flawless. Mouse boundaries are not correct.
Might be playable if you use controller and keep your mouse cursor in the bottom-right. Otherwise, completely unplayable.
Everything to the bottom-right of the mouse cursor never updates. Turning vsync off makes it sort of update, but very behind the rest of the screen.
Tried using other versions of Proton and switching between windowed, windowed fullscreen, an fullscreen, but nothing resolved the issue.
gamescope -f -W 3439 -H 1439 --force-grab-cursor --expose-wayland -- %command%
The quality of the water looked odd in comparisson to the rest of the game.
As of posting this report, using any mouse or keyboard breaks the game. Only when using Gamescope (and enable wayland for wayland users) is there no need for the windowed command on proton
It runs
I've gotten to the elevator and into the base. Game runs fine but no long playtests yet to see if the game cashes.
Borked input
The reason why it (mostly) works on the steamdeck is because there are no mouse/keyboard inputs. I used a BT mouse and the game hangs immediatly without the compatability options.
Mouse+Keyboard causes it to crash at the main menu, but works perfectly with a controller
The game would not load into the menu if using a resolution greater than 1080p AND using keyboard+mouse. I tried every proton version, but what allowed me to finally start playing was turning on my controller and using only that if I wanted to play at 1440p.
Mangohud also caused it to crash if I tried turning it on.
vcrun22
Install vcrun22 because I got errors without them
The game thinks im using novideo driver 999.99, the game runs great with no issues. DLSS and FSR both work fine
%command% -windowed
Game crashed in full screen mode
Game didn't start with any proton modes or switches I tried. I had to lower my screen resolution to 1920x1080 (or lower) to make it playable. After that all works smoothly.
gamescope -f -W 3439 -H 1439 --force-grab-cursor -- %command%
I've played the game so far without any issues using a controller. But after further testing I finally managed to make the mouse and keyboard work by using gamescope. Just set the launch parameters above and adjust the -W and -H to your monitor resolution minus 1.
UE5 tries to fix low perfomance with alot of scaling, but it looks bad
Crashes between acts. Not critical.
Playing the release version
Deck controls - no issues
I've got 45-50 fps on totally default graphics on steam deck. It's low settings with TSR. Looks very bad.
Sound can clip a bit sometimes.
I've got a game freeze while getting to the Base first time.
Switched to proton experimental and got game crash at the same moment. Crash happens after save, so it is not a big problem.
Switching TSR to FSR3 did not raise performance, but image became less crappy.
I would recommend turn on FSR3 Frame Gen, got 60-70 fps without visual degradation with FSR3 Balanced on low
Playable state on Deck, still fun to play.
It just works OOTB
Was really expecting a ton of issues, given the game is rated Silver at the moment. A lot of people are complaining about crashing when using KB/M or complaining about other random crashes and glitches.
So far, I've played for 2 hours, performance wise, framerate is above Windows 11 for me, no crashes and keyboard and mouse works, just like Xbox Gamepad also work.
I guess I was just lucky given the ammount of tinkering reports I have read or issues.
Flawless
Played the entire game with no issues whatsoever. No special treatment needed, just install and go.
Freeze before main menu
I don't understand how the demo can work so well, but they won't fix the main game. Even on SteamDeck the game has brightness/alpha and crash issues.
The game doesn't work perfectly but is playable overall if you don't mind occasional artifacts.
gamemoderun %command% -windowed
Cursor window glitches in-game
The game freezed on some occasions though with the current configuration that I use I haven't noticed any freeze yet.
Graphic settings in my current configuration (didn't encounter any freezes yet, only cursor glitches):
- Fullscreen
- NVIDIA DLSS (with Low Latency and Frame Generation DISABLED)
I also switched the NVIDIA PRIME profile to NVIDIA (Performance Mode)
Game opened in window works well with mouse and keabord, I'll try it later with controllers in fullscreen mode.
%command% -ResX=1920 -ResY=1080 -windowed
Game needs to be opened in window with 1920x1080 resolution
For now game opened in window works well with mouse and keabord, I've played ca. 3 hrs, I'll try it later with controllers in fullscreen mode.
use -windowed in start parameter, start the game and use it in window mode and simply maximize the window
-windowed
Fullscreen and Window-Fullscreen not work without startparameter: -windowed
It would be good for the developer arrive 2025 and develop games with linux support.
Not sure if it was a patch or just not alt-tabbing, but game worked fine windowed and not switching workspaces
gamemoderun %command% -windowed
Full screen crashes and no longer works
Game would freeze when running above 1080p resolution.
Game would freeze when entering the menu screen by pressing ESC
Possible Workaround:
- Set the Bottle's Renderer to Vulkan (Settings -> Advanced Display Settings -> Renderer -> Vulkan)
- Enable Virtual Desktop (to get to the menu screen), go to graphics settings and set to Full Screen and 1280x720, Apply
- Exit Game
- Disable Virtual Desktop
- Launch Game and set Graphics to 1080p.
Game has run fine for me this way, including opening the menu with ESC
No issues, just put my normal launch options I use for every game, hit play, and it worked.
__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 game-performance %command%
-windowed
Going into FullScreen WILL cause the game to hang. The game must launch and stay in Windowed mode.
Using Keyboard and Mouse WILL cause the game to hang 90% of the time. Using a controller will allow the game to function properly.
Using a keyboard and mouse will, 90% of the time, cause the game to freeze and must be force-closed. Attempting to interact with the game with KB&M while the intro videos are playing will also cause the game to freeze.
If you have a controller, use it, as this game just really hates KB&M input from Linux.
