Jump to content

False "save corruption" during gameplay


Ramagast

Recommended Posts

  • Replies 1.3k
  • Created
  • Last Reply

Top Posters In This Topic

Probably not helpful some random thoughts

1. Skyrim's engine can decide and tell whether a save file is corrupt or not, after loading it, by displaying in-game message "save file is corrupt and can not be loaded", and refuse to load the save.

2. Our case is similar but different in that Skyrim's engine can tell its corrupt before loading the save game.

3. In our case, Skyrim tells that all our save games are corrupt, even a vanilla save saved right after Helgen cart ride sequence and the character creation menu.

4. On the other hand, restarting Skyrim "fixes" this issue.

5. There seems to be no direct trigger for this symptom to occur. If a player does X and the game gets corrupted, the player can restart Skyrim and do X again, without corrupting the game.

6. There are some common symptoms that occur frequently along with corrupted game.

6-1. Some dialogue options become missing

6-2. Some message boxes display nothing, instead of their usual text messages.

And all these thoughts lead me to believe there's some kind of fault in garbage collection system in Skyrim engine, which in turn makes me believe this problem is nearly impossible for end users to solve. I mean, what makes any saves "corrupt" to begin with? What makes Skyrim engine display that bugger of the message box saying "this save is corrupt and blah blah"? It's all occluded to end users: the game just tells you it's broken, not giving you any reason why it's broken or any clue to how to fix the problem.

My best bet to consult this problem would be Bethesda's engineer. Anyone made a contact on their official forum yet?

Edited by unblest
Link to comment
Share on other sites

I didn't have this problem before the 1.2 patch.
If this is some kind of vanilla problem, it once again raises the question of why it only affects so few people.

I wanted to try Bethesda forum, but didn't find the place for this topic. Technical support topic directly states that they're not dealing with mod-related problems.

Link to comment
Share on other sites

Oops. My bad. :) Anyway, I thought the reason for posting there was that it isn't a mod-related problem, but something the engine isn't handling well. It may be *triggered* in heavily modded games, but that's not the same thing. If you write to the council because your pram gets caught in a big crack in the pavement, they're not supposed to say "your fault for having a pram." They need to fix the pavement. If possible. Anyway, it's done now, and we'll see what they say.

 

Lethiel

Link to comment
Share on other sites

I cant check afterwards but i dont think it was a problem with 1.2. I had by that point good 180ish mods also all of the building mods and managed to build the stuff without fake corruption.

I think i played a good 80 hours before 1.3 and it was fine. It started to happen in december with the fake corrpution stuff.

Edited by Leagacy of Morrorwind
Link to comment
Share on other sites

I have not seen this bug at all myself, with 1.3 and now 1.4.. and I am pretty much full time playing SE at the moment as a mod developer. However given the descriptions above this smacks of memory corruption occurring (as in over-writing addresses it shouldn't) very possibly during an I/O operation. One question.. do guys who are suffering this have auto-save enabled? If so.. turn it off. That would be my first suspect if I was you.

Link to comment
Share on other sites

I always turn it off first thing, after the problems it always caused in Oldrim, so no, I don't think it's that, but thank you for the suggestion.

 

The people on the Bethesda forums are being very nice (and just a little bit patronising) and telling me repeatedly that no, Bethesda can do no wrong, it's got to be a mod issue, just reinstall the game, start unmodded and add back mods one at a time, play for three hours before adding another mod to make sure it's stable, and so on and so forth. By my reckoning, with my modlist, that's six hundred hours (twenty-five full days if I did it non-stop) of repeating the first three hours of play, two hundred slogs through Bleak Falls Barrow, to establish what we are already fairly sure of, that there is a problem with the game engine since the 1.3 patch which makes it go wonky when supporting mods. I don't really have that kind of time or patience, unfortunately, especially not with something I supposedly do for fun.

 

So I guess I'll carry on as I am, saving and quitting and restarting every half hour, till either someone can suggest an actual solution or I get too hacked off with the whole thing and go back to Uru. I mean, I know that gameworld backwards and inside out, but at least it's reliable.

 

Sorry. Bit down this morning.

 

Lethiel

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...