Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.
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.
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.
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.