On Mon Jun 29 19:15:09 2026 +0000, Tim Clem wrote:
Right, clearly we'd like to find these sorts of issues, but to me it's a question of whose responsibility that is. Do we want to break things widely and at random and let users deal with the frustration? Or should we, the developers, be seeking out games that ship their own d3d libraries and setting builtin overrides to see what happens?
only ID3DXEffectCompiler looks annoying, because it will need substantial amount of changes, to get it right. That's the sort of thing I worry about - that's sounds like something that will be broken for a while, which means we're effectively requiring that users tinker with DLL overrides to get something working that used to be fine out-of-the-box. Do we already have WineHQ bugs for each issue? Also, do all of those games actually come with their own copy of d3dcompiler_xx.dll / d3dx*.dll?
Ideally we'd fix most of the new issues before Wine 12 is out. In the meantime, downstream is certainly free to revert this, but better yet would be to help with the fixing, as that will actually move Wine's implementation forward and help with other games requiring the same features. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10967#note_144463