Sarek9-15-r1 Released
Stable Build:
The first revision of Sarek9-15, so what has been done?
First of all big thanks to Artewar67 for the fix to this bug:
Sometimes, when using WineD3D, the maximum supported OpenGL version is capped at 4.4 instead of the expected 4.6.
This was fixed by changing the following line in the wine.inf file:
HKCU,Software\Wine\Direct3D,"MaxVersionGL",0x10001,"460" to HKCU,Software\Wine\Direct3D,"MaxVersionGL",0x10001,"0x40006"
Additionally, i have make some changes to the Proton file, mainly related to DXVK. Specifically, line 936 has been updated from:
dxvkfiles = ["d3d11", "d3d10core", "d3d9"] to dxvkfiles = ["d3d11", "d3d10", "d3d10core", "d3d10_1", "d3d9"]
This ensures all DX10 files from the older DXVK versions are correctly called. The latest DXVK versions only include "d3d11", "d3d10core", and "d3d9", while the older ones also contain "d3d10" and "d3d10_1".
Stable Async Build:
This build is similar to the stable version but uses DXVK 1.10.3 Async instead of the regular one.
Why DXVK Async?
The main reason is performance. DXVK Async enables asynchronous shader compilation, while the regular DXVK uses synchronous compilation. In regular DXVK, when a game encounters new shaders, they are compiled synchronously, causing brief stutters or freezes as the game waits for the compilation to finish. In contrast, DXVK Async compiles shaders in the background, allowing the game to continue running, though there may be minor graphical artifacts until compilation is complete.
So why isn't it in the normal version?
While DXVK Async significantly improves performance by reducing stuttering, it poses a potential risk of triggering client-side anti-cheat systems in multiplayer games. This risk arises because the tool alters shader handling, which might be viewed as cheating by some anti-cheat software. Although there haven’t been confirmed bans for using DXVK Async, the possibility remains, and I personally wouldn’t risk my Steam account for it.
Testing Build:
Once again, there's no need for a public testing build. We currently have a private build with experimental configurations that might provide a slight performance boost, but it's still very unstable.