Which GPU DXVK uses, and how to change what the game sees

What is your situation?

• I just want to see which GPU DXVK picked
• My laptop uses the wrong GPU
• My game says the card is unsupported
• I want DLSS or NVAPI on Linux
• Does DXVK work with my NVIDIA, AMD or Intel GPU?

See which GPU DXVK picked

Two places show it. The HUD item devinfo (included in DXVK_HUD=1) prints the GPU name and driver in the corner of the game (HUD page, F18). The log prints a Found device: line for each GPU DXVK found; this is the exact text to copy into a filter.

          1
          info:  Found device: llvmpipe (LLVM 20.1.2, 256 bits) (llvmpipe 25.2.8)
          
          
          The name to match. A real card reads like "NVIDIA GeForce RTX ..." or "AMD Radeon ...". You only need a distinctive part.
        
          2
          info:  Creating device:
          
          
          
        
          3
          info:  llvmpipe (LLVM 20.1.2, 256 bits):
          
          
          
        

Under Wine the log goes to the terminal; on Windows it needs DXVK_LOG_PATH set (environment variables).

Laptops with two GPUs

If the game runs on the integrated GPU, work through these in order, stopping when the HUD shows the right card.

1. Tell Windows. In Windows settings, System, Display, Graphics, add the game’s exe and choose High performance. This is Windows’ own setting and we have not tested it with DXVK.
2. Hide the integrated GPU in DXVK. Add to dxvk.conf:

   dxvk.hideIntegratedGraphics = True

   It hides integrated GPUs when a dedicated one is present (since 2.3.1). The file’s own comments say the filter below is preferred.
3. Filter by name. DXVK_FILTER_DEVICE_NAME=RTX (a part of the name) or, in dxvk.conf, dxvk.deviceFilter = RTX (since 2.4).
4. Filter by UUID if two GPUs have the same name: DXVK_FILTER_DEVICE_UUID takes the 32-digit Vulkan device UUID (since 2.6.2).

On Linux the usual way to choose a GPU is outside DXVK: Mesa’s DRI_PRIME=1, or NVIDIA’s __NV_PRIME_RENDER_OFFLOAD=1 with __VK_LAYER_NV_optimus=NVIDIA_only. These are widely documented but we have not tested them; see the Linux page.

Old games that reject new or Intel GPUs: vendor spoofing

Many old games ship a list of graphics cards they know, and refuse or lower settings for the rest. Examples reported by users are Fallout 3 failing on an Intel Arc card (upstream issue 3029) and the card database in The Sims 3. DXVK can report a different vendor, device ID and name.

d3d9.customVendorId = 10de
d3d9.customDeviceId = XXXX
d3d9.customDeviceDesc = "Name of a card the game knows"

Use the dxgi. versions of the same three options for Direct3D 10 and 11 games. We proved the vendor part: d3d9.customVendorId = 10de and dxgi.customVendorId = 1002 changed the vendor ID the test program saw (F27). We did not test the device ID or the name.

The device ID should belong to a real, older card the game knows; a made-up pair can break rendering. We publish no tested vendor and device pairs yet. The built-in profiles already do this for some games (the one for The Sims 2 sets a GeForce 7800 GTX identity); see how profiles work and the options reference.

Why your D3D9 game shows a different GPU name

On a GPU whose vendor DXVK’s Direct3D 9 does not recognise, it reports a known AMD card instead. Our software GPU triggered it (F28):

          1
          info:  D3D9: Detected nonclassical vendor ID: 0x10005
          
          
          
        
          2
          info:  D3D9: Hiding actual GPU, reporting:
          
          
          DXVK noticed an unusual vendor and chose to hide it.
        
          3
          info:    vendor ID: 0x1002
          
          
          
        
          4
          info:    device ID: 0x73df
          
          
          
        
          5
          info:    device description: AMD Radeon RX 6700 XT
          
          
          What the game is told instead.
        

Direct3D 11 showed the real name. We have not checked what real NVIDIA, AMD and Intel GPUs show.

One setting matters to Intel owners: d3d9.hideIntelGpu defaults to True (since 2.6.2). Upstream’s comment says it reports Intel GPUs as AMD to Direct3D 8 and 9 games, to avoid restrictions in legacy games aimed at old Intel integrated chips. If a Direct3D 9 game on an Intel GPU shows an AMD name in its settings, this is why. We did not test it on Intel hardware.

Hiding NVIDIA (and when to unhide it): NVAPI and DLSS

By default DXVK reports NVIDIA GPUs as AMD through DXGI unless NVAPI is enabled (dxgi.hideNvidiaGpu = Auto, since 2.3), so games do not take NVIDIA-only code paths that need NVAPI. If you use dxvk-nvapi for DLSS you want the real GPU shown: set DXVK_ENABLE_NVAPI=1 on plain Wine, or PROTON_ENABLE_NVAPI=1 on Proton. Related options with the same pattern exist for other vendors: dxgi.hideAmdGpu, dxgi.hideIntelGpu and dxgi.hideNvkGpu. We could not test any of them. The full story is on the dxvk-nvapi page.

Does DXVK work with NVIDIA, AMD and Intel?

Yes if the GPU has a Vulkan driver recent enough for the DXVK version. Pick your GPU in the Version Picker on the requirements page; its answers come from the DXVK wiki.

For older cards see DXVK 1.10.3; for newer ones, DXVK 3.x.

Driver control-panel settings and DXVK

Settings forced through a Direct3D profile in the NVIDIA Control Panel or AMD Adrenalin may not apply once DXVK draws the game, because the driver then sees a Vulkan program instead. This is community reporting; we did not test it, so we cannot say which settings still work.