protonscr

Fatekeeper

protonclosed appid 2186990Game compatibility - UnofficialXAudio2
ValveSoftware/Proton#9868 · opened 2026-06-10 by JimLahey08 · updated 2026-06-10 · 4 comments · github · game page · search this game
JJimLahey08 2026-06-10 github

steam-2186990.log

Compatibility Report

  • Name of the game with compatibility issues: Fatekeeper
  • Steam AppID of the game: 2186990

System Information

  • GPU: Nvidia 5090
  • Video driver version: 610.43.02
  • Kernel version: 7.0.11-1-cachyos
  • Link to full system information report as Gist:
  • Proton version: Experimental

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

Symptoms

With no launch options, the game briefly shows a small image while launching then goes to a black screen and hangs. Adding the descriptor heap launch option doesn't seem to fix the issue.

Reproduction

Just attempt to launch the game on Nvidia 5000 series on CachyOS/Linux

Computer Information:
Manufacturer: Micro-Star International Co., Ltd.
Model: MAG X870E TOMAHAWK WIFI (MS-7E59)
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 9800X3D 8-Core Processor
CPU Family: 0x1a
CPU Model: 0x44
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 5271 MHz
16 logical processors
8 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Supported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported
Operating System:
CachyOS (64 bit)
Kernel Name: Linux
Kernel Version: 7.0.11-1-cachyos
X Server Vendor: The X.Org Foundation
X Server Release: 12401012
X Window Manager: KWin
Steam Runtime Version: steam-runtime_1.0.20260430.230225
Client Information:
Version: 1780352834
Browser GPU Acceleration Status: Disabled
Browser Canvas: Unavailable
Browser Canvas out-of-process rasterization: Disabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Disabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Disabled
Browser Rasterization: Disabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Disabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Unavailable
Browser WebGL2: Unavailable
Browser WebGPU: Disabled
Browser WebNN: Disabled
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce RTX 5090/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 610.43.02
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 239 Hz
VendorID: 0x10de
DeviceID: 0x2b85
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 27.52" x 15.55" (31.57" diag), 69.9cm x 39.5cm (80.2cm diag)
Primary VRAM: 32607 MB
Sound card:
Audio device: Nvidia GPU aa HDMI/DP
Memory:
RAM: 31455 Mb
VR Hardware:
VR Headset: None detected
No VR configuration with trackers detected
Most number of trackers in a session: 0
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 3813397 MB
Largest Free Hard Disk Block: 3154458 MB
Storage:
Number of SSDs: 2
SSD sizes: 4000G,0B
Number of HDDs: 0
Number of removable drives: 0
JJimLahey08 2026-06-10 github

Changing proton versions doesn't seem to help, nor does adding heaps launch option on bleeding edge.

Kkisak-valve maintainer 2026-06-10 github

Hello @JimLahey08, looking around a bit it looks like this game generally works for most players. This hints that there's an additional factor involved for you. Blind guess, does taking lsfg-vk out of the mix have an effect?

JJimLahey08 2026-06-10 github

Hello @JimLahey08, looking around a bit it looks like this game generally works for most players. This hints that there's an additional factor involved for you. Blind guess, does taking lsfg-vk out of the mix have an effect?

It shouldn't be applied to the game since I don't have any steam launch options enabled for this game. You have to add a profile in LSFGVK-UI and add a steam launch command like LSFG_PROCESS="Fatekeeper" to enable it. I saw a few protondb entries saying the game wouldn't run for them but they were sparse on hardware details. It seems AMD and some Nvidia cards like the 4000 series run it just fine.

I can look into uninstalling lsfg-vk to see if that helps, but I'm hoping that's not the root cause.

JJimLahey08 2026-06-10 github

Hello @JimLahey08, looking around a bit it looks like this game generally works for most players. This hints that there's an additional factor involved for you. Blind guess, does taking lsfg-vk out of the mix have an effect?

So you were right. Even though I didn't define the launch option for lsfg-vk for this game it still detected the process "Game Thread" and tried to run lsfg-vk. I deleted the Game Thread profile from lsfg-vk that I had for another game with the same price name and now the game launches. Thank you!

Nothing extracted yet.