Fallout 4

Fallout 4

View Stats:
Autosave question
Is there ANY way to make the game save every five minutes REGARDLESS OF PIP BOY USAGE? Any mod or menu option I've never seen? Just got burned hard by a CTD for the thousandth time. Built a top notch town around Finch Farm over the course of an hour and OF COURSE I CTD just as I'm putting on the finishing touches. Obviously no autosave. Because NOBODY is frequently going into their pipboy while settlement building for long periods :steamsad::steamsad::steamsalty:
< >
Showing 1-15 of 34 comments
yea, i'd like to know this also and for the same reason.
hours of work building lost is more than just a bit disapointing for me.
showler Dec 6, 2017 @ 1:48pm 
I think there is an autosave mod that saves in build mode.
Gordon Freeman Dec 6, 2017 @ 1:52pm 
Originally posted by free_the_beast:
Is there ANY way to make the game save every five minutes REGARDLESS OF PIP BOY USAGE? Any mod or menu option I've never seen? Just got burned hard by a CTD for the thousandth time. Built a top notch town around Finch Farm over the course of an hour and OF COURSE I CTD just as I'm putting on the finishing touches. Obviously no autosave. Because NOBODY is frequently going into their pipboy while settlement building for long periods :steamsad::steamsad::steamsalty:
Have you tried fixing your tato ?
Eminem Dec 6, 2017 @ 1:52pm 
You got couple options if you on PC, this is one of those...

https://rd.nexusmods.com/fallout4/mods/12889
Stormbreaker420 Dec 6, 2017 @ 3:15pm 
Originally posted by showler:
I think there is an autosave mod that saves in build mode.
I'll have to find one.


Originally posted by soge99:
You got couple options if you on PC, this is one of those...

https://rd.nexusmods.com/fallout4/mods/12889
Comments on that aren't overly positive don't want anything that will screw with my game too much or anything.


Originally posted by nobody willsee this video right?:
yea, i'd like to know this also and for the same reason.
hours of work building lost is more than just a bit disapointing for me.
Dude. I feel you. Just now finished remaking my town the way it was.
Ahroovi Dec 6, 2017 @ 3:48pm 
Get a PC that meets specs, or fix your load order and/or mods that are used. I finally came back to Fallout 4, and the first thing I did was get a bunch of mods off Nexus. Total came out to 249(esp/m files, I have 350 or so total mods actually). I installed all of these before even playing the game. They all work together, no CTD's at all, no instability, all I have is a performance hit. (or maybe that's just vanilla idk) With these I was able to make my Sanctuary base have a separate power grid with backups for the siren system alone, separate light power grid with a third redundancy in the works right now, along with timers for said lights at all sites so they only come on at specific times or during storms/bad weather, and separate power for all defense related items.I spent about 3 hours building in there without saving or even leaving workshop mode, no issues.


If you know you have CTD's for some random reason, just take the time to exit workshop mode and hit F5 to quicksave.
Last edited by Ahroovi; Dec 6, 2017 @ 3:52pm
Stormbreaker420 Dec 6, 2017 @ 3:56pm 
Originally posted by Ahravi the waff:
Get a PC that meets specs, or fix your load order and/or mods that are used. I finally came back to Fallout 4, and the first thing I did was get a bunch of mods off Nexus. Total came out to 249(esp/m files, I have 350 or so total mods actually). I installed all of these before even playing the game. They all work together, no CTD's at all, no instability, all I have is a performance hit. (or maybe that's just vanilla idk)
My PC is well past the specs and my load order is as good as it can be. CTD just happens in rare spots. Consequences of some of my less professional quality mods. I don't really get why you seem to have come here to brag about how great your game works xD I mean none of this was about why the CTD happened so your answer here just seems a little weird.
Ahroovi Dec 6, 2017 @ 4:00pm 
My point is it's something on your end causing those CTD's. Even I wasn't confident going in after installing all these mods, and to my surprise, it worked fine.Shows that Fallout 4 is really stable, if not buggy though. And I edited that to say you can just exit and quicksave if the CTD's are causing so many issues for you. The real solution would again be to check what mods you have installed since you just admitted some are low quality.
Which, I have low quality mods too, and some dated from 2015, again, with no issues.
Try remembering if you've done any ini tweaks as well. Not all of them actually help.
showler Dec 6, 2017 @ 4:09pm 
Having the game crash after two hours in the build mode is not the sign of having a potato computer or bad load order.
Exiss Dec 6, 2017 @ 4:41pm 
Originally posted by showler:
Having the game crash after two hours in the build mode is not the sign of having a potato computer or bad load order.
Maybe not a bad load order, but there can be numerous reasons, failing or overheating hardware, something gummed up in the system causiing a loading issue, old or outdated mods can cause these too. I know the CTD battle and it's frustrating, but there's a couple mods that you can set autosave intervals and stuff. I use Simple Autosave Manager, but it seems that each save dumps a lot of information, so my game lags up hard for several seconds each time... I just force a regular save every so often.

If you go into the INI (fallout4/fallout4custom):
[Workshop]
bWorkshopAutoSaveOnExit=1 ;will save each time you exit workshop mode, which helps.

Otherwise, the Fallout 4 Config Tool on Nexus also has an option under Gameplay that allows you to change the numerical number of autosaves in frequency. I know there's an option in the INI somewhere, just forgot what it was in the meantime. I'm not sure if the game itself actually does follow autosave rules in workshop mode though, so that may be the issue. Just pop out of workshop mode occasionally and should be good.
Stormbreaker420 Dec 6, 2017 @ 5:11pm 
Guys. Seriously enough about the CTD it's literally one in a million it barely ever happens that isn't what any of this was about.

