CrossOver Support - Community Forums

Is there any chance we can get access to the Mac-specific DXVK source so that we can apply the async patch found here: https://github.com/Sporif/dxvk-async

Or is there some way we could get a Mac specific DXVK build with the async patch applied? Would help quite a bit with d3d11 games that suffer from a lot of shader compilation stutters.

I know this is not exactly what you're looking for, but here are some different builds of DXVK built by Codeweavers:

http://ftp.codeweavers.com/pub/crossover/dxvk/

I've tested the DXVK 1.7 build successfully, but it only partially resolved one bug.

Devyn Mapes wrote:

Is there any chance we can get access to the Mac-specific DXVK
source so that we can apply the async patch found here:
https://github.com/Sporif/dxvk-async

Or is there some way we could get a Mac specific DXVK build with the
async patch applied? Would help quite a bit with d3d11 games that
suffer from a lot of shader compilation stutters.

The reason the asynchronous patches were removed from upstream DXVK is people who used it were banned.

If your willing to take the risk of getting banned you could downloaded the released crossover-sources-20.0.4 add the asynchronous patches then compile, you’ll only need the 64Bit dlls and not the d3d9.dll, after setting DXVK to enabled for a bottle you’d need to manually resolve the bottles system32 dlls with the once you built.

Eric Volker wrote:

I know this is not exactly what you're looking for, but here are
some different builds of DXVK built by Codeweavers:

http://ftp.codeweavers.com/pub/crossover/dxvk/

I've tested the DXVK 1.7 build successfully, but it only partially
resolved one bug.

A lot of the bugs with DXVK on macOS is due to the lack of transform feedback in MoltenVK.

I'm aware that they async patches were removed from DXVK for that reason; they still have a place in single player games though, IMO. Those async changes are a part of one of the pretty popular proton forks for a reason; they make some games playable that would otherwise stutter far too much.

I was under the impression, after reading many comments on github issues and commits, that the mac-specific dxvk changes were not bundled in the crossover source code. I never ran a diff between the crossover dxvk source and the normal dxvk source though, so maybe the changes are there.

I'll run a diff and compare the source code to see.

Edit:

After running a diff, it does appear that the changes are bundled with the crossover source code. I'll just re-build it with the async patch then.

Devyn Mapes wrote:

I'm aware that they async patches were removed from DXVK for that
reason; they still have a place in single player games though, IMO.
Those async changes are a part of one of the pretty popular proton
forks for a reason; they make some games playable that would
otherwise stutter far too much.

I was under the impression, after reading many comments on github
issues and commits, that the mac-specific dxvk changes were not
bundled in the crossover source code. I never ran a diff between the
crossover dxvk source and the normal dxvk source though, so maybe
the changes are there.

I'll run a diff and compare the source code to see.

Edit:

After running a diff, it does appear that the changes are bundled
with the crossover source code. I'll just re-build it with the async
patch then.

I’d rather be safe by providing the reason it was removed.

Yes the sources got added later after I’d opened a support ticket for the lack of DXVK sources.

I’d skipped dealing with async patches as it’s hard enough to get users to read the current documentation...., but it would be interesting to hear if it ends up making any impact or not on macOS. As esync makes almost no impact for macOS.