
dataphract
Published
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command%
Starting the game using RADV causes the options menu to not work: the cursor movement sound plays on loop and the menu cannot be backed out of, nor can any options be changed. Starting with AMDVLK resolves the issue.
Set game to fullscreen by setting the following in config.ini:
[RenderConfig] FullScreenDisplayMode=<monitor's native resolution and refresh rate> FullScreenMode=true WindowMode=FullScreen [AppOption] WindowMode=FullScreen Resolution=<monitor's native resolution>
Game continually changes window resolution and jumps between monitors during startup. After that, window seems fine.
Options menu doesn't work. The categories on the left can be browsed, but the actual settings don't respond to mouse or controller input. In the options menu, the game makes a continual clicking sound as though repeated inputs are being received, but they continue even with no input devices connected. The rest of the game appears unaffected.
vk_amdvlk %command%
Alt-tabbing out and back into the game window causes the OS mouse cursor to permanently show in the middle of the window. Requires a restart to get the cursor to go away.
Default Proton results in a hard segfault as soon as the game launches.
Proton Hotfix with RADV driver results in graphical artifacts.
Proton Hotfix with AMDVLK is completely stable with great perf (~90fps @ 1440p Ultra). vk_amdvlk
(from the Arch AUR package amd-vulkan-prefixes
) is equivalent to setting VK_DRIVER_FILES="/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json
.
Not perfect, but generally quite stable and the game's generous autosaving makes the occasional crashes largely a non-issue.
Audio missing from initial-run cutscene.
Two crashes in two hours, both triggered by cutscenes. Game becomes unresponsive, and a debug dialog appears after two minutes indicating that the rendering thread has stopped responding.
Consistently crashes after every achievement, requiring all major bosses to be beaten twice as the crashes occur before the game can autosave. Some other crashes of unknown cause.
Works more or less perfectly 99% of the time, but the satisfaction of beating a difficult boss is a bit dampened by the game immediately crashing and losing that progress.