https://bugs.winehq.org/show_bug.cgi?id=57834
--- Comment #16 from Shmerl shtetldik@gmail.com --- (In reply to Zeb Figura from comment #15)
Meanwhile, all of the big 3 problems I listed have been fixed, several years ago in fact, and Wine's d3d11 implementation is actually quite good. But nobody has noticed, both because everyone's attention is on DXVK, and because optimal performance still relies on Vulkan, which can't be the default yet. And when there are bugs—and several users I am infinitely thankful towards are still reporting them—I simply don't have the time to do anything about them.
Thanks for clarifying that it's more of a resources / focus problem and not really some conceptual blocker like compatibility needs. The latter is somehow indeed a common a perception and it's good that you explained that it's wrong and Wine can have good performance without being blocked by MoltenVK and similar cut down Vulkan backends.
Most of the new the games these days are D3D12 anyway, so that really is the biggest elephant in the room, but D3D11 is of course still quite important too.
If at some point upstream Wine will catch up to dxvk / vkd3d-proton from resources standpoint, I'd be interested in trying using that to compare / report issues.