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

Git Clone URL: (read-only)
Package Base: dxvk-wine-git
Description: Dummy package
Upstream URL:
Licenses: zlib/libpng
Submitter: ssorgatem
Maintainer: ssorgatem
Last Packager: ssorgatem
Votes: 5
Popularity: 1.487223
First Submitted: 2018-07-22 16:53
Last Updated: 2019-02-26 15:37

Pinned Comments

ssorgatem commented on 2018-07-22 17:00

These packages use a winelib build of DXVK instead of a Windows build. This means they are built as a wine library rather than a Windows DLL. Therefore, they do not need a crosscompiler to be built.

They can replace the dxvk-mingw-git and dxvk-bin packages. Be sure to re-run the setup script if switching over from those.

To install DXVK on a WINEPREFIX (with the variable properly set):

setup_dxvk install

In order to uninstall DXVK from a wineprefix:

setup_dxvk uninstall

Latest Comments

1 2 3 4 Next › Last »

algebro commented on 2019-03-14 14:13

@algebro you don't need mingw for anything here...

Oh my bad, looks like I accidentally tried to install dxvk-win32-git in addition to this one, which pulled all the mingw dependencies. Just to make sure, dxvk-git will install both the 32 bit and 64 bit libraries right?

I remember having this problem when trying to build DXVK with a clang-built wine... what wine package are you using?

Good call, I am indeed using wine-staging 4.3 built with clang. I'll try again with GCC (hopefully the official package gets updated soon)

Update: Recompiling wine-staging with gcc allowed me to build and install this package, thanks!

ssorgatem commented on 2019-03-14 14:02

@algebro you don't need mingw for anything here...

Can you actually compile simple things with wineg++?

I remember having this problem when trying to build DXVK with a clang-built wine... what wine package are you using?

algebro commented on 2019-03-14 13:57

I'm getting the following error trying to build the package: ERROR:  Compiler wineg++ can not compile programs.

Any idea how to fix? I've verified that I've installed all the mingw make dependencies and that winegcc and wineg++ both exist in /usr/bin.

ssorgatem commented on 2019-02-27 08:57

Well, I did it to keep the behaviour as close to the previous script as possible.

You can alsways use /usr/share/dxvk/ directly, which defaults to replacing dxgi.dll and copying rather than symlinking.

gee commented on 2019-02-27 04:17

I agree, I was surprised by that choice. Maybe make that a required option when running the script.

loathingkernel commented on 2019-02-26 20:03

IMHO the script should not default to --without-dxgi, it should be a positional argument at least. The dxvk wiki states that a few option and games don't work well or at all with the dxgi implementation from wine.

peterg commented on 2019-02-09 13:03

@ssorgatem There seems to be a path typo in the setup_dxvk_aur.verb file.

installed_file4="C:\\windows\\system32\\system32/d3d10core.dll" \

should read

installed_file4="C:\\windows\\system32\\d3d10core.dll" \

This is present in all dxvk builds although it doesn't seem to cause a problem, at least not for me.

ssorgatem commented on 2019-01-26 10:27

@zfkerr see? It's a problem upstream. I told you it needed to be reported ;)

zfkerr commented on 2019-01-26 10:15

@ssorgatem look at this, please:

ssorgatem commented on 2019-01-20 19:48

So you can't see any difference between the symlinks you create and the ones the script creates?

The problem is, if I make the links manually, I will do them exactly as in the script.

You must be doing something different. I can't know what it is you are doing different by doing it myself.

Alternarively, maybe you could send me a tarball of your working prefix?

To be sure, it is a 64-bit prefix? if so, are both 64-bit and 32-bit DXVK linked there?