DXVK on Android with Winlator and GameHub

How Winlator runs a Windows game

Each box does one job:

          1
          game.exe            the Windows game
          
          
          
        
          2
          -> Wine           lets Windows programs run on a non-Windows system
          
          
          
        
          3
          -> Box64          translates x86 code to the phone's ARM code
          
          
          
        
          4
          -> DXVK           turns Direct3D calls into Vulkan
          
          
          
        
          5
          -> Vulkan driver  Turnip on many Adreno phones; a vendor driver
          
          
          
        
          6
                            or a translation layer (Vortek, PanVK) on Mali
          
          
          
        

DXVK is only one of four layers. A crash can come from any of them, so a game failing is not proof that DXVK is at fault.

Which DXVK version for your phone’s GPU

The DXVK 3.x requirement matters here: it asks for a Vulkan 1.4-class driver with listed extensions, and DXVK 2.x needs Vulkan 1.3 (requirements page). Our lab driver reported 1.3 and still ran 3.1.1, because DXVK checks features, not the version number (F33). So the version on the label is not a verdict either way: use the HUD or log on your phone.

To find your GPU: Settings, About phone, then the processor name, or any Vulkan-info app. Adreno names start with Adreno plus a number; Mali with Mali-G.

What is a .wcp file?

A .wcp file is a component package used by Winlator-family apps. It holds a build of DXVK (or another component such as a graphics driver). The app unpacks it and lists it in its settings.

Switch the DXVK version in Winlator

The menus differ between Winlator versions and forks, so treat these as the general shape, reported by guides:

GameHub and other launchers

We have not used GameHub. Launchers in this family handle components differently: some choose DXVK for you, some hide the setting, some use their own driver packages. If no DXVK setting exists, you cannot change it from the app.

DXVK settings that matter on phones

• Frame cap. DXVK_CONFIG=dxvk.maxFrameRate=30 works as an environment setting on desktop (F22); put it in the container’s environment variables. See Limit FPS.
• Low VRAM refusals. d3d9.maxAvailableMemory changes the memory a Direct3D 9 game is told (F25). See VRAM and memory. It does not add memory.
• HUD. DXVK_HUD=1 shows the version and device, which is the quickest diagnosis (HUD page).

When nothing works

For Direct3D 12 games see DXVK vs vkd3d-proton.

Before you ask for help, note the app and its version, the GPU and driver (Turnip version), the DXVK version, and the game’s graphics API. Ask in the app’s own community, not DXVK’s GitHub.