Hey All

I read that quick saving van corrupt your save games.....it was recommended to totally disable all auto saves and not use quick saves at all.

Ive used quick saves since morrowind not anu problems.

Now the reason this is posted in the mod section.....

within 3 years ive come to like using jaxonz's positioner to decorate lakeview manor to the way but always crashes eventually while loading saves.

Now after researching it seems people believe that quick and auto saving is bad.....as started above the only time ive noticed a problem is when ive been redecorating lakeview manor.

It was recommended to place all furniture you wand then use the exterior table to remove the workbenches and start moving and adding new stuff and to be weary of messing with placing lights.

So what does everyone think and welcome any wiadom on this matter.

Qwert

Honestly the idea that quick/autosaves are dangerous is one of those things that are true in theory but that cause problems in practice only extremely rarely. Like, statistically insignificantly rarely.


As you said, you've been using quicksaves and autosaves since Morrowind and have never had any save corruption because of it.


It's like driving a car. Yes, you run the risk of getting into a car accident every time you drive, but we consider a consequent refusal to drive pathological.


The possibility that your issues with Lakeview Manor and crashing are caused by quick/autosaves is astronomically unlikely.

Quicksaves and autosaves are technically exactly like the other saves (except the names aren't unique so the files get replaced).

People have been blaming autosave and quicksave for savegame corruption but that's just because they haven't traced the cause-effect relationship back far enough. Any corruption people are experiencing is most likely because they used quick load, died and let the game auto-load the last save, or used quit to main menu then loaded one game over another. That last case is specially dangerous. When you load a game over top of another memory isn't completely cleared. Various things can be left behind and then when you make a save later (of any type) you end up with bits of information from both saves merged together. That's been true since Morrowind. Most people are blaming the saves for the problems but it's really the loading of one game over another that creates the corruption.

But it's also true that the Hearthfires houses are complex, heavily scripted, and a technical mess with all of the interconnections between the various objects. I would say that if you're using quicksave and quickload in those houses just after crafting or moving something you probably have the optimal conditions for creating the kind of inconsistencies that can break saves. Scripts get paused and their exact state is recorded in the savegame file. In theory other game processes work the same way, but given how complex those locations are I don't think it's unreasonable to assume that occasionally something doesn't get captured correctly. So just to be safe, make sure you stand and admire your work for a moment after making changes to the furnishings so that you give the game a chance to run the scripts and get all of the interconnected objects in the right state before leaving the house or using quicksave.

I have had the same problem using Jaxonz's Positioner on a small house mod that doesn't have scripts. I stopped having crashes with Positioner when I stopped using quicksaves, but I am also very cautious with it now. I make hard saves and exit out of the game if I mess up and have to reload.

Damn guys thanks so much for the insights...im gonna re-read this cuz of the high intelligence put into the writings.

Wow what a great way to start the day.....??

I don't use Jaxonz's Positioner specifically (although it is on my list of mods to try), but I run between 150-200 mods, use quicksave/autosave frequently, and rarely crash.

I am using practically exclusively manual saves from console (to name them to my liking) - and usually forget to and die and have nowwhere close to get back to:-)

Not to seem like I'm changing the subject here, but is it possible this thing where your save crashes on load is related to this: http://forums.nexusmods.com/index.php?/topic/3924850-corrupt-saves-strcount-0xffff-ctd-on-load/ ?

The method you use to save is absolutely irrelevant, but given that this issue with Papyrus string count only just came to light in the last month, it makes me wonder if there aren't a lot more instances where having that run out isn't a problem. Anything using scripts that winds up generating a lot of strings can fall victim to that.

I do disable auto-saves in all my Bethesda games, because I had random crashes when the game was auto-saving in Fallout 3.

But I've never had any problems with quicksaves so far ^^

I don't even think I could play one of those games without using quicksaves

Having to open the menu each time I want to save would be so tedious. I'd rather take the 'risk' with the quicksaves.

Well, that's interesting. Be nice if Beth (or someone) could up that to 32 from 16 so maybe some folks wouldn't have the issue....