Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal. You can also buy games using our partner links for GOG and Humble Store.
We do often include affiliate links to earn us some pennies. See more here.

Continuing the exciting Wine-related news tonight, DXVK [GitHub] for Vulkan-based D3D11 and D3D10 implementation that's used with Wine has a 0.81 version now available.

Reminder: DXVK is one of the projects that makes up Valve's Steam Play. Enabling Windows games to run on Linux, directly through the Linux Steam client. Valve help fund the development of it.

Here's the highlights of what's new:

Improvements

  • 32-bit builds are now compiled with the dw2 exception model for better performance
  • Minor reduction of CPU overhead
  • Added configuration option to disable D3D10 support (set "d3d10.enable = False"). This can be used to let problematic D3D10 games fall back to their D3D9 renderer.

Bug fixes

  • Fixed occasional crash/hang when the state cache is enabled (#665)
  • Fixed potential violation of the Vulkan specification when copying images
  • Star Control: Origins: Fixed rendering issues when MSAA is enabled (#666)

While perhaps not as overly exciting as previous builds, every tiny hint of a performance increase through each release will add up to create a better experience for everyone. The level of work going into DXVK is seriously impressive. 

Article taken from GamingOnLinux.com.
Tags: Vulkan, Wine
24 Likes
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. Find me on Mastodon.
See more from me
The comments on this article are closed.
18 comments
Page: 1/2»
  Go to:

Leopard Oct 5, 2018
Best part of it:

QuoteMinor reduction of CPU overhead (I know it's getting boring, but I swear I'm telling the truth!)
Koopacabras Oct 5, 2018
well done they fixed bug 666, must be a really diabolic bug.
Liam Dawe Oct 5, 2018
Quoting: Guest
QuoteThe level of work going into DXVK is seriously impressive.
If I'm not mistaken, there were about 30 commits for that +0.01 upgrade, from 0.80. Perhaps not roadmap-worthy stuff, but still a boatload of work it seems.
Number of commits doesn't equal the amount of work though.
buenaventura Oct 5, 2018
Hey, nice!
YoRHa-2B Oct 5, 2018
Quoting: chancho_zombiewell done they fixed bug 666, must be a really diabolic bug.
Fixing that was actually a shitton of work, so it kind of lives up to its number I guess? On the bright side, it also makes depth-to-color image copies more efficient than they were before, so it wasn't exactly wasted effort.

More important is the other bug though, I thought it was quite rare, but apparently a lot of Lutris users started running into it as of late. FWIW, the fix for that bug was cherry-picked for the Proton build.

And yeah, things might be rather boring nowadays, but it's mostly feature complete and doesn't have a huge amount of optimization potential left.


Last edited by YoRHa-2B on 5 October 2018 at 8:24 pm UTC
Leopard Oct 5, 2018
Quoting: Guest
QuoteThe level of work going into DXVK is seriously impressive.
If I'm not mistaken, there were about 30 commits for that +0.01 upgrade, from 0.80. Perhaps not roadmap-worthy stuff, but still a boatload of work it seems.

Critical part in that release is #665.
Mohandevir Oct 5, 2018
Keep doing your awesome work YoRHa-2B!
jens Oct 5, 2018
  • Supporter
Quoting: YoRHa-2B
Quoting: chancho_zombiewell done they fixed bug 666, must be a really diabolic bug.
Fixing that was actually a shitton of work, so it kind of lives up to its number I guess? On the bright side, it also makes depth-to-color image copies more efficient than they were before, so it wasn't exactly wasted effort.

More important is the other bug though, I thought it was quite rare, but apparently a lot of Lutris users started running into it as of late. FWIW, the fix for that bug was cherry-picked for the Proton build.

And yeah, things might be rather boring nowadays, but it's mostly feature complete and doesn't have a huge amount of optimization potential left.

Thanks a lot for all your work spent on this. It is still magic that I'm playing GTA5 on my machine.

I have a small question: Next to stream output there is still "Predication" on your list with missing features. From my (limited) understanding this should only affect performance for games that use this feature (e.g. Arkham Knight wants to do so). Do you have a feeling about what you can gain with predication, assuming that it is actually possible to somehow translate this DX feature.
YoRHa-2B Oct 5, 2018
Quoting: jensDo you have a feeling about what you can gain with predication, assuming that it is actually possible to somehow translate this DX feature.
No idea, depends on the game. It can potentially avoid some GPU work (CPU is entirely unaffected).

It's a massive PITA to implement though, because it's tightly tied to queries in D3D11, and those really don't map well to Vulkan queries at all.


Last edited by YoRHa-2B on 5 October 2018 at 8:55 pm UTC
Koopacabras Oct 5, 2018
Before 0.80 Sherlock Holmes Devils Daughter loading screen time was extremely long, seriously, it took forever like 10 minutes, now it's blazingly fast, those small improvements do make a difference. Thanks for you work.


Last edited by Koopacabras on 5 October 2018 at 9:40 pm UTC
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring 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.