The Elder Scrolls V: Skyrim

The Elder Scrolls V: Skyrim

View Stats:
sonofbalder May 19, 2014 @ 6:20pm
should i disable the autosave ?
and if yes why
?
< >
Showing 1-15 of 20 comments
wowszer May 19, 2014 @ 6:36pm 
No. But you shouldn't rely on it either. You should save regularly and also for important events, and keep them. So many say they haven't got a save just before an event, or seem to only rely on auto save and quick save. They are easily saved over, then gone.
sonofbalder May 19, 2014 @ 6:42pm 
thanks
Incunabulum May 19, 2014 @ 6:49pm 
Yes, autosave can cause problems with saves and CTD's - not for everyone and not all the time but it happens a decent amount.

At the very least, only keep the 'save on travel' option - that only autosaves when you fast travel or go through a door (area transistions).

Doesn't mean you can't *quicksave* and you should be doing that all the time anyway. Vanilla Skyrim is unstable as hell and modded Skyrim doesn't make it better. If you're not hitting quicksave every couple of minutes you're setting yourself up for a world of pain.
Jim713 May 19, 2014 @ 6:51pm 
Nope don't disable it god theres been many times that it kept me from screwing up the come. Plus also has been needed when a file corupts and I need to go back.
Jim713 May 19, 2014 @ 6:54pm 
Oh by the way don't rely on quick save alone. Do lots snd lots of normal saves, so if file or two get corrupt you can go back not to far in gam.
Marcy May 20, 2014 @ 12:55am 
I wouldn't recommend doing that.
What I usually do is make a hard save (manually from the pause menu) every time I enter a different region, progress on a level or quest, etc.
And quicksave when I'm just traveling around.

I don't rely on autosave at all, but I like having it turned on so that I at least have SOME certainty of being able to go back.
Zerwaxle May 20, 2014 @ 1:01am 
I use the Skytweak mod so I sort of got used to just manually saving and it's not that bad, so it's up to you, but I sort of think Incunabulum might be right... sort of... he/she sounds right... I think.... kablabalbalabl.
gnewna May 20, 2014 @ 1:42am 
If it's not causing any problems, there's no reason to disable it (but as others have said, make sure you have 'hard' saves - done through the menu - as well... if disabling auto-saves helps you to remember you need to do that, then I guess that's another reason to disable it) but if you frequently crash when entering a building/city/etc or at other auto save points, it's worth a try, as without auto saves on transition I find I have about 95% fewer CTDs on transition.
★Kelvy★ May 20, 2014 @ 2:32am 
I have my auto saves set at 15 mimutes and manually save over them (approx. 3 auto saves)
Ilja May 20, 2014 @ 3:52am 
I would estimate that 99 % of players that have problems with autosave and/or sleep are the same ones telling to us that their textures are 100 % compatible, having multiply hair mods is okay and they communicate with words "LOL No Patches U Mad?"

Then they whine, how Bethesda is **** and we are all *****, because we can't help them.

Anyone who does not find themselves from that description can keep their autosaves active. Lucky for us, that amount still seems to be the grand majority. :)
Last edited by Ilja; May 20, 2014 @ 3:53am
SpeedFreak1972 May 20, 2014 @ 4:00am 
Well I use the ingame save system tried an alternative save mod however that ctd's a lot.
Mumbles May 20, 2014 @ 5:12am 
Originally posted by Ilja (Ref):
I would estimate that 99 % of players that have problems with autosave and/or sleep are the same ones telling to us that their textures are 100 % compatible, having multiply hair mods is okay and they communicate with words "LOL No Patches U Mad?"

Then they whine, how Bethesda is **** and we are all *****, because we can't help them.

Anyone who does not find themselves from that description can keep their autosaves active. Lucky for us, that amount still seems to be the grand majority. :)

That's hardly accurate - there were huge problems with crashing from all the autosaving when the game released. Watched it happen consistently on both PS3 & PC - I personally don't have autosaves on and don't really need them. If you're running a lot of scripted mods I'd recommend turning them off if you're pushing your comp's limits - since I've watched the game CTD whenever it tries to autosave on top of scripts starting up in newly loaded areas.

But yeah - if you don't get CTD's in new areas - don't worry about it. If you're experiencing CTDs upon entering an area or waking & are running things like Frostfall + Wet & Cold and whatever else - I'd say turn them off.
gnewna May 20, 2014 @ 5:14am 
Ref, mostly, probably, yes, but even when I was running completely vanilla I used to reflexively menu-save before going through just about any transition because of all the crashes (although I suppose I didn't have the unofficial patches at that point, either). (It did take me a while to discover that it might be the autosave rather than the transition that was the problem, and now I've got my autosaves off, I hardly ever have those particular CTDs.)
VisciousFishes May 20, 2014 @ 5:24am 
I save when sleeping and save on wait but not on travel or the timed auto save in character menus. f5 is my friend in most situations that I need and I do a console save every now and then to make sure I have a named save game for hints when I take breaks away from the game. Like when a new title comes out I am keen to play and Skyrim gets relegated to the "whenever I can be bothered" pile of games. I had far too many problems back when Skyrim got launched to be using the save on transition/travel.
Ilja May 20, 2014 @ 5:41am 
@Mumbles: Yes. There was a lot of crashing with autosaves, when game was released. We a running third year from that point and most bugs have been fixed with unofficial patches.

I have a very heavily scripted game, with a lot of active scripts. Frostfall, Realistic Needs and Diseses, Wet and Cold + Ashes + Holidays, several different cloak and NPC scanning effects, large variety of LL mods and so on. My machine is far from any kind of a beast, but it is not crashing - merely sometimes lagging near waterfalls, because I am too stubborn to remove a certan file from my game.

This happens, because I keep my mods in strict order. I do not simply install what looks cool, but I collect, test and install them as thematic body. Each and every one of them is listed as compatible/support to central mod in that body. For example, all my survival mods are compatible with Frostfall, or made support it. My master files are cleaned withd TES5Edit and I also clean all orphaned scripts from my saves regulary with Save game script cleaner.

In 2014, badly planned mod bodies and bloated saves will certainly still crash the game. But, can we really blame autosave for that? More top of that, it is not about the amount of scripts in game, but the quality of active scripts in game. It is usually wise to wait for a moment, before installing a new nice looking mod. Scripts might have some troubles that other users and WIP testers will notice.

@gnewna. You are right. There are still problems with vanilla Skyrim and autosaves. I admit that I neglected that above.
Last edited by Ilja; May 20, 2014 @ 5:43am
< >
Showing 1-15 of 20 comments
Per page: 1530 50

Date Posted: May 19, 2014 @ 6:20pm
Posts: 20