Menu
What's new
By:
Filters
the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Super slow saves 2.0.0

Sort by date Sort by votes
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.
 
Upvote 0 Downvote
jshwea said:
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.
Click to expand...
Didn't FF7 have a similar issue on PSX?
 
Upvote 0 Downvote
smitty420 said:
Didn't FF7 have a similar issue on PSX?
Click to expand...
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.
 
Upvote 0 Downvote
yaugieLC said:
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.
Click to expand...
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.
 
Upvote 0 Downvote
Lowjax said:
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.
Click to expand...
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.
 
Last edited:
Upvote 0 Downvote
kinggath said:
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.
Click to expand...
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.
Did you wait for the plots to start building? That might make a difference, I don't think I ever saved before they started construction, but during and after.

I'll try loading it back up. I didn't try it after restarting my computer, it's possible FO4 holds something in virtual memory even after exiting the game that could effect something.
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
kinggath said:
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.
Click to expand...
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.
 
Upvote 0 Downvote
kinggath said:
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.
Click to expand...
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.

How do I check what type of hard drive I have? I have to imagine it's at least ssd, gaming laptop (lowish end, for a gaming laptop) about a year old, but not sure how to check.

Edit: just did it again, instead of quick save I slept to kick off an autosave, that took just under 2 minutes, immediately followed with an exit save that took about 20 seconds. I've no idea why it's not working for you...
 
Last edited:
Upvote 0 Downvote
Tarkkh said:
yes its know and the team is looking into it as far as I understood!
Click to expand...
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.
 
Upvote 0 Downvote
For now I've made my peace with the issue and adjust my play style accordingly. Try not to save at any settlement, try not to fast travel from there and so on.

The bugger is, it doesn't always happen. Usually, after fast travelling to any settlement, the first save finishes normally. The next one doesn't and takes minutes. It's still worst with autosaves and fast travel, when it can take up to five minutes for it to kick in.
 
Upvote 0 Downvote
When my game freezes during saving for ages but eventually recovers, task manager invariably shows fallout4 as 'not responding' and the cpu usage drops significantly conmpared to normal. I have no idea what this means:)

diziet
 
Upvote 0 Downvote
You must log in or register to reply here.
Top