https://bugs.winehq.org/show_bug.cgi?id=48160
Nocifer apmichalopoulos@outlook.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |apmichalopoulos@outlook.com
--- Comment #12 from Nocifer apmichalopoulos@outlook.com --- As I am the OP of https://bugs.winehq.org/show_bug.cgi?id=48180, which has been marked as a duplicate of this one, I will report here that unfortunately this patch fails to resolve the issue reported in that other thread. I applied the patch to the most recent git sources and ran the .exe in a new, clean prefix.
As previously suggested, I also ran a WINEDEBUG=+d3d11,d3d,d3dshader but it exploded into a 6,5GB file, so I ran it again with only warn+d3d11,warn+d3d,warn+d3dshader. The resulting log provides nothing other than some d3d shader warnings which are probably due to wine not having full support for d3d11. To confirm this, I ran the WINEDEBUG in a clean 4.19 prefix and the resulting debug log is identical to that produced by running it in a 5.0-rc1 prefix with the patch applied.
I can provide any tracelogs or whatever else you may require.