https://bugs.winehq.org/show_bug.cgi?id=47471
--- Comment #40 from Sveinar Søpler cybermax@dexter.no --- (In reply to Steve Ebey from comment #39)
(In reply to Sveinar Søpler from comment #38)
(In reply to Matteo Bruni from comment #36)
Sveinar, you said on the mailing list that this bug is not reproducible anymore, correct?
This was fixed with the root signature update 1.1 patch here: https://source.winehq.org/git/vkd3d.git/commitdiff/ c002aee119b638d30eeb7cdc91099449ccafeafc
This requires wine-staging patch: https://www.winehq.org/pipermail/wine-devel/2019-October/152356.html
Steve Ebey: Are you sure you have tested latest GIT + that wine patch?
yes, to latest on all gits, and now, when I even try to run dx12 the game crashs before it even loads, with error 132. I have to compile without mingw and I do not understand why that is. i used to be able to compile with mingw, but since 4.10 I have had issues with mingw throwing segment faults, when it gets to a certain part of the compile for the 64bit portion of wine. I am starting a new job, so time to test will be sparse for me, until the college I work at takes the Christmas break. During Christmas break, about 2 weeks long, I will have unrestricted access to 20+ computers, that I can test various combinations of hardware and distros, to see what is going on with wine. I run Fedora, as that one seems to give me the least amount of problems. I will try Nvidia and AMD cards, intel and amd cpus, and find what works best.
Wine REQUIRES https://www.winehq.org/pipermail/wine-devel/2019-October/152356.html to not crash. This is a patch not in GIT.