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.
Quoting: YoRHa-2BQuoting: 1xokWould you mind to elaborate a bit about AMD's Vulkan driver state on Windows?It's fairly buggy even compared to the open-source AMDVLK driver, which would indicate issues in the proprietary shader compiler.
What's so bad about it?
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?
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
See more from me