- Messages
- 147
Since updating, super slow saves. I mean quick saves, real saves, etc. 20+ mins!!
Didn't FF7 have a similar issue on PSX?Maybe worth a look at old problem Going to post this here
On the PS3 Skrim had a save problem with the longer you played, the more data it had, would cause saving issues.
I know it was not the same engine but it is similar. Bethesda did eventually patch it.
Looking at how they patched it might give a led to what is going on.
Just saw a video talking about it, thought I would mention it.
It's actually a reasonably common issue, and an easy one for internal testing to miss, since it requires playing one save for a substantial period of time - something you don't tend to do when trying to beta-test unless trying to test something else that requires that.Didn't FF7 have a similar issue on PSX?
FF7s was famous. If you were on the 3rd disc, you absolutely had to keep a save outside of Sephiroth's crater and then finish the entire crater in one shot because any save inside the crater was virtually guaranteed to be corrupted. I learned the hard way, thinking I could keep 3 seperate save files and surely one of them would work. Nope, every time, as soon as hit a certain screen, your save was ruined forever. I wound up getting the PC version 6 months later because it didnt have that problem. iirc the PSX memory card was only 128k, divided into 16 8k slots and FF7 only used one at a time. One game that I can barely remember (Tecmo's Deception maybe) used 15 of the 16 slots. I think they learned their lesson cuz FF8 saved on mulitple slots, and 9 was far more cartoony.It's actually a reasonably common issue, and an easy one for internal testing to miss, since it requires playing one save for a substantial period of time - something you don't tend to do when trying to beta-test unless trying to test something else that requires that.
Yes my save was corrupted. And I've been having many issues with it! Damn glad I asked this question, I forgot about corrupted saves. derpMaybe try saving again in fallout and loading it in resaver. If a save won't load via resaver, it's usually corrupted.
Just tried repeating these steps and I'm not getting a long save - which is a bummer, if I can get a repeatable on such a small load order its exactly what will allow me to fix this. Was the long save occurring when you did quicksave, save from main menu, save from console, or by triggering an autosave from something?slowsaves2 - Both the save and the exit save were slow, unfortunately I had not turned on logging.
slowsaves3 - Loading back to before the slow save I did effectively the same thing, only with logging turned on, contains the log files, only the normal save was slow, exit save was slightly slower than normal, but only meaning it took two or three seconds.
slowsaves4 - Same as 3, except I waited for construction to finish before saving.
Edit three : If you want to recreate the long save for yourself, load the older save, kill the protection in your sights, loot him and the mailman, then go build three residential plots. I've done that four times from that save and it long saves every time.
I don't know, it happens to me every time I did it like six times in a row. Kill the protecton, build a couple residentials save (quick or normal, I did both) then exit save. At least one of the saves should be slow, usually both.Just tried repeating these steps and I'm not getting a long save - which is a bummer, if I can get a repeatable on such a small load order its exactly what will allow me to fix this. Was the long save occurring when you did quicksave, save from main menu, save from console, or by triggering an autosave from something?
Also, which save in particular should I use? I used the Autosave from slowsaves3.zip, as that had the oldest timestamp on it.
Some of us have that on a larger scale. The lag between closing of the pipboy and the load screen can take up to several minutes. Especially when trying to fast travel from larger settlements.I think I got it to trigger after fast traveling. There's a weird delay after selecting the location where the pipboy drops down and the game seems to hang for a moment before going to the loading screen.
Sorry, reloaded it, killed the protectron looted him and the mailman then built three residential plots. Saved as soon as at least one started building, quick save took about a minute and a half followed immediately by an exit save that took just over two minutes.Just tried repeating these steps and I'm not getting a long save - which is a bummer, if I can get a repeatable on such a small load order its exactly what will allow me to fix this. Was the long save occurring when you did quicksave, save from main menu, save from console, or by triggering an autosave from something?
Also, which save in particular should I use? I used the Autosave from slowsaves3.zip, as that had the oldest timestamp on it.
Same here, but I noticed a randomness. Sometimes saving takes the same speed as normal.Since updating, super slow saves. I mean quick saves, real saves, etc. 20+ mins!!
yes its know and the team is looking into it as far as I understood!Since updating, super slow saves. I mean quick saves, real saves, etc. 20+ mins!!
They’ve been looking into for 35 days, we know a lot of the specifics, and there are thousands of posts about this very subject. Go to the Latest Patches forum and you should find everything you want to know about it, except when it’s going to be fixed, since the dev team can’t replicate the issue and they’re relying on our save files to figure it out.yes its know and the team is looking into it as far as I understood!
Old post Tarkkh.yes its know and the team is looking into it as far as I understood!
another old post Tarkkh.yes its know and the team is looking into it as far as I understood!
We use essential cookies to make this site work, and optional cookies to enhance your experience.