Don't want to see articles from a certain category? When logged in, go to your User Settings and adjust your feed in the Content Preferences section where you can block tags!
We do often include affiliate links to earn us some pennies. See more here.

DXVK has levelled up once again, as release 1.1.1 is out and it's a major update that also acts as the re-release of DXVK 1.1 which was removed due to issues.

Major new features with this release should result in your frame timing being more consistent and triple buffering should now work as expected. For games that have a lot of shaders, memory utilization should be reduced as well. Configuration options in the DXVK config file can be limited to a single executable, meaning you can now use one single file and not one per-game.

Queries were also re-worked, which should see Unreal Engine 4 titles get improved performance although you need at least Wine 4.5/Proton 4.2 and NVIDIA 418.52.05 or AMD/Intel Mesa 19.1-git for your GPU driver. It needs the "VK_EXT_host_query_reset" extension supported, as without it certain games may perform "significantly worse".

Some notable bugs were also solved with this release like incorrect MSAA sample locations in shader code, crashing when using the Windows build of RenderDoc with Wine, AMDVLK had issue with flickering or having artifacts in some games and so on. Issues with specific games like NieR:Automata, Sekiro: Shadows Die Twice, Space Engineers and SpellForce 3 were also solved.

This release also has improved compatibility with Wine's own Direct2D implementation and there's also some minor optimizations for multisample resolve operations, presentation and "other things".

Find the release announcement here.

Article taken from GamingOnLinux.com.
34 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.
15 comments
Page: «2/2
  Go to:

garpu May 5, 2019
I've been using the 430.09 driver with it, and haven't had problems, but I don't play any Unreal 4 games. Rather, I played a few hours of Path of Exile last night with the combination, and didn't notice any problems. (Things were getting a bit hot when watching videos on twitch at the same time, but twitch always hits my cpu harder than most games. Go figure.)
massatt212 May 6, 2019
does anyone have dxvk 1.0+ version with Async implemented, want to test some single player games like need for speed payback
axredneck May 6, 2019
Quote... triple buffering should now work as expected.
Doesn't triple buffering increase latency?
Shmerl May 7, 2019
Quoting: GuestThe new 1.1.1 seems like a really nice release. Only 3000 MB RAM usage in The Witcher 3 with Ultra settings: https://drive.google.com/file/d/1zbMREcDt7XJwSamwkMaR61OVeC70CmDI/view?usp=sharing 6 GB RAM is the minimum requirement if you want to run it on Windows 10. DXVK is wonderful.

Interesting point. Is it due to compressed shaders?
YoRHa-2B May 7, 2019
Witcher 3 doesn't have too many shaders, and they aren't that big either. Savings in that game shouldn't be more than 100MB.

If you're looking for a game where the shader compression and not storing multiple copies of the shader code really makes a huge difference, fire up Quake Champions or Dishonored 2, it saves well over 1GB there.


Last edited by YoRHa-2B on 7 May 2019 at 12:25 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.