HOW-TO · DEVELOPMENT BUILDS · NOT DONE BY US
Get a DXVK development build or compile it yourself
How we checked this
Release, master or fork?
- Everyone: the official release, from the download page.
- You were told a fix is on master: a development build, only to test that fix.
- You need a different feature set: a fork; see forks.
Download a development build
-
Open the artifacts workflow
The README links to it. GitHub Actions has built DXVK on every change since 1.8.1, per the README and release notes. -
Pick a run on master and download its artifact
You must be signed in to GitHub. Artifacts expire after a while, so grab one you need soon. -
Unpack it
Look for thex64andx32folders, as in a release. -
Install like a release
Use the same copy steps as the Windows guide or Linux guide. -
Note which build you have
Write down the commit hash. A non-release build may show extra text in the HUD version item; we did not check how it looks.
Hash-checking does not work on these: the verifier knows only official releases (F44).
What changed since the last release
On GitHub, open the repository’s compare view between the last tag and master to read the commits. Our notes record one unreleased change as of November 2026: the legacy frame limiter option was removed on master. Treat it as dated information and check the commit list. See releases for released changes.
Build it yourself
Per the 3.1.1 README you need Meson 0.58 or newer, a MinGW-w64 cross compiler 10.0 or newer, glslang, and the repository with its submodules; the same README gives Wine 10.0 as the runtime for this line, while the runtime wiki says 10.1 (both as stated in their sources). The README describes two routes: a packaging script, and a manual Meson setup with cross files. The output DLLs land in the build folder you chose. A common community error is a MinGW-w64 without POSIX threads; on Debian and Ubuntu the fix people give is to select the posix variant of the MinGW alternative. We did not build DXVK, so we cannot confirm any of this beyond what the README says. Read the README for the exact steps.
Risks and etiquette
- Master builds are untested: use them offline.
- Say it is a master build if you report a bug, with the commit, a log and the last release that worked. Do not report it as a release bug.
- Never run “nightly” builds from third-party sites; see Is DXVK safe?
- DXVK Native has its own build notes: DXVK Native.
Questions people ask
Where are DXVK nightly builds?
DXVK has no nightly download page. Development builds come from GitHub Actions artifacts for the master branch, per the README. Never take a nightly from a third-party site.
Do I need to sign in to download artifacts?
Yes, GitHub requires you to be signed in to download Actions artifacts, and old artifacts expire.
Is DXVK master safe?
It is untested between releases. Use it only to test a specific fix, offline, and keep the official release to go back to.
What do I need to compile DXVK?
According to the 3.1.1 README: Meson 0.58 or newer, a MinGW-w64 cross compiler 10.0 or newer, glslang, and the repository with its submodules. Follow the README for exact commands; we did not build it.
Why does my DXVK build fail with threading errors?
A frequent cause is a MinGW-w64 without POSIX threads. On Debian and Ubuntu, switching the MinGW alternative to the posix variant is the usual fix. This is community advice that we did not verify.
Sources
- DXVK README at v3.1.1 (building, development builds) · accessed 2026-11-07
- DXVK 1.8.1 release notes (artifacts CI) · accessed 2026-11-07