
It can't restart the savestate it just made, but it can also load the savestate just fine if I do it manually.Fixing game-breaking issues in The Godfather: The Game - Part 1 `S SYS: Saved savestate! path='E:/Emulators/RPCS3//savestates/BLUS30023.SAVESTAT'Į SYS: Restart failed: Savestate data is corrupted or it's not an RPCS3 savestate`

I am embarassed to say that I thought of something like this but I just can't find the button/menu item to save a state.Įdit: I found out it's Ctrl + S by looking around the notes for the builds around when savestates were put in.Įdit II: I'll let you know how stable it is for me while starting via this method just for any dev that passes by this topic though, this happens when I save a state: I've also tried the other settings, and I think it's only the driver delay that's relevant for our case. That's what I do and it seems to have significantly delayed the crashes at times. Then enter fullscreen only when you're loaded your save and controlling your character. Just remember to right-click the game and select "Boot with savestate" the next time you launch it. Here's hoping they find a fix before that Make a savestate on the main menu of the game to quickly circumvent the unrecognized controller bug with this game. :( Anyways, if I do find out a better way, I'll be posting it here. I have standard Win10 display settings and it still happens.

I don't specifically recall switching windows while I played but since I stream my gameplay I probably tabbed out for only a few moments to click on OBS or Discord or something.ĭoes it matter if I have Windows 10's magnification enabled? I use a large 1080p monitor that does okay 4K, enough that I have my desktop resolution as 4K with 150%-size icons and play my games at 1080p internally since 4K gameplay streamed at 1080p makes things microscopic. Yeah, since my post I tried a few different things and they all crashed within an hour. I've gathered this from over 4 hours of testing. I've been found that doing so significantly increases your chance of that error.

I've been able to play for around 2 to 3 hours at a time PROVIDED that you do not, under any circumstance, alt-tab or shift windows while playing. The only thing that really delayed it (note that I'm using the word delay, as I've found nothing that will stop the crashing) was setting the driver wake-up delay to 200 or 300.
