DXVK forks and related projects

Fork family tree

          1
          upstream DXVK  ---------------------------------------------->  3.x (current)
          
          
          
        
          2
          |-- 1.x ---- dxvk-async (archived) ; Sarek and Gcenx macOS branch off the 1.10 line
          
          
          
        
          3
          |-- 2.x ---- dxvk-gplasync (tracks 2.x with GPL)
          
          
          
        
          4
          |-- (older base) ---- dxvk-remix (NVIDIA RTX Remix runtime)
          
          
          
        
          5
          |-- Valve's tree: proton_X branches, used to build Proton
          
          
          
        

dxvk-remix (RTX Remix)

This is the one fork with no page of its own here. Per its repository it replaces the Direct3D 9 fixed-function pipeline with a path-traced renderer so modders can remaster old games with NVIDIA’s RTX Remix toolkit. Games that use it need an NVIDIA RTX GPU, which we know from NVIDIA’s documentation, not from testing. Do not mix its DLLs with upstream DXVK’s in the same folder: one file name has one owner (conflicts). Go to NVIDIA’s own documentation for use.

DXVK-Sarek

Sarek keeps the 1.10 line working for GPUs that cannot meet newer Vulkan requirements. Details and risks are on the 1.10.3 and Sarek page.

dxvk-async and dxvk-gplasync

The original async patch is archived; gplasync is its 2.x successor. Neither is part of official DXVK, and DXVK_ASYNC does nothing there. See DXVK async and gplasync.

Mac builds (Gcenx)

A fork on the 1.10 line for macOS through MoltenVK. See DXVK on macOS.

Valve’s DXVK tree for Proton

Valve keeps a tree with proton_X branches that Proton is built from, so the DXVK inside a Proton version can differ from the newest upstream release. See DXVK in Proton.

Other forks you may see

HDR forks, low-latency variants of gplasync and Lutris’s old DXVK fork exist. We have not looked at them closely. The generic advice below applies to all.

How to judge a fork