Package Details: dxvk-win64-bin 1.0.3-2

Git Clone URL: (read-only)
Package Base: dxvk-bin
Description: Dummy package
Upstream URL:
Keywords: dxvk
Licenses: zlib/libpng
Conflicts: dxvk-git
Provides: dxvk
Submitter: ssorgatem
Maintainer: ssorgatem
Last Packager: ssorgatem
Votes: 86
Popularity: 7.146541
First Submitted: 2018-03-02 07:39
Last Updated: 2019-04-16 07:24

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 »

ssorgatem commented on 2019-04-16 14:33

No, putting $pkgdir there will break the link when installed.

That whole chmod line needs to be removed. It should be fixed now.

JIgnacioTG commented on 2019-04-16 06:57

I resolved the "chmod: cannot operate on dangling symlink 'setup_dxvk'" bug editing too the PKGBUILD file but adding the variable $pkgdir in the line of the symbolic link:

ln -s $pkgdir/usr/share/dxvk/ "$pkgdir/usr/bin/setup_dxvk"

I don't know if this breaks something.

mallgrab commented on 2019-04-15 23:49

It cries about "chmod: cannot operate on dangling symlink 'setup_dxvk'"
Editing the PKGBUILD and adding "cd $pkgdir/usr/bin"
below "mkdir -p $pkgdir/usr/bin"
fixed the problem for me.

ssorgatem commented on 2019-04-07 16:01

The 1.1 release has been pulled out because it was buggy (reportedly caused GPU hangs), so this package hasn't included it.

Nocifer commented on 2019-03-03 13:04

Hi, is there a reason that this package installs dxvk with the new --without-dxgi flag enabled by default? Or rather, I do understand the reason somewhat (probably so it can work out of the box without breaking synergy with vkd3d, dxup et al) but it's actually not really recommended by the developer because it breaks (or at least underperforms in) many games, especially when one's using an nvidia card. And even worse is that I can't see any way of installing WITH dxgi without modifying the provided script and removing the flag.

I think it'd be preferable if users could choose to install with or without dxgi themselves; maybe by creating a flag in your own script (e.g. --dxgi) which if present would serve to disable the --without-dxgi flag of the upstream script, which could then remain the default as it is now.

damachine commented on 2019-02-26 17:12

@ssorgatem Thanks for your help. have the old setup methode use for now.

ssorgatem commented on 2019-02-26 16:16

then the setup script should work when using the non-proton wine, and then you can go back to using proton's wine

damachine commented on 2019-02-26 16:12

"WINEPREFIX="/EXTRA/.steam/steamapps/compatdata/271590/pfx" wine winepath -u 'C:\windows\system32'"



ssorgatem commented on 2019-02-26 16:10

@damachine have you tried using it with non-proton wine on a proton prefix?

The older scripts had many limitations which this script solves (like being able to uninstall, for example). It also relied on winetricks and a winetrick verb... which I'm not too fond on mantaining.

But you are free to use an older version of this package, but replacing the DXVK files...

You can also just manually set it up; it's just symlinking or copying a couple files.

In any case, Proton should include this version of DXVK in a short time.

And last time I tried, whenever I started a game with Proton, it overwrote the manually installed DXVK with its own... so little point with the setup script supporting that.

damachine commented on 2019-02-26 16:00

@ssorgatem Is it possible to use the old setup script as a lagacy setup methode like that works for proton use. sorry that i repeat when it works before so fine.