Package Details: dxvk-bin 1.2.1-0

Git Clone URL: (read-only)
Package Base: dxvk-bin
Description: A Vulkan-based compatibility layer for Direct3D 10/11 which allows running 3D applications on Linux using Wine (Windows DLL binary files)
Upstream URL:
Keywords: dxvk
Licenses: zlib/libpng
Conflicts: dxvk-bin<1.0-1, dxvk-git, dxvk-win32-bin, dxvk-win32-bin<1.0-1, dxvk-win64-bin, dxvk-win64-bin<1.0-1, dxvk-win64-git
Provides: dxvk
Submitter: ssorgatem
Maintainer: ssorgatem
Last Packager: ssorgatem
Votes: 95
Popularity: 11.017284
First Submitted: 2018-03-02 07:39
Last Updated: 2019-05-19 18:42

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

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

ssorgatem commented on 2019-02-26 15:46

@damachine the setup script won't work with proton's wine, because proton's wine is missing some parts in which it relies.

Try using your system's wine, it should work that way.

Yes, the old method worked 2 days ago.... but now there's a new setup script, which requires wine to work (actual wine, not just the part of wine that proton has).

damachine commented on 2019-02-26 15:42

@ssorgatem i use steam beta with proton last beta of proton is installed i think its a wine 3.16 i see with protontricks under winecfg. local i have installed wine-staging 4.2-1 from arch repo with some prefix with dxvk. the old install methode works 2 days before from the dxvk-master git clone.

ssorgatem commented on 2019-02-26 15:31

@damachine that means either your WINEPREFIX or your wine installation are missing parts of wine, that is, winemenubuilder.exe

What wine are you using? I don't think it's going to work with the one from Proton.

damachine commented on 2019-02-26 15:20

@ssorgatem the command brings me "wine: cannot find L"C:\windows\system32\winemenubuilder.exe" wine: configuration in '/EXTRA/.steam/steamapps/compatdata/271590/pfx' has been updated. /EXTRA/.steam/steamapps/compatdata/271590/pfx/dosdevices/c:/windows/syswow64" i have test it with a non steam prefix i become the same. thanks for your work

ssorgatem commented on 2019-02-26 15:07

@damachine with that same prefix set, what is the output of wine winepath -u 'C:\windows\system32' ?

That's how the script determines the prefix' location. If it doesn't work for Proton prefixes (like yours), then that is a bug that should be filed upstream.

I'm just packaging the setup script unmodified, just wrapping it with the arguments so that it behaves the most compatibly like the previous scripts.

damachine commented on 2019-02-26 14:44

WINEPREFIX="/EXTRA/.steam/steamapps/compatdata/271590/pfx" ./ install brings me "Failed to resolve C:\windows\system32." also with other prefixes. have export the prefix and then "./ install" but the same failed as above Any help. The old setup methode had work fine before.

ssorgatem commented on 2019-02-26 12:20

@kode54 it should be fixed now

kode54 commented on 2018-12-30 02:06

Minor issue with these packages: It stages the .dll files as belonging to the user that built the package, rather than belonging to root.

ssorgatem commented on 2018-10-13 07:28

@BrianAllred it should be fixed now

BrianAllred commented on 2018-10-12 22:20

Is there anyway the script could have a proper shebang (#!/bin/sh) at the top? I use fish shell, and it can't execute the script (throws "Exec format error"), so I currently either have to run it in a bash shell, wrap it in a bash one-liner, or put the shebang in there myself.

Not a big deal, but would be nice to have. Thanks for maintaining this!