RPCS3
Metal Gear Solid 4 (NA 2.0) soft-lock during "Breakthrough"
Quick summary
During "Breakthrough," where Snake, Drebin and Naomi are escaping via a APC there is a soft-lock that can occur with specific framerate settings enabled.
Details
During "Breakthrough," when Snake has to destroy a gate while being attacked by an enemy APC before being able to progress. If certain settings are enabled/adjusted, and the player destroys the enemy APC before destroying the gate, the sequence breaks and does not progress as intended https://streamable.com/f5zhez
Using the recommended configuration from the RPCS3 Wiki as a base, if the Framelimit is set to 50, 120, or auto with Vsync enabled, results in the soft-lock. Using Vysnc under any framelimit also lead to the soft-lock. Separately, during testing I was able to get the soft-lock once with only Auto and no VSync, and another time without. I tried to get a log for that instance, but the emulator froze when I was grabbing the information for this issue report. Attached log is using Framelimit 50.
Attach a log file
METAL GEAR SOLID 4 GUNS OF THE PATRIOTS [BLUS30109].log.gz
Attach capture files for visual issues
https://streamable.com/f5zhez
System configuration
AMD Ryzen 5 5600X 6-Core Processor 32 GB Memory NVIDIA GeForce RTX 2080 SUPER Graphics Driver Version - 32.0.15.7216
Other details
No response
As mentioned in Discord, can't reproduce. Just tried auto + vsync and progressed without issues. Also tried matching your settings and still can't reproduce.
Might want to retry without patches for the log, as issues with them enabled are not allowed.
As mentioned in Discord, can't reproduce. Just tried auto + vsync and progressed without issues. Also tried matching your settings and still can't reproduce.
Might want to retry without patches for the log, as issues with them enabled are not allowed.
I'll try an give it another go either today or tomorrow, but I assume using the patch that prevents crashing is still allowed for reports?
Narrowed it down. Since patches do not count for bugs that is my mistake, and I apologize, but it seems the problems start with the "Unlock FPS" patch 1.0 by "TriggerHappy"
Narrowed it down. Since patches do not count for bugs that is my mistake, and I apologize, but it seems the problems start with the "Unlock FPS" patch 1.0 by "TriggerHappy"
If it was the patch, it'd have 100% happened yesterday when I checked for both this issue and the other one in Discord, as I was using it.
Have you verified your game dump?
Yes. Through a long process of testing multiple different things with @ItsLaguna the other day, and only me being able to recreate it after verifying my files, and going so far as to delete every demo666 file, the issues could only be replicated with those settings on my end. Only conclusion we came to was either my PC is doing something bizarre, or my original dump was damaged in some way we can't see.
TL;DR with the settings stated in the original issue I'm able to consistently recreate the soft-lock, but no one else has as of now. Likely a me specific issue.
Closed issue. So far no one else has brought it up or been able to recreate it, and it only presents itself when using a patch that isn't required to get the game running.
Re-opened.
Speaking with another user in the RPCS3 discord yesterday, I was made aware that someone else was able to recreate the issue, that being discord user ArchineerLock. More specifically, they were able to recreate it and have the same CPU as me. (AMD Ryzen 5 5600X)
With new information to work with, at the very least there is now one more person who is able to recreate this issue. This might point towards the softlock corresponding to specific hardware, but at the time of this update ArchineerLock did not disclose what emulator version they were on or other factors.
If you can replicate it again, could you open the RPCS3 debugger and select the MGS4 MAIN thread, then screenshot where it's stuck at?
I have just replicated (accidentally, as is tradition) the freeze twice, and have recorded some footage of the game and debugger. For settings, neither vsync was on, nor did I match any of the other frame limit settings mentioned, using the ps3 native frame limit (and the fps unlock hack). I'll give it another go without, and if that's the issue, I'll assume my footage is unnecessary (unless asked for it).
For the record, my cpu is 5700x3d, so a close cousin of your own.
Retried the scene without fps patch on: It worked Retried the scene with fps patch on to present a log during the freeze: it also worked, unfortunately, so it could've been just "bad"/"good" luck. A third try with the fps patch on, again, presented the freeze in a different position to before, but same effect.
Either way the fps patch "maybe" affects the scenario. I've gotten footage of the debugger twice now, and a log.
