I was thinking this but what leads me to believe it’s a filing error is it crashes when you choose manual save, every time, and the time played in main menu matches my auto save, kind of like the people who had that initialise new game issue with their saves.
Let’s say G is auto save button and F is manual save button and E is loading game from main menu. Then A is initialise, B is last autosave and C is last manual save and D is empty line or no entry
So ideally the savestates should be for me,
What seems to be happening is
It’s like there’s a line error and something is being ignored or passed over or the wrong state has been filed in the wrong location.
Like the initialise new game error people had in the first week that they fixed, they seemed to have this issue with their save states.
Like I’ve no idea about actual coding but I’ve got a very basic understanding of it, and this is the worst explanation in the world but I believe it is the exact same issue as the Initialise new game issue.
The data is still there, my playtime is still there on the main meni, the buttons are just loading the wrong thing.
The game crashes if I use the button for the wrong thing because nothing is assigned to that button now (as the wrong save is now set to the autosave position and manual save button is now null)
I’m going to wait for the fix, I hadn’t played in a week due to a family funeral but the previous week I’d built about twenty outposts in uncharted space and id like to keep those
My last manual save was a week before I even did any of that so it’s putting me back quite far.
Luckily I’ve a new save I started when I was waiting for legacy saves to become unbugged at launch, which I can finally enjoy as that had hit the progression bug and I couldn’t continue artemis quest about three weeks ago. I’m sure by the time I hit a new bug in my new save, they’ll have patched this save state loading error with my legacy save
Oh I should mention, the game did not crash, I saved and exited perfectly fine.
The hanging I had Mentioned , during 1.55 I believe , was not leading to a crash, but required me to close the application from the PS4 menu as it never recovered (before 1.55 hanging woukd happen the odd time for maybe ten seconds then continue) and while I had not played since last Saturday until yesterday, everything was lovely and smooth with 1.56 and was starting to do the base archive missions (this was not fixed on 1.55 console as implied by official notes)