VerifiedShow Details
Unknown
MANGOHUD_CONFIG=full,no_display WINEDLLOVERRIDES="dinput8=n,b" mangohud %command%
Since this is originally a Switch game, and runs on the RE Engine on DX12, the game runs and performs very well, as expected. You might want to include REFramework as usual (among other things, it can unlock the framerate in cutscenes, which are otherwise bizarrely locked to 30fps), just don't forget to include the WINEDLLOVERRIDES.
The out-of-the-box and official version of Proton works very well, practically identical to the Windows version in terms of performance, however using Proton GE 9-27 it has been running with a 20% increase in FPS.
WINEDLLOVERRIDES="dinput8=n,b;winmm=n,b" mangohud %command%
REFramework is installed for mods (RiseTweaks, BetterMatchmaking, NoKillCam+SlowMo, UI_Scaler).
I previously install REFramework Direct2D but it causes fps loss so I had to remove it and mods that requires it.
DLL overrides are for enabling REFramework & creamAPI hook (winmm.dll) for unlocking cosmetic DLCs.
Works perfect
Runs great overall, no difference from Windows.
Steam input had to be disabled on game properties for gamepad to work.
Seems to be working well for me, with no tweaks. Two crashes in about 16 hours, though I feel may be because of current, unoptimized state.
Some freezing, though I feel it may be because the game is unoptimized currently
Crashed twice so far
Activating certain objectives crashed the game and caused intense graphical errors
Works out of the box perfect on GE Proton 9-23. Even installed mods and those worked perfectly without issue.
gamemoderun WINEDLLOVERRIDES="dinput8.dll=n,b" PROTON_USE_DXVK=1 %command% -dx11
at first give me a black screen only, then I use only this command and let me play: PROTON_USE_DXVK=1 %command% -dx11 after the first successful run I was able change all commands, no issues in game so far
Only Proton 8.0-5 worked fine for me. Other Proton versions either gave me performance issues that slowed down my entire system, or intense texture glitches.
Screen flickering on Wayland is caused by a variable in the config file. Go to the game folder, open config.ini, and change "WindowModeOption" to 1. Fixed the issue for me and the game works perfectly. Changing the option in-game did not work, as it would instantly revert to the default option.
UI/Texture flickering
game flickers constantly, it's a heavy epilepsy hazard, settings revert instantly, game stuck in windowed mode
game flickers heavily, from the splash art to the main menu, if i was epileptic i would have had a seizure
not only was it stuck in windowed mode, settings claims vehemently that it's fullscreen and it's stuck that way impossible to change
options menu doesn't work, settings revert instantly
somewhat losing my mind with so many people saying it runs flawlessly, this is a nightmare
Just works!
Install and Play!
Works like native.
Happens rarely but the game would practically freeze as it tanked to sub-zero frames per second, making the game unresponsive and forcing the player to close the game.
I tested in multiple proton versions apart from this one and they all eventually had the same problem where the game's framerate tanks and becomes unresponsive. The only difference between versions is that some had more graphical artifacts than others.
Too much flickering assets. The characters and monster still appear as normal, but everything else keeps flickering, including the ground.
Lots of flickering assets, including ground areas.
Had to disable Steam Imputs for the controller to be detected.
At first, the game did not opened even tho Steam said it was running, so I had to close it through the "stop" button and re-open it.
Couldn't open the game through Proton Hotfix and Proton GE opened the game but have me a black window.
Colisions still work as intende, so the game is still playable if you really want too, but the ground flickering is too much for me.
Map became sort of invisible and spazzed out while buildings stayed the same.
Maybe it's a proton GE issue? Haven't tested alternatives.
130~ hours in - had zero issues. REframework mods also work on steam deck.
TDP to 10 watts, GPU clock to 900
Had artifacting during sunbreak final boss, never appeared anywhere else
In advanced graphics settings, make sure image quality is 100% and not 150% as this was causing stuttering. Most other settings are up to you and matter more for battery life than framerate. Lowering resolution and having FSR on can help, but can also make text harder to read
WINEDLLOVERRIDES="dinput8.dll=n,b" %command%
Using protontricks to use Fluffy Mod Manager
Slight performance hiccups at the start, but after a while it runs fine.
Trying to run the game with the command line changes to hook the dinput8.dll for REframework, but then the game gives me an error saying my GPU isn't compatible with the game. It'll boot up just fine without the command line change.
In some fights, the music audio is missing (and I noticed that it seems to be exclusive to the monster Khezu).
The Flooded Forest location is extremely poorly optimized. Frequent stutterings regardless of the selected graphics settings.
Played with Proton-Experimental [bleeding-edge] in High settings (only Shadow option in Medium to avoid stutterings), 1080p windowed fullscreen with 60 FPS stable (cutscenes are 30 FPS locked).
Nvidia DLSS off because I didn't need it, and reporters on the game's forums indicate that this on, ruins the monster's fur.
Played the entire base game and your expansion Sunbreak.
It's an excellent game.
Another heavy hitter that works on linux!
Sunbreak's Hub Area Floor went missing, didn't impact gameplay though.
60fps
Fetal Error D3D (6)
The game opens and show all the start credit and then after the first loading screen it crashes with an error "Fetal Error D3D (6)". At first I thought it was something to do with wayland, so I switch to x11 but nothing. After that I try to switch proton version but still nothing. Finally, I try to change the config file so that the game ran with DX11. and I added the -dx11 launch option. I also try launch option "WINEDLLOVERRIDES="dinput8.dll=n,b" gamemoderun %command%" but still got the error. If anyone can help me with this I will be happy. For now, the game doesn't run. I will update if I find something new.
WINEDLLOVERRIDES="dinput8.dll=n,b" mangohud gamemoderun %command%
Multiplayer and mods work without issue. The WINEDLLOVERRIDES var enables REFramework to hook the game and enable mods.
Occassionally during a hunt the game slows down and rubberbands back.
Disable dynamic shadows for higher FPS. I was able to get 50 on a 1440p external monitor at native resolution, and stable 60 with no dips at 720.
WINEDLLOVERRIDES="dinput8=native,builtin" %command%
I had a very consistent spike in frametimes every 6 seconds or so.
In case anybody is experiencing a very consistent spike in frame times on regular intervals, and is also having very long steam startup times; your hostname or loopback-aliases having a hyphen might be the issue, as it was for me.
Try launching steam from the terminal, and if something along the lines of 'src/steamUI/webuitransportcontroller.cpp (206) : Failed to connect to websocket' appears after the ui finishes loading; try to do what is suggested in this thread https://github.com/ValveSoftware/steam-for-linux/issues/10879#issuecomment-2171168395 .
Aside from modifying the aliases of my loopback interfaces in /etc/hosts, I also changed my /etc/hostname file in order to match my hostname with my aliases.
Ubuntu users: install steam from flathub NOT from the default app store. The game will not start if you run otherwise. Game runs perfectly after doing the above. Fluffy Mod Manager 5000 also works. Follow the instructions on the pinned comment in the posts tab. Minor audio glitches every ~20 mins or so.
No controller rumble. Might need additional tinkering to fix
Larger framedrops compared to windows when there are a large number of particle effects on screen
