Compatibility Report
- Name of the game with compatibility issues: ARC Raiders
- Steam AppID of the game: 1808500
System Information
- GPU: NVIDIA GeForce RTX 2060 Max-Q + AMD Radeon iGPU hybrid setup
- Video driver version: NVIDIA 595.71.5
- Kernel version: Linux 7.0.2-arch1-1-g14
- Link to full system information report as Gist: https://pastebin.com/Dwt3rDmC
- Proton version: Proton Experimental, latest GE-Proton, and Proton-TKG tested
I confirm:
Symptoms
ARC Raiders runs correctly under Proton, but the FSR3 Frame Generation option never appears in-game on Linux/Proton.
This happens even though the log shows that FSR and frame generation related components appear to load successfully:
amd_fidelityfx_upscaler_dx12.dll loads successfully
amd_fidelityfx_framegeneration_dx12.dll loads successfully
- VKD3D detects FSR resources
- NVAPI works
- Reflex latency markers work
- DX12/VKD3D swapchain initializes correctly
Relevant log lines include:
NtGdiDdDDIQueryAdapterInfo type 31 stub
NtGdiDdDDIQueryAdapterInfo type 48 stub
FSR resource detected. Forcing retained GPU reference to work around broken integration code in either game or UE5.
Observed behavior:
- FSR upscaling components load
- FSR frame generation DLL loads
- FSR resources appear active during runtime
- DLSSG / NVIDIA Streamline components initialize but unload shortly afterward
- Frame Generation option never appears in the game UI
This was tested with:
- Proton Experimental
- latest GE-Proton
- Proton-TKG
- NVAPI enabled
VKD3D_FEATURE_LEVEL=12_2
PROTON_HIDE_APU=1
- NVIDIA-only Vulkan ICD
- Gamescope
- latest NVIDIA driver available on system
The issue does not appear to be a local configuration issue. It is reproducible across multiple Linux systems, including another PC, and public reports exist describing missing ARC Raiders frame generation options on Linux.
Theory
ARC Raiders may be querying WDDM / D3DKMT / HAGS-related capability APIs through Streamline or frame-generation capability checks. Proton/Wine appears to stub or incompletely implement some D3DKMTQueryAdapterInfo paths, especially type 31 and type 48, which may cause the game to hide or disable frame generation support despite FSR resources loading correctly.
Potentially related:
Reproduction
- Install ARC Raiders on Linux through Steam.
- Use Proton Experimental, latest GE-Proton, or Proton-TKG.
- Launch with logging enabled:
PROTON_LOG=1 PROTON_ENABLE_NVAPI=1 DXVK_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_HIDE_APU=1 %command%
- Open the game.
- Go to graphics settings.
- Observe that FSR3 Frame Generation does not appear as an available option.
- Check the generated
~/steam-1808500.log.
Expected result
FSR3 Frame Generation should appear and be enableable when the game loads FSR3 components successfully.
Actual result
FSR3 Frame Generation does not appear in the UI, despite FSR3-related DLLs and resources being loaded/detected in logs.
Summerised logs around FSR3/Frame Generation in general: https://pastebin.com/izNADNvw
Compatibility Report
System Information
I confirm:
Symptoms
ARC Raiders runs correctly under Proton, but the FSR3 Frame Generation option never appears in-game on Linux/Proton.
This happens even though the log shows that FSR and frame generation related components appear to load successfully:
amd_fidelityfx_upscaler_dx12.dllloads successfullyamd_fidelityfx_framegeneration_dx12.dllloads successfullyRelevant log lines include:
Observed behavior:
This was tested with:
VKD3D_FEATURE_LEVEL=12_2PROTON_HIDE_APU=1The issue does not appear to be a local configuration issue. It is reproducible across multiple Linux systems, including another PC, and public reports exist describing missing ARC Raiders frame generation options on Linux.
Theory
ARC Raiders may be querying WDDM / D3DKMT / HAGS-related capability APIs through Streamline or frame-generation capability checks. Proton/Wine appears to stub or incompletely implement some
D3DKMTQueryAdapterInfopaths, especiallytype 31andtype 48, which may cause the game to hide or disable frame generation support despite FSR resources loading correctly.Potentially related:
D3DKMTQueryAdapterInfoD3DKMTEnumAdapters2WDDM_2_7_CAPSD3DKMTEnumAdapters2andD3DKMTQueryAdapterInfo(forWDDM_2_7_CAPS) wine#259Reproduction
~/steam-1808500.log.Expected result
FSR3 Frame Generation should appear and be enableable when the game loads FSR3 components successfully.
Actual result
FSR3 Frame Generation does not appear in the UI, despite FSR3-related DLLs and resources being loaded/detected in logs.
Summerised logs around FSR3/Frame Generation in general: https://pastebin.com/izNADNvw