Arch Linux User Repository

DXVK upstream just merged d3d8 support, so I updated our setup script. Be sure to re-run it to enjoy DXVK's shiny new d3d8 frontend!

WINEPREFIX="/path/to/your/prefix" setup_dxvk install --symlink

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

error: target not found: mingw-w64-gcc
==> ERROR: 'pacman' failed to install missing dependencies

Shouldn't it get the dependencies automatically?

@SilverSynch upstream doesn't support a setup script anymore. No source is changed behind anyone's back. Upstream provides a winetricks verb that copies both your 32bit and 64bit local builds into your wineprefix. That's not what the setup script did and that is unsuitable for a package of a distribution.

The current solution (packagers rolling their own setup scripts) was proposed by upstream. See the discussion that lead up to it, specifically mentioning the AUR packages: https://github.com/doitsujin/dxvk/issues/572

You can also see why upstream's approach is not suitable for distro packages: by copying instead of symlinking, you have to manually run again the setup verb for each of your wineprefixes every time you update DXVK.

Meanwhile, for upstream, symlinking is not the best option, since it forces the built binaries to stay in the same path, and thus cannot be moved. This is not a problem for distro packages, but it is for users building or downloading DXVK themselves.

If you don't like my approach to the setup scripts, feel free to ignore them and do it manually as you like or edit them to suit you. But if you want to copy DXVK libraries into specific wineprefixes maybe you are better off using Lutris or winetricks rather than this package. I just preserved the old behaviour, because it is advantadgeous to most users of this package.

Please clarify that this package uses a custom install script, I don't like it when pkgbuilds change the source behind my back. Additionally, if the way the original script works is a problem, you should be making an issue on their github so we can have an upstream solution.

In the same way, you cna use different verions of DXVK for the 32 and 64 bit libraries without any problem.

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.

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

@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.

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

The original 64-bit setup_dxvk.verb (https://github.com/doitsujin/dxvk/blob/master/utils/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?

fatal: unable to access 'https://aur.archlinux.org/dxvk-git.git/': Could not resolve host: aur.archlinux.org error cloning dxvk-git

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