Package Details: dxvk-bin 1.9-1

Git Clone URL: (read-only, click to copy)
Package Base: dxvk-bin
Description: A Vulkan-based compatibility layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine (Windows DLL binary files)
Upstream URL:
Keywords: dxvk
Licenses: zlib/libpng
Conflicts: d9vk, dxvk
Provides: d9vk, dxvk, dxvk=1.9
Submitter: ssorgatem
Maintainer: ssorgatem (kekonn)
Last Packager: ssorgatem
Votes: 165
Popularity: 5.35
First Submitted: 2018-03-02 07:39
Last Updated: 2021-06-16 07:30

Pinned Comments

ssorgatem commented on 2018-03-27 06:47

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 »

tb0n3 commented on 2020-12-20 03:58

It works with wine-staging, so I went with that.

ssorgatem commented on 2020-12-07 10:04

Huh, weird. What is your wine version? Maybe there's been some change in how that package manages it...

tb0n3 commented on 2020-12-07 05:48

I'm unsure why, but despite having wine-staging-git in the dependencies it will not update with yay or makepkg because it claims wine conflicts. I do not have the wine package installed. Only wine-staging-git. I'm not sure what the fix is.

ssorgatem commented on 2020-07-05 09:12

Yes, but do look at the other options of the setup_dxvk script too, depending on what excatly do you want ;)

darkside commented on 2020-07-05 08:21

@ssorgatem Thank you very much!

Just to be sure, If I want to install it in custom wine prefix with symlink WINEPREFIX=~/wine/affinity setup_dxvk install --symlink Is the right way?

ssorgatem commented on 2020-07-05 08:14


It depends.

When you install dxvk through winetricks, winetricks copies the specified version of the DXVK dlls to that wineprefix. It won't get updated unless you manually update it.

With this package, you can install DXVK in a wineprefix with the --symlink option, which rather than copying the DXVK dlls into the wineprefix, symlinks them. So each time this package is updated, the DXVK dlls in each linked wineprefix are automatically updated too.

darkside commented on 2020-07-05 08:07

It is possible to install dxvk inside winetricks (installation of DLLs section). Is this something different?

loathingkernel commented on 2020-05-19 21:46


To add to what others said, Proton's version of DXVK is different from upstream DXVK as it includes an extra component to enable the co-existence of DXVK with VKD3D under the same wine. It is required to pass configuration options to DXVK when wine's DXGI (required by VKD3D) is in use. GE's proton distribution also patches DXVK for the same effect.

Also, installing to arbitrary directories in the user's home folder is not something the package manager should do. It is up the userspace applications to do that.

ssorgatem commented on 2020-05-19 16:23

@shoober420: Installing in by default Proton directories seems like bad idea; they already include a version of DXVK. Like @kerkonn says, a separate package that woudl replace Proton's DXVK with another DXVK may be the way to go.

Wine is a dependency because you need wine to use it, and a minimum version too. The setup script won't work without wine, so you need wine even to install it into a Proton wineprefix.

kekonn commented on 2020-05-19 16:02


We don't want to do this by default. People might have their proton set up just the way they want to. Doing that would ideally be a package on it's own that depends on a dxvk package.

GE's Proton definitely includes DXVK, vanilla proton might do so as well, but I'm not sure.

I'll leave moving stuff to optdepends for @ssorgatem because I'm not sure if there are maybe reasons they are where they are.