
Hakushaku
Published
Crashes in loading screens with FSR Frame Generation enabled.
Without frame generation the framerate can be low on high settings. Toggling it off before loading screens is not reliable as you don't know when there will be a loading screen.
Manual redistributable installation
Works quite well for me so far. No issues besides the required manual redistributable installation.
Occasionally audio freezes shortly or crackles
Switching to fullscreen crashes the game
Frame drops in certain areas. Tuning of graphics settings required.
The game seems to run fine so far. Although with some smaller issues that are noticable but not game-breaking. I had issues with the character creator with regular Proton so I didn't even bother testing that. Will update if I find other problems.
Switching to fullscreen crashes the game. Borderless works fine.
WIth GE Proton 9-1 even the options menu works.
DXVK_HDR=1 gamescope -b -W 5120 -w 5120 -H 1440 -h 1440 -r 120 --hdr-enabled gamemoderun %command%
The demo worked fine for me with decent performance. Just enabling frame generation made it slow down significantly and cause visual artifacts.
PROTON_BATTLEYE_RUNTIME="/home/nifl/.local/share/Steam/steamapps/common/Proton BattlEye Runtime/" SteamDeck=1 gamemoderun mangohud %command%
Game will randomly get stuck at the launcher
The terrible launcher and anti-cheat make it difficult to get the game to run without issues on Linux. Can not consider this enjoyable for the average user in its current state.
gamemoderun VKD3D_CONFIG=dxr %command%
The audio occasionaly mutes for around half a second
Crashes randomly when fast-traveling
Raytracing options are greyed out regardless of tinkering on newest mesa driver. The crashes also happen on Windows, but seem to be more common on Linux. Probably due to some VRAM overhead from DXVK. The game runs fine for me on ultra settings at 5120x1440. I had FSR2(Quality) enabled, but the image quality stayed decent at all times.
Unplayable for me
Crashes wihout stating any error completely randomly but very frequently. Tried different Proton versions and other fixes without any improvement of stability.
Unplayable with music most likely due to XAudio2_8 compatibility issues
Music fails and freezes the game after ~7 track switches. Music with vocals doesn't work at all.
Tried several workarounds, but nothing changed the result. The music player stops playing music after switching the track ~7 times. Vocal songs don't work at all. And the game crashes after a few screen transitions (probably due to audio track switching). Game is "playable" without music (if you delete the files like others suggested) but that is not a valid solution to me.
WINEDLLOVERRIDES="xaudio2_8=n" %command%
FAudio is broken for this game. Downloaded XAudio2_9, renamed it to XAudio2_8 and forced wine to use that. No crashes and all music plays normally that way.
Doesn't start due to broken EAC implementation
Unlike other EAC titles this relies on the Epic Service rootkit being installed on the system. The existing EAC compatiblity layer does not work with this, preventing it from running on Linux at all. People that got it running probably had an old version of the game. As of this moment it is unsupported on Linux even if you want to play single player.
Crashes on videos if resolution is higher than 1080p
Requires GE-Proton due to Windows Media Foundation
AMD_VULKAN_ICD=AMDVLK VKD3D_CONFIG=dxr11,dxr gamemoderun %command% -autoconfig -sw
Artifacts when volumetric lighting was enabled
Had to tinker with the raytracing settings to get stable fps
DXVK_HDR=1 gamemoderun gamescope --hdr-enabled -rt --adaptive-sync -f -W 3440 -w 3440 -H 1440 -h 1440 -r 120 -- %command%
Constant stutters
Due to the severe stutters, the game is unplayable on more than adequate hardware.
With GE-Proton8 and regular Proton the videos didn't work for me. With GE-Proton7 video works fine and the game runs well.
At first the game wouldn't launch. Tried multiple times. Tried restarting steam. It started working after I switched to Experimental. Then it also worked on GE. Back when the game was released I didn't have this issue, so I assume it has to do with a Steam client update.