On Mon Jun 29 19:04:33 2026 +0000, Tim Clem wrote:
Philosophically I don't know how to feel about this. Many apps that ship their own d3dcompiler or d3dx will break, and I imagine Proton will end up just reverting this. Games we've seen thus far that have broken: - Crusader Kings II (graphical corruption; d3dcompiler) - Final Fantasy 15 (crash; d3dcompiler) - Star Wars Outlaws (this actually seems like a loader bug - we pick builtin d3dcompiler now, and that tries to go looking for wined3d.dll without changing the search path) - Assetto Corsa (crash; missing D3DX11CreateShaderResourceViewFromFileW) - They Are Billions (crash; needs working ID3DXEffectCompiler) Otherwise we'll never learn about those issues and it will never get fixed. It will be easy to revert for the next major release, if it comes to that.
From this list only ID3DXEffectCompiler looks annoying, because it will need substantial amount of changes, to get it right. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10967#note_144460