Package Details: dxvk-mingw-git 1.5.r3.ga265af74-2

Git Clone URL: (read-only, click to copy)
Package Base: dxvk-git
Description: A Vulkan-based compatibility layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine. Windows DLL version)
Upstream URL:
Keywords: dxvk
Licenses: zlib/libpng
Conflicts: dxvk-bin
Provides: d9vk, dxvk, dxvk=1.5.r3.ga265af74
Submitter: ssorgatem
Maintainer: ssorgatem
Last Packager: ssorgatem
Votes: 19
Popularity: 1.04
First Submitted: 2018-01-24 19:41
Last Updated: 2019-12-17 22:16

Pinned Comments

ssorgatem commented on 2018-06-22 06:24

This package provides Windows binaries of the DXVK dlls. They work on wine and should work on Windows too. If you don't specifically want Windows binaries and you want to just use DXVK on wine, the winelib package is a better approach and much easier to build (dxvk-winelib-git).

To enable DXVK in a wineprefix, do the following (with the WINEPREFIX variable properly set):

setup_dxvk install

In order to uninstall DXVK from a wineprefix:

setup_dxvk uninstall

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

ssorgatem commented on 2018-08-22 13:40

Why would it be unsafe? An app uses either 32-bit or 64-bit D3D10/11. Both cannot be used at the same time. So you can "mix" 32-bit wined3d and 64-bit DXVK (or vice-versa) in the same prefix without problems.

AlexanderR commented on 2018-08-22 13:16

@ssorgatem I am fairly sure, that partial install (e.g. installing 64-bit dxvk libs without installing 32-bit ones) is unsafe.

ssorgatem commented on 2018-08-19 23:51

@AlexanderR it's not a patched verb, it's a different one.

The upstream verb assumes both 32-bit and 64-bit DXVK are available and assumes a certain directory structure.

Morepver, it copies the DXVK dlls to the WINEPREFIX.

If I used the upstream verb, I'd need to put 32 and 64 bit libraries in the same package... and you'll need to re-run the setup verb for each of your wine prefixes after every update.

My custom verbs deal only with either 32 or 64 bit libraries, letting you choose which to install or enable in your prefixes.

But most importantly, they symlink, rather than copy, the DXVK dlls, so that whenever you update the package, the libraries are automatically updated in all your wine prefixes where my verbs (or the previous setup script) were run.

For 32 bit dlls, install the 32-bit package (dxvk-win32-git), which has a script for them.

AlexanderR commented on 2018-08-19 23:05

@ssorgatem Why are you using a patched setup_dxvk.verb instead of upstream version?

The original 64-bit setup_dxvk.verb ( installs both 32-bit and 64-bit dlls to accommodate wine's WoW64 emulation (e.g. running both 32-bit and 64-bit apps in the same 64-bit prefix). Your package installs modified setup_dxvk64, that does not install 32-bit dlls. Is there any valid reason for that?

Plexcon commented on 2018-08-17 19:47

fatal: unable to access '': Could not resolve host: error cloning dxvk-git

ssorgatem commented on 2018-07-24 12:58

@libcg nice catch! Indeed, the links were broken, for both 32 and 64 bit packages. Should be fixed now.

libcg commented on 2018-07-24 12:41

There is an issue with the setup_dxvk32 symlink. It points to /usr/share/dxvk// instead of /usr/share/dxvk/x32/

ssorgatem commented on 2018-07-23 15:29

I created a package for the winelib build, so you can build 64-bit DXVK without needing a crosscompiler (MinGW64):

ssorgatem commented on 2018-07-22 15:01

I decided to split this package in 2, each providing the 32-bit or 64-bit libraries, and their respective scripts.

cogwerkz commented on 2018-07-09 09:16

Probably related to some of the git versions of the ming compiler packages. I personally just use the -bin versions of those. Faster compilations, works with this package, no key problems.