DXVK Native
DXVK Native is a port of DXVK to Linux which allows it to be used natively without Wine.
This is primarily useful for game and application ports to either avoid having to write another rendering backend, or to help with port bringup during development.
Release builds are built using the Steam Runtime.
How does it work?
DXVK Native replaces certain Windows-isms with a platform and framework-agnostic replacement, for example, HWNDs can become SDL_Window*s, etc.
All it takes to do that is to add another WSI backend.
DXVK Native comes with a slim set of Windows header definitions required for D3D9/11 and the MinGW headers for D3D9/11. In most cases, it will end up being plug and play with your renderer, but there may be certain teething issues such as:
__uuidof(type)is supported, but__uuidof(variable)is not supported. Use__uuidof_var(variable)instead.
DXVK Native also has some performance tweaks for D3D9, disabling float emulation and some validation.
This is configurable in d3d9_config.h.
Games/Projects Using DXVK Native
- Portal 2 (Valve - Windows & Linux)
- Left 4 Dead 2 (Valve - Windows & Linux)
- Ys VIII, Ys IX (PH3 Games - Stadia)
- Perimeter (Linux)
- Momentum Mod (Linux)
- Portal 2: Community Edition (Linux)
Build instructions
Requirements:
Steam Runtime
DXVK Native can be built in the Steam Runtime using docker.
If you don't care about this, simply skip this section.
To build in a Steam Runtime docker, simply cd to the DXVK directory and run:
for 32-bit:
docker run -e USER=$USER -e USERID=$UID -it --rm -v $(pwd):/dxvk-native registry.gitlab.steamos.cloud/steamrt/scout/sdk/i386 /bin/bash
for 64-bit:
docker run -e USER=$USER -e USERID=$UID -it --rm -v $(pwd):/dxvk-native registry.gitlab.steamos.cloud/steamrt/scout/sdk /bin/bash
Building the library
Inside the DXVK directory, run either:
On your host machine:
./package-native.sh master /your/target/directory --no-package
With Steam Runtime:
./package-native-steamrt.sh master /your/target/directory --no-package
This will create a folder dxvk-native-master in /your/target/directory which will contain a the libraries and tests.
In order to preserve the build directories and symbols for development, pass --dev-build to the script.
HUD
The DXVK_HUD environment variable controls a HUD which can display the framerate and some stat counters. It accepts a comma-separated list of the following options:
devinfo: Displays the name of the GPU and the driver version.fps: Shows the current frame rate.frametimes: Shows a frame time graph.submissions: Shows the number of command buffers submitted per frame.drawcalls: Shows the number of draw calls and render passes per frame.pipelines: Shows the total number of graphics and compute pipelines.memory: Shows the amount of device memory allocated and used.gpuload: Shows estimated GPU load. May be inaccurate.version: Shows DXVK version.api: Shows the D3D feature level used by the application.compiler: Shows shader compiler activitysamplers: Shows the current number of sampler pairs used [D3D9 Only]scale=x: Scales the HUD by a factor ofx(e.g.1.5)
Additionally, DXVK_HUD=1 has the same effect as DXVK_HUD=devinfo,fps, and DXVK_HUD=full enables all available HUD elements.
Frame rate limit
The DXVK_FRAME_RATE environment variable can be used to limit the frame rate. A value of 0 uncaps the frame rate, while any positive value will limit rendering to the given number of frames per second. Alternatively, the configuration file can be used.
Device filter
Some applications do not provide a method to select a different GPU. In that case, DXVK can be forced to use a given device:
DXVK_FILTER_DEVICE_NAME="Device Name"Selects devices with a matching Vulkan device name, which can be retrieved with tools such asvulkaninfo. Matches on substrings, so "VEGA" or "AMD RADV VEGA10" is supported if the full device name is "AMD RADV VEGA10 (LLVM 9.0.0)", for example. If the substring matches more than one device, the first device matched will be used.
Note: If the device filter is configured incorrectly, it may filter out all devices and applications will be unable to create a D3D device.
State cache
DXVK caches pipeline state by default, so that shaders can be recompiled ahead of time on subsequent runs of an application, even if the driver's own shader cache got invalidated in the meantime. This cache is enabled by default, and generally reduces stuttering.
The following environment variables can be used to control the cache:
DXVK_STATE_CACHE=0Disables the state cache.DXVK_STATE_CACHE_PATH=/some/directorySpecifies a directory where to put the cache files. Defaults to the current working directory of the application.
Debugging
The following environment variables can be used for debugging purposes.
VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validationEnables Vulkan debug layers. Highly recommended for troubleshooting rendering issues and driver crashes. Requires the Vulkan SDK to be installed on the host system.DXVK_LOG_LEVEL=none|error|warn|info|debugControls message logging.DXVK_LOG_PATH=/some/directoryChanges path where log files are stored. Set tononeto disable log file creation entirely, without disabling logging.DXVK_CONFIG_FILE=/xxx/dxvk.confSets path to the configuration file.DXVK_PERF_EVENTS=1Enables use of the VK_EXT_debug_utils extension for translating performance event markers.