Developer Philip Rebohle announced today the release of DXVK 1.7.2 to further improve the D3D9, D3D10 and D3D11 to Vulkan translation layer.
Used with Wine, and part of the Steam Play Proton compatibility layer, it's great to see it still moving along. This is the first release since August and while it's technically a minor release in versioning, the actual fixes included look to be quite important.
There's a "major" regression fixed for D3D9 titles that caused crashes in many games, a fix for D3D9 crashes on AMDVLK due to invalid Vulkan API usage, they've worked around some stack overflows in some 32-bit D3D9 games, a workaround is now in place for rendering issues on AMD drivers in some Unity Engine games, another workaround is added for Unicode on Windows "being garbage" and you can disable log files being created.
Additionally these games saw some fixes that should help them run better: Baldur's Gate 3, Final Fantasy XIV, Just Cause 3, Marvel's Avengers, Need for Speed Heat, PGA TOUR 2K21 and Trails in the Sky SC.
Release notes can be found here.
As a reminder: it's possible to update your Steam Play Proton install with this newer DXVK release, without waiting on a new Proton build. To do so you can just overwrite the existing DXVK files with the release download of DXVK 1.7.2. You can find your Proton install somewhere like this (depending on your Steam Library drives):
path-to-your/SteamLibrary/steamapps/common/Proton x.x/dist
Where x.x is whatever Proton version installed you wish to give a new DXVK.
Inside there you will see "lib" and "lib64", for 32bit and 64bit. Inside each of those, there's a "wine" folder and inside there is a "dxvk" folder and that's where you replace the files with new versions. Do so at your own risk but it's usually harmless. If you mess anything up, one way to ensure it gets reinstalled cleanly is just to remove the "/dist" folder.
Last edited by mrdeathjr on 7 October 2020 at 4:58 pm UTC
QuoteThere's a "major" regression fixed for D3D9 titles that caused crashes in many games
So now they can update Proton too, or there's another major problem holding it?
Quoting: BielFPsAFAIK what's holding up Proton is that WINE > 5.09 broke esync/fsync. Proton might get updated, but it will probably still be based off 5.09.QuoteThere's a "major" regression fixed for D3D9 titles that caused crashes in many games
So now they can update Proton too, or there's another major problem holding it?
Quoting: kokoko3kAnybody knows why newer wine versions do not support esync/fsync anymore and if a replacement is in the work?
I asked wine-staging developers, they said the changes in Wine are so significant, that maintaining esync patches is too much work, that's why they were dropped.
See: https://bugs.winehq.org/show_bug.cgi?id=36692#c16
I didn't know fsync stopped working though. That sounds worse. I suppose it won't be a priority until fsync support is actually in the upstream kernel. I don't know why that takes so long.
Last edited by Shmerl on 7 October 2020 at 7:16 pm UTC
Quoting: ShmerlI asked wine-staging developers, they said the changes in Wine are so significant, that maintaining esync patches is too much work, that's why they were dropped.
See: https://bugs.winehq.org/show_bug.cgi?id=36692#c16
I didn't know fsync stopped working though. That sounds worse.
I don't know about fsync, but Keyrock said that.
Anyway, from the link you posted it doesn't sound THAT bad, at least there's hope:
QuoteCurrently the wine-staging "eventfd_synchronization" patch set is disabled. Due to the current and ongoing work in ntdll.so, it will need significant work to rebase
Last edited by kokoko3k on 8 October 2020 at 7:50 am UTC
See more from me