DXVK, a Vulkan-based compatibility layer for Direct3D 11 for use with Wine

This is interesting
Did not know about the D3d9 one.
Methinks more games shall run soon :)

Still quite buggy at this stage, but some games do perform well already.

I like my Blizzard games, and it seems to be more fluid using DXVK than gallium-nine on Diablo III... But there are some visual bugs that need fixing.

I tried Quantum Break also which launches but is pretty slow in game right now 10-20 fps.

I've thought about trying this with Dying Light as I can't get the native Linux version to launch.

One thing to mention is you really need to be using the latest mesa-git and radv-git drivers if you're an AMD user, I was getting some weird glitches on the stable branch.


Last edited by lejimster on 26 March 2018 at 9:19 am UTC

QuoteIt's interesting to see what will become of this, since the Wine developers are working on their own Vulkan implementation.

If you mean that Wine people are working on their D3D-on-Vulkan implementation – that’s true, but they are not doing the same. DXVK implements D3D11 on Vulkan. Wine’s VKD3D is to implement D3D12-on-Vulkan (basically the exact reverse of what Vulkan Portability Initiative tries to achieve), and Vk9, as you wrote, is to implement D3D9-on-Vulkan.

Three projects, and every one of them tries to implement a different version of D3D API.

I only wonder if Windows applications can call to multiple D3D versions simultanuously to draw on the same context, and if so, how it can be handled by such projects (does D3D11 implementation have to implement D3D9 and everything below too?). And if so, can all the D3Dx-on-Vulkan projects share code? As I have almost no experience with GPU programming and absolutely none with DirectX, I have no idea – but it’s something that, in my not educated enough mind, seems like a potential problem.


Last edited by silmeth on 26 March 2018 at 9:25 am UTC

Quoting: GuestAny chance this will get included in the wine-staging project? so far it seams a pain in the ass to install as it is.

Installing DXVK is pretty easy. It’s just pasting two dlls to wine prefix / application directory and setting library overrides in wine.

The problematic part is not directly related to DXVK – it is setting up Vulkan support in Wine itself (which needs Windows Vulkan SDK installed and set up). I think with time Wine will handle it somehow more automatically (probably like installing Gecko and Mono?), but for now they did not figure out how to do it properly.


Last edited by silmeth on 26 March 2018 at 10:27 am UTC

Quoting: lejimsterStill quite buggy at this stage, but some games do perform well already.

I like my Blizzard games, and it seems to be more fluid using DXVK than gallium-nine on Diablo III... But there are some visual bugs that need fixing.

I tried Quantum Break also which launches but is pretty slow in game right now 10-20 fps.

I've thought about trying this with Dying Light as I can't get the native Linux version to launch.

One thing to mention is you really need to be using the latest mesa-git and radv-git drivers if you're an AMD user, I was getting some weird glitches on the stable branch.

I can run Dying Light native without problems on Nvidia binary. If you are a Mesa user , you must force OGL version to 4.5 via launch options.

Quoting: silmethThree projects, and every one of them tries to implement a different version of D3D API.

True enough, I would have thought the Wine developers would eventually move to do more with Vulkan, but perhaps if they integrate stuff like this when it's more mature they won't need to themselves for other parts of D3D.

Quoting: lejimsterI've thought about trying this with Dying Light as I can't get the native Linux version to launch.

Hello fellow vega 56 user!
Just force the gl version:
MESA_GL_VERSION_OVERRIDE=4.4 MESA_GLSL_VERSION_OVERRIDE=440 %command%

:)

Quoting: nox

Quoting: lejimsterI've thought about trying this with Dying Light as I can't get the native Linux version to launch.

Hello fellow vega 56 user!
Just force the gl version:
MESA_GL_VERSION_OVERRIDE=4.4 MESA_GLSL_VERSION_OVERRIDE=440 %command%

:)

I need to try this tonight as currently nothing happens. Sometimes I'll get the splash box but then it immediately crashes.


Last edited by drlamb on 26 March 2018 at 12:35 pm UTC

dxvk had amazing progress. Some features though are quite hard to implement, such as stream output, because Vulkan lacks comparable functionality. So that's still in the TODO list.

Overall performance is very good, unlike with wined3d which now currently is bugged by buffer mapping issues (but Wine developers are working on it).

For TW3, in the wilderness, dxvk gives 65+fps:


In areas with many NPCs, it gives 55+fps:


That's without vsync, 1920x1200, Vega 56 8GB VRAM.


Last edited by Shmerl on 26 March 2018 at 1:15 pm UTC

Quoting: LeopardI can run Dying Light native without problems on Nvidia binary. If you are a Mesa user , you must force OGL version to 4.5 via launch options.

Quoting: nox

Quoting: lejimsterI've thought about trying this with Dying Light as I can't get the native Linux version to launch.

Hello fellow vega 56 user!
Just force the gl version:
MESA_GL_VERSION_OVERRIDE=4.4 MESA_GLSL_VERSION_OVERRIDE=440 %command%

:)

Thanks, but I guess I should have been more specific. It appears to be an Arch issue that only effects Mesa users. I think some other distros suffer the same problem. I tried for hours different work arounds, even following GloriousEggroll's snap package guide and it still wouldn't launch :'(.