Regression: Resistance: Fall of Man - RSX Verification failed (#14104)

Jonathan44062 commented 6 months ago

Quick summary

A user in discord said, in Resistance you got a crash error in Bristol - Devil at the door and London - A desparate Gamble

But I could only replicate the crash error in Bristol, London was fine.

Details

Just playing in Bristol with a few minutes I got this error crash

F {RSX [0x1e3ca70]} SIG: Thread terminated due to fatal error: Verification failed
(in file D:\a\1\s\rpcs3\Emu\RSX\Common\texture_cache.h:383[:7], in function is_expired)

Attach a log file

RPCS3.log

Resistance FOM log no RSX Atomic.zip

RPCS3.log

Attach capture files for visual issues

No response

System configuration

Windows 10 22H2 Intel Core i7-8700 15.93 GiB RAM GPU: NVIDIA GeForce GTX 1070 Ti (545.92)

Other details

I'm gonna share my save file to test better the levels I mentioned https://www.mediafire.com/file/iqiahc8kfifrp9d/BCUS98107_PROFILE.rar/file

kd-11 commented 6 months ago

Just playing in Bristol with a few minutes I got this error crash

How long are we talking? Usually with games like these I struggle to play and if savestates don't work with it, debugging becomes almost impossible.

Jonathan44062 commented 6 months ago

About 6 minutes, that's the time the crash gave me, maybe less RPCS3.log

Darkhost1999 commented 6 months ago

F {RSX [0x22f8e74]} SIG: Thread terminated due to fatal error: Verification failed
(in file D:\a\1\s\rpcs3\Emu\RSX\Common\texture_cache.h:383[:7], in function is_expired)

RPCS3.log The save data provided helped to jump to the level and after about 6 deaths I said screw this and made my own controller profile inside the in-game options. I got past the giant Brute guy who blasted through the gate and was figuring out the timing for these radial mines. When my game froze reproducing the issue

Littlemouse1968 commented 6 months ago

You should try using the "Disable On-Disk Shader Cache" option in the Advanced tab.

andersenvlad commented 6 months ago

Can confirm same crash happens on my system: Happens on a lot of levels not just Devil at the Door.

RPCS3.log

RFoM+RPCS3_Crash

RFoM_Crash

This particular crash is fixed by reverting to release 0.0.27-15031

Littlemouse1968 commented 6 months ago

It's a regression since rpcs3-v0.0.28-15302. Last working version is rpcs3-v0.0.28-15277, but you have to flag liblv2.sprx in advanced tab (due to another regression fixed in rpcs3-v0.0.28-15312).

Jonathan44062 commented 6 months ago

So you're saying, the build 0.0.28-15302 (https://github.com/RPCS3/rpcs3/pull/14104) is the culplit

koksoni commented 5 months ago

Downgrading to version rpcs3-v0.0.28-15277 worked for me

Roman13456 commented 4 months ago

You should try using the "Disable On-Disk Shader Cache" option in the Advanced tab.

Was experiencing the same problem and your advice really works!

aro230 commented 3 months ago

You should try using the "Disable On-Disk Shader Cache" option in the Advanced tab.

Was experiencing the same problem and your advice really works!

Unfortunately it doesn't work for me, so it's not a universal solution, sadly. Still waiting for a potential fix, as this bug makes Resistance more ingame than playable in my eyes

aro230 commented 1 month ago

Shouldn't Resistance be now considered as 'ingame' rather than 'playable'? Just stumbled upon yet another crash, which seems to be the same one but in a completely different level, 'Thames - On The Ice' to be precise.

Nabeel-the-dev commented 3 weeks ago

I found a fix!

Same issue after that minefield section. My system is a ryzen 5 5600, 16Gb ram 3600mhz radeon rx 6700xt When I was playing GOW ascension, I learned a trick to set the driver wake up delay at 200 and increase in increments of 40 or 60 if crashing persists.

Coming to Resistance, the settings on the wiki should do just fine, along with disabling the on disc renderer as mentioned previously. After I landed at 480 wake up delay, I still got a crash, but decided to run it again without changing any settings. So far, I've gotten past 2 chapters after devil at the door without any crashes, even after dying.

Put simply, follow the wiki settings, disable the on disc renderer, set the driver wake up at 200 and try those exact settings one more time. If it still crashes, increase delay by 40 or 60 and repeat. Or just jump straight to 480 and do the same

aro230 commented 2 weeks ago

I found a fix!

Same issue after that minefield section. My system is a ryzen 5 5600, 16Gb ram 3600mhz radeon rx 6700xt When I was playing GOW ascension, I learned a trick to set the driver wake up delay at 200 and increase in increments of 40 or 60 if crashing persists.

Coming to Resistance, the settings on the wiki should do just fine, along with disabling the on disc renderer as mentioned previously. After I landed at 480 wake up delay, I still got a crash, but decided to run it again without changing any settings. So far, I've gotten past 2 chapters after devil at the door without any crashes, even after dying.

Put simply, follow the wiki settings, disable the on disc renderer, set the driver wake up at 200 and try those exact settings one more time. If it still crashes, increase delay by 40 or 60 and repeat. Or just jump straight to 480 and do the same

Thank you for your contribution, but unfortunately this doesn't seem to fix the issue for me. I disabled the on disc renderer, all the other settings are set to the ones from the wiki, but not even the 480 driver wake up helped me. Still crashing in Bristol - Devil at the door.

Probably worth to point out that the same crash happens if you wait for too long in the main menu to watch the sort of highlight intro that shows gameplay footage. Maybe it's the cause for all of this, who knows.

RPCS3 / rpcs3