Confused on Steam Play and Proton? Be sure to check out our guide.
We do often include affiliate links to earn us some pennies. See more here.

No doubt some of our readers will be in for a busy weekend testing, with another release of DXVK now officially available.

Developer Philip Rebohle put out DXVK 1.4.3 this evening which adds in a new file format for the state cache, which should give smaller files. The state cache from previous versions of DXVK should be converted automatically, so no manual effort is required.

Additionally, even more performance is continuing to be squeezed out of this Vulkan layer for Wine as it has a reduction in CPU overhead. It was noted that it should be of particular benefit to those games that have a large number of different shaders. Frankly, I'm amazed Rebohle can somehow still push the performance even further.

On top of that, a few bug fixes were added into the mix too:

  • Fixed incorrect barriers in case graphics shaders write to UAVs.
  • Fixed incorrect MSAA sample positions being reported to shaders.
  • Fixed some MSVC compiler warnings (#1218).

Find DXVK on GitHub.

Article taken from
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.
Page: «4/4
  Go to:

sub Oct 20, 2019
Quoting: YoRHa-2B
Quoting: 1xokWould you mind to elaborate a bit about AMD's Vulkan driver state on Windows?
What's so bad about it?
It's fairly buggy even compared to the open-source AMDVLK driver, which would indicate issues in the proprietary shader compiler.

It wouldn't be so bad if things were at least consistently broken, but they aren't. One driver update might randomly fix an issue, the next update might fix something else but break the very same thing they fixed in the earlier update. It's a rollercoaster, and honestly I just can't be arsed to report bugs against it.

AMD's Windows driver has been a broken mess ever since Navi launched anyway, with D3D9 being completely broken in some cases and other major issues, but that's a different story.


That doesn't sound promising, indeed.
I have a very old card. Radeon HD 7950.
The Windows driver never gave me headaches.
Even when that card was new.

All games I tried with Vulkan run great on that old beast (paired with a Phenom II X4).
DOOM and Wolf 2. FullHD. Perfectly smooth. :)

In the not too far future I will update the full rig.
The idea was to go for Navi judging from my AMD experience so far... Hmmmm.

Specifically for Navi, would you suggest using AMDVLK or RADV?
YoRHa-2B Oct 20, 2019
Quoting: subSpecifically for Navi, would you suggest using AMDVLK or RADV?
I don't have any personal experience with Navi, but from what I'm hearing from users, it doesn't seem to be stable at all yet, on any driver; the kernel driver is apparently also causing major headache (read: system hangs and fun stuff like that). I'd give it a few more months.

Last edited by YoRHa-2B on 20 October 2019 at 7:10 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 with no article paywalls. We also don't have tons of adverts, there's also no tracking and we respect your privacy. 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.