Does the game even work on Windows with your GPU?
I can't find any information on whether Pascal actually exposes min16 support on Windows, but Maxwell apparently doesn't so there's a good chance that Pascal isn't supposed to either.
It's possible that the game make some weird assumptions and we need to gate min16 support behind actual fp16 support, but then War Thunder will stop working again because that game just refuses to draw anything unless we report min16 support. Can't really test this properly because I simply don't have hardware that old.
FWIW, the game works fine on RDNA2, I recently fixed an unrelated issue with it.
It worked on Windows last time I checked. I'll test again and let you know.
BTW GTX 1070 is listed as a minimum requirement.
GTX 1080Ti is still pretty capable GPU. For example in proton/wine I reach 80-120 fps in Forza Horizon 5 (on Ultra/High + 2xMSAA) on 1440p.
Can you give the PR above a try? I was able to reproduce the crash when fiddling with D3D12 feature caps and it does seem like my suspicion was correct.
I can confirm that the PR fixes the issue. Tested in both wine-staging and proton experimental-bleeding-edge, which now includes the latest master with this commit on top.
Thanks a lot.
The game crashes when you attempt to drive on track. Happens on any session - single player, special event, academy, etc. I did a regression test and found that commit a7159b80e165bfa311eb1e8f39aceba7e696e555 causes the crash.
Steps to reproduce:
Software information
Assetto Corsa Evo, default settings
System information
Log files
Crash log with
PROTON_LOG=1 %command%:steam-3058630-crash.log
This is with the vkd3d-proton commit preceding the regression (8ff7d792d3a94d8b33ac0443351dfab6e9dfb533):
steam-3058630.log
The game is working properly.
I also tested wine-staging v10.6+ with Steam (Windows) installed on a prefix. The game works properly with the vkd3d-proton commit preceding the regression, and crashes on a7159b8 or later.