Package Details: dxvk-win32-git 1.0.r1.g71186859-1

Git Clone URL: (read-only)
Package Base: dxvk-git
Description: Dummy package
Upstream URL:
Keywords: dxvk
Licenses: zlib/libpng
Submitter: ssorgatem
Maintainer: ssorgatem
Last Packager: ssorgatem
Votes: 16
Popularity: 1.741645
First Submitted: 2018-01-24 19:41
Last Updated: 2019-02-26 15:51

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

1 2 3 4 5 6 ... Next › Last »

silly commented on 2019-02-09 18:20

Shouldn't win packages setup dxgi as well? Assumed it was only the wine packages that could utilize wine's dxgi.

ssorgatem commented on 2018-08-28 06:06

Then you need to take care yourself of satisfying AUR dependencies. Which is going to be a lot of fun for mingw64...

The winelib version should be easier to install.

greencopper commented on 2018-08-28 05:39

I am not using any helper.

ssorgatem commented on 2018-08-28 04:36

@greencopper certainly. What AUR helper are you using? Maybe try the winelib builds (dxvk-wine64-git, dxvk-wine32-git), which don't require mingw64

greencopper commented on 2018-08-28 04:19

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

Shouldn't it get the dependencies automatically?

ssorgatem commented on 2018-08-26 20:17

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

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.

SilverSynch commented on 2018-08-26 19:50

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.

ssorgatem commented on 2018-08-22 13:40

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

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.