Package Details: dxvk-winelib-git 1.1.1.r0.g37f9a7ff-2

Git Clone URL: (read-only)
Package Base: dxvk-wine-git
Description: A Vulkan-based compatibility layer for Direct3D 10/11 which allows running 3D applications on Linux using Wine. Winelib version
Upstream URL:
Licenses: zlib/libpng
Conflicts: dxvk-bin, dxvk-git, dxvk-mingw-git, dxvk-win32-git, dxvk-win64-git, dxvk-wine32-git, dxvk-wine64-git
Submitter: ssorgatem
Maintainer: ssorgatem
Last Packager: ssorgatem
Votes: 6
Popularity: 1.556723
First Submitted: 2018-07-22 16:53
Last Updated: 2019-05-04 19:32

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

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

ssorgatem commented on 2019-01-02 09:59

Thank you for finding it out!

Should be fixed now. Hopefully.

svanheulen commented on 2019-01-01 00:51

Ok, I found the issue. It was only happening with 32-bit games and the reason is that your sed for modifying the setup_dxvk_aur.verb is not correct.

You might consider just removing the "DXVK_ARCH=..." line in the verb and setting it in the setup_dxvk32/64 scripts. Like "DXVK_ARCH=64 winetricks --force ..."

Then you wont have to use sed on the verb file at all, it will be the same for both archs.

ssorgatem commented on 2018-12-31 15:33

Is it the one from Tk-Glitch? Because that's what I'm using.

For prefixes where dxgi.dll was symlinked, you may need to remove the link manually and double check the dll overrides...

But on a fresh prefix it should just work.

svanheulen commented on 2018-12-31 14:50

I'm using a custom build of wine-staging-nine 4.0rc4 with esync patches. If no one else is having issues, it must be something wrong on my end, so don't worry about it. The old PKGBUILD still works fine for me so I can just use that until I have time to properly troubleshoot the issue.

ssorgatem commented on 2018-12-29 20:16

Strange. Which version of wine are you using? Also make sure that dxgi.dll isn't marked as "native" in winecfg.

Does it happen with both 32-bit and 64-bit games?

svanheulen commented on 2018-12-29 20:07

The latest changes to the PKGBUILD do not work for me. Games complain about not being able to load dxgi.dll. I re-ran setup_dxvk32/64 and I also tried with a fresh Wine prefix.

ssorgatem commented on 2018-12-29 12:09

In the last update, the path of the DXVK libraries has changed, which means you'll need to re-run the setup script on your prefixes to have DXVK working.

It's also no longer using a custom dxgi.dll, so now it can work simultaneously with vkd3d in the same prefix!

ssorgatem commented on 2018-12-05 09:04

@Sukid it builds fine on my end. Maybe you are missing some headers?

Which compiler are you using? I think you need to use the same you used to build wine. So if you use wine built with GCC, use GCC.

I couldn't build with GCC against a Clang-built wine.

Sukid commented on 2018-12-05 03:13

Getting a lot of /usr/include/c++/8.2.1/cmath:45:15: fatal error: math.h: No such file or directory #include_next <math.h> and /usr/include/c++/8.2.1/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next <stdlib.h>

resulting in compiling not working. What changed?

ssorgatem commented on 2018-10-16 10:50

@zfkerr thank you! Should be fixed now.