Sadly, this doesn't appear to work for me. I either get the same error as before, or the game window opens and then vanishes into thin air (yet the game continues to run in the background, with no way for me to access it).
I have an anti tamper error on steamdeck, I use proton experimental and I followed all the instructions (copy the files to the root, delete the shader cache )
im trying to use that dstorage update, but it not working for me, but the older version of the dll work for me, it probably got something to do with the linux version as people that use latest stable version or even bleeding edge version of linux run the game fine, can you tell what distro you use?
I'm also using linux, used the directstorage update mod, and able to play post-update!
I don't really wanna test it (since it's working for now) but I wonder if the Linux instructions for the directstorage mod are the key for it? I remember I had to move the old DLLs into the compatdata system32 folder, put the new DLLs in the game folder, then use the wine DLL override. I suspect it was the "moving old DLLs to system32 folder" step that fixed crashes. Using Arch Linux, Proton Experimental, stable.
I wonder if the Linux instructions for the directstorage mod are the key for it? I remember I had to move the old DLLs into the compatdata system32 folder, put the new DLLs in the game folder, then use the wine DLL override
Context: The 'wine DLL override' isWINEDLLOVERRIDES="dstorage,dstoragecore=n,b" %command%So what's happening here is that by moving the original DLLs to the 'system32' folder of the prefix, the old DLLs are becoming the 'b' (for built-in), and the 'directstorage' mod's DLLs are becoming the 'n' (for native).
So if the original mod's DLLs failed ('=n,b' prioritizes the native, then the builtin), it fails over to the original game ones that got moved to the prefix.
So if the original mod's DLLs failed ('=n,b' prioritizes the native, then the builtin), it fails over to the original game ones that got moved to the prefix.
You know, I didn't think too hard about it at the time, but you're entirely right. It's probable that, even though I installed the newer DLLs, I've been falling back to the old DLLs this whole time. Whelp, lmao.
This should mean, though, that installing these to system32 would (probably) let you play normally, even if the DLLs in the game's directory change! (Plus, if proton gets an update, or if the DLLs change again to a working version, it should seamlessly swap back to the native versions!)
Oh so this is what's been causing the game to crash my machine on boot even tho i unnistalled all my mods and verified files? Oke then if so good to know
20 comments
WINEDLLOVERRIDES="dstorage,dstoragecore=n,b" %command%
Still wont launchProton version
Mesa driver
Pc spec
Did you delete shader.chace file sometimes shader.chace2?
I don't really wanna test it (since it's working for now) but I wonder if the Linux instructions for the directstorage mod are the key for it? I remember I had to move the old DLLs into the compatdata system32 folder, put the new DLLs in the game folder, then use the wine DLL override. I suspect it was the "moving old DLLs to system32 folder" step that fixed crashes. Using Arch Linux, Proton Experimental, stable.
Hope this helps!
WINEDLLOVERRIDES="dstorage,dstoragecore=n,b" %command%So what's happening here is that by moving the original DLLs to the 'system32' folder of the prefix, the old DLLs are becoming the 'b' (for built-in), and the 'directstorage' mod's DLLs are becoming the 'n' (for native).So if the original mod's DLLs failed ('=n,b' prioritizes the native, then the builtin), it fails over to the original game ones that got moved to the prefix.
'The more you know' jingle.
You know, I didn't think too hard about it at the time, but you're entirely right. It's probable that, even though I installed the newer DLLs, I've been falling back to the old DLLs this whole time. Whelp, lmao.
This should mean, though, that installing these to system32 would (probably) let you play normally, even if the DLLs in the game's directory change! (Plus, if proton gets an update, or if the DLLs change again to a working version, it should seamlessly swap back to the native versions!)