Ratchet & Clank Trilogy: Part 3 crashing

[stuffi3000]

Quick summary

The third installment of the Ratchet & Clank Trilogy keeps crashing after playing for a few minutes.

Details

I recently tried to pick up Ratchet & Clank 3 again to continue where I left off two years ago. However, after playing for a few minutes, the game simply freezes and then crashes, with the sound still playing in the baclground until the sound file is done, then it stops. The issue happened while I was playing in the arena, after from a few rounds to a quater of the final challenge, but also while continuing the story on a planet where you have to use a tool to aim lasers at satellites, or in Blackwater City.

I tried to sick as closely to the default settings as possible, together with what is indicated on the Wiki. The following parameters are not on default settings: SPU Block Size: Mega (not from wiki but saw it suggested) ZCULL Accuracy: Relaxed (from wiki) Framelimit: 60 (from wiki) Resolution scale: 300% (3840*2160).

While researching the issue I tried playing with block size settings, with the ZCULL accuracy, with VSync and with having the game it full screen or not. I can't seem to narrow it down to a specific action, although it seems to have happend twice when I tried to select the holoshield projector in my weapon wheel in the arena, but trying again after a crash to just selecting to holoshield projector doesn't cause a crash. Apart from that, it just mostly seems to be random. In my latest try, I managed to get though the level with the satellites, and went to Blackwater city to fend of the aliens. After beating the first round, I quickly crashed in the second.

If I recall correctly, I didn't have these crashing issues before. I for sure didn't have them for the first and the second game (played on built 0.0.28-xxxxx before).

Any help would be appreciated. I can do further testing if needed.

Attach a log file

RPCS3.log

Attach capture files for visual issues

No response

System configuration

Windows 11 AMD Ryzen 3600 GTX 980ti (driver 555.99) 32GB RAM

Other details

No response

[AniLeo]

One thing is wrong in your log, you placed RPCS3 inside a Windows directory with special permissions (Program Files). Portable software such as RPCS3 should NOT be placed there.

As for the crash, if still occurs, try RSX FIFO Mode: Atomic, SPU XFloat: Accurate and SPU Block Size: Safe.

Furthermore, if it still occurs, and it's a regression, we will need to know what's the last build that doesn't crash, in order to pinpoint the breaking change and assign a developer.

[stuffi3000]

One thing is wrong in your log, you placed RPCS3 inside a Windows directory with special permissions (Program Files). Portable software such as RPCS3 should NOT be placed there.

As for the crash, if still occurs, try RSX FIFO Mode: Atomic, SPU XFloat: Accurate and SPU Block Size: Safe.

Furthermore, if it still occurs, and it's a regression, we will need to know what's the last build that doesn't crash, in order to pinpoint the breaking change and assign a developer.

Hi, thanks for your answer.

It's not in a protected Windows directory: only the program files folder on the C:\ drive has special protection. My installation is on E, in a program files folder I created myself to mirror the file organisation from my main drive for other software.

I'll try it with these settings and I'll get back to you.

As for the regression, I don't really know how I'm supposed to go through 2 years of version history to find the exact built that causes the crash. What I can do, however, is trying to play on the built I previously played on if I can find it. Will keep this issue updated here too.

[stuffi3000]

One thing is wrong in your log, you placed RPCS3 inside a Windows directory with special permissions (Program Files). Portable software such as RPCS3 should NOT be placed there.

As for the crash, if still occurs, try RSX FIFO Mode: Atomic, SPU XFloat: Accurate and SPU Block Size: Safe.

Furthermore, if it still occurs, and it's a regression, we will need to know what's the last build that doesn't crash, in order to pinpoint the breaking change and assign a developer.

I tried with your settings and was able to play for a solid 30 minutes before the crash happened again.

I attached my most recent log file. RPCS3.log

[stuffi3000]

I tried with version 0.0.25-14524, using the same settings, and the same issue occurs after a few minutes of playing. I'd like to send the log file, but it's over 500MB big....

[Risusama]

As for the regression, I don't really know how I'm supposed to go through 2 years of version history to find the exact built that causes the crash. What I can do, however, is trying to play on the built I previously played on if I can find it. Will keep this issue updated here too.

@stuffi3000 You don't have to start by going through every single build. As you said, you can try to find the build it worked on for you previously. Then hop to a newer version, in like a week intervals or something like that. When you find a build that is broken, backpedal a little bit and try to pinpoint the last build that worked.

As for log files, you might be able to reduce its size quite drastically if you compress it.

[stuffi3000]

Thanks for the information @Risusama.

I have tried this time with version 0.0.20-13325, but the crash still occurs after around 30-40 minutes of gameplay.

I have compressed and attached my (1.8GB) log below: RPCS3 0.0.20 log.zip

Here's also my log from 0.0.25: RPCS3 0.0.25 log.zip

I previously didn't play the game on a version lower than 0.0.20, so the crashes were probably already happening when I first played (and probably the reason why I stopped at some point). That seems to indicate that it's in fact not a regression.

Is there anything else I can do to help?

[Hasster1]

Could this issue be related to https://github.com/RPCS3/rpcs3/issues/12585 ?