Originally posted by Exiss:
Originally posted by showler:
Having the game crash after two hours in the build mode is not the sign of having a potato computer or bad load order.

If you go into the INI (fallout4/fallout4custom):
[Workshop]
bWorkshopAutoSaveOnExit=1 ;will save each time you exit workshop mode, which helps.
This is perfect. I don't want a constant lag every time it autosaves every five minutes so not really into a manager but simply autosaving on workshop exit would be a HUGE help because although I don't use the pipboy much on long build sessions I do tend to pop in and out of workshop mode to fiddle with various things that need normal view or fight an enemy who has wandered into the area. Thanks
Exiss Dec 6, 2017 @ 5:17pm 
No probs, I'm not sure if it's an autosave manager issue, but the "really long pause on autosave" issue has occured for me mostly in survival mode. Haven't really cared enough to troubleshoot it as one I got my CTD issues resolved, I cut back on the autosaves to fall in line more with what they had intended. Hope this resolves your issue though.
Ahroovi Dec 6, 2017 @ 5:33pm 
Autosave performance is an issue in a lot of games, just worse on Bethesda because of how much junk is thrown into the save files. Mine are like 20mb right now, and it increases as you go on normally, and even more with more settlement building. Autosaving writes to disk(or SSD) which causes disk I/O, which uses, CPU power. That jump in usage for a sec can cause stuttering or freezing. Really nothing to troubleshoot. Even if it CTD's doing it just start looking at your save file size, if it's massive that's probably your problem right there. That's just Bethesda, go and run a save game cleaner, VERY CAREFULLY.

Originally posted by free_the_beast:
Guys. Seriously enough about the CTD it's literally one in a million it barely ever happens that isn't what any of this was about.

Originally posted by Exiss:

If you go into the INI (fallout4/fallout4custom):
[Workshop]
bWorkshopAutoSaveOnExit=1 ;will save each time you exit workshop mode, which helps.
This is perfect. I don't want a constant lag every time it autosaves every five minutes so not really into a manager but simply autosaving on workshop exit would be a HUGE help because although I don't use the pipboy much on long build sessions I do tend to pop in and out of workshop mode to fiddle with various things that need normal view or fight an enemy who has wandered into the area. Thanks
If this fixed it for you cause you exit workshop occasionally, what was stopping you from hitting F5 and quicksaving?
Last edited by Ahroovi; Dec 6, 2017 @ 5:35pm
Exiss Dec 6, 2017 @ 5:44pm 
Originally posted by Ahravi the waff:
Autosave performance is an issue in a lot of games, just worse on Bethesda because of how much junk is thrown into the save files. Mine are like 20mb right now, and it increases as you go on normally, and even more with more settlement building. Autosaving writes to disk(or SSD) which causes disk I/O, which uses, CPU power. That jump in usage for a sec can cause stuttering or freezing. Really nothing to troubleshoot. Even if it CTD's doing it just start looking at your save file size, if it's massive that's probably your problem right there. That's just Bethesda, go and run a save game cleaner, VERY CAREFULLY.

The issue isnt a split second pause, its a solid 5-10 second freeze, on a dual SSD RAID 0, ONLY on survival. And now that I've played survival, I don't want to play anything less. I'd be fine with a half second or second pause, that's normal, but not 5-10 seconds.

If this fixed it for you cause you exit workshop occasionally, what was stopping you from hitting F5 and quicksaving?
IDK about others, but repeatedly smashing the quicksave button isn't something I constantly think about doing. Part of being in the game, you get immersed sometimes. And having to hit the button repeatedly every few minutes is a bit of a mood killer. Why should we have to manually quicksave when we can change an option and have an autosave interval shortened? We have an option, we can use it...
Stormbreaker420 Dec 6, 2017 @ 5:46pm 
Originally posted by Ahravi the waff:
Autosave performance is an issue in a lot of games, just worse on Bethesda because of how much junk is thrown into the save files. Mine are like 20mb right now, and it increases as you go on normally, and even more with more settlement building. Autosaving writes to disk(or SSD) which causes disk I/O, which uses, CPU power. That jump in usage for a sec can cause stuttering or freezing. Really nothing to troubleshoot. Even if it CTD's doing it just start looking at your save file size, if it's massive that's probably your problem right there. That's just Bethesda, go and run a save game cleaner, VERY CAREFULLY.

Originally posted by free_the_beast:
Guys. Seriously enough about the CTD it's literally one in a million it barely ever happens that isn't what any of this was about.


This is perfect. I don't want a constant lag every time it autosaves every five minutes so not really into a manager but simply autosaving on workshop exit would be a HUGE help because although I don't use the pipboy much on long build sessions I do tend to pop in and out of workshop mode to fiddle with various things that need normal view or fight an enemy who has wandered into the area. Thanks
If this fixed it for you cause you exit workshop occasionally, what was stopping you from hitting F5 and quicksaving?
What was stopping me was the fact I play with a controller and don't keep any of the keyboard commands besides the console in my head. I had literally no idea you could quicksave like that. And besides, that isnt the issue. I could always have paused and quicksaved but who remembers? Nobody ever thinks a CTD is coming. Best to have an autosave set up in a handy spot than be quicksaving every few minutes.
< >
Showing 1-15 of 34 comments
Per page: 1530 50

Date Posted: Dec 6, 2017 @ 1:10pm
Posts: 34