Open smec44 opened 1 year ago
I am having the same issue, my system info
My proton log
Apparently there is no problem on my Steam Deck, but I don't think it's specifically NVIDIA because this guy has AMD GPU and also has the same problem
~Hello @smec44, Version: Windows XP
in your log looks abnormal. It's expected that Proton Experimental gives the game a Windows 10-like wineprefix and that could be fatal for a game using d3d12. Can you try to move/remove the game's wineprefix and let Proton generate a new wineprefix?~ Second Proton log makes that less relevant.
@kisak-valve Would love to but I've already switched Proton versions 5 times already and am afraid of triggering Denuvo. I'll try with a fresh prefix tomorrow but for now the game is running with -dx11 on 7.0-6.
@smec44 Did you use NVM apparently it's just a suffixed flagVKD3D_CONFIG=dxr11
prefix? I tried it with 7.0-6 and it still did not work
Proton 7 works fine, but Bleeding edge causes the game to simply not boot at all and return the play button to green. Guess there was a regression.
I have the same issue but with a different GPU on the demo. My information:
GPU: Intel Arc A770 Driver/LLVM version: Mesa 23.1.0-dev version I compiled on Feb-15-2023 Kernel version: 6.2.0-rc2+ from drm-intel branch I compiled on Feb-15-2023 Link to full system information report as Gist: Proton version: 7.0.6
Proton Experimental looks like it hangs, but Proton 7 does show a window before unexpectedly closing. Steam Deck works fine.
Hello @simonlui, wine: Call from 0000000170032138 to unimplemented function CFGMGR32.dll.CM_MapCrToWin32Err, aborting
looks like a line of interest from your log.
@kisak-valve Here's a gist with Proton Experimental in case that helps.
After looking around a bit and pondering the Proton 7.0-6 log, I suspect that you're also affected by something similar to https://gitlab.freedesktop.org/mesa/mesa/-/issues/8094#note_1726007.
Dang, wasn't expecting XeSS to be at fault but it makes sense. I guess I can try and play around with renaming DLLs and whatnot but it feels really hacky to try that.
Edit: Renames of the DLL as suggested in the Mesa issue and variants of the rename doesn't work in this case, it feels like something else.
Crash on experimental should be fixed in upstream vkd3d-proton now.
I had no trouble launching and playing the game on 7.0-6 on launch day with 6900xt and mesa 22.2.5. No launch options needed but did have to manually add several missing dlc....
Compatibility Report
System Information
I confirm:
steam-1805480.exp.log
Symptoms
Game will either produce an error window "game needs the following to run: visual c++ runtime" or do nothing. Same behaviour with 7.0-6, experimental, and GE-49 Same behaviour on Steam Deck despite being verified
edit: running with -dx11 gets the game to launch
Reproduction
Click play