Check out our Monthly Survey Page to see what our users are running.

There's so many incredible things going on around Wine right now it's hard to keep track. DXVK is now expanding to support Direct3D 10 over Vulkan in Wine.

Talking about it on the official GitHub account in this issue, the main developer of DXVK said it works in a similar way to DXUP with it being a "very thin wrapper around the existing D3D11 interfaces, while allowing for better interoperability between the two APIs.".

As for how much it actually supports, well, quite a lot. It implements "most" of the Direct3D 10.1 core API and the shader reflection API. However, the Effects API is not currently supported. To use it, you will need the d3dcompiler_43.dll, which can be grabbed by using winetricks.

More information on it here.

Additionally, there's also another new project named Direct3D 9-to-11 which aims to convert Direct3D 9 programs to Direct3D 11. It's supposed to be used with DXVK and it's currently under "heavy development". It will be interesting to see how this project shapes up, although there is already the VK9 project to keep an eye on.

So much Wine, so little time.

Article taken from GamingOnLinux.com.
Tags: Vulkan, Wine
24 Likes, Who?
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG, Humble Store and Paradox Interactive. See more here.
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
The comments on this article are closed.
34 comments
Page: «4/4
  Go to:

axredneck 14 Aug, 2018
Quoting: mrdeathjr... devil may cry 4 ... can be stay or not in hyphotetical tests for wine 3.15 / 3.16 :D
This
Ardje 14 Aug, 2018
Quoting: STiATInteresting, that Mesa and DXVK need game based workarounds. Seems game devs / engines are not always compliant to standards.
Eh... they all have...
Nvidia always comes with a giant list of tweaks and workarounds for games. If you change the name of the game those tweaks suddenly don't work. Just like those 3d benchmarks that suddenly score lower when you change their name.
The same with ATI and fglrx, especially for crossfire use.
I assume the same with AMD.
For now mesa still seems to be very distant of making gamename based fixes.
MayeulC 15 Aug, 2018
Quoting: ArdjeFor now mesa still seems to be very distant of making gamename based fixes.
driconf? That's used to adjust driver behaviour to various application quirks; which can be name-based.

And the same is being done for DXVK, for instance... Some apps are just broken, and wouldn't work with a conforming driver, or would only work with poor performance (as far as I know, it's sometimes as simple as lying about being an nvidia driver, the supported extensions, or tweaking GL threading). That's one of the things that Vulkan set out to address, if I'm not mistaken.


Last edited by MayeulC on 15 August 2018 at 10:09 am UTC
legluondunet 15 Aug, 2018
With this new DXVK changes, I can finally launch and play "Assassin's Creed™: Director's Cut Edition" directx10 version.
It's the first time I can play this game since I bought it in 2013 on Steam...
But Just Cause II is still too unstable.


Last edited by legluondunet on 15 August 2018 at 11:14 am UTC
While you're here, please consider supporting GamingOnLinux on:

Patreon, Liberapay or PayPal Donation.

We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.