|
Post by Dova on Feb 8, 2014 3:58:12 GMT
What we need it appears is a step by step method where we can avoid these corrupted lists or whatever is going on. Since the wardrobe, as but one example, will permit the illegal inputs we have to do what the scripts don't. I've been following seyhebs step by step thing and it works, but only up to a point. The script execution time depends upon the capability of the computer. My tech apparently has all scripts execute instantly while my computer can take 10 seconds or even longer just to display wardrobe status or contents. Get impatient or input something while it is trying to regurgitate things and poof, another sticky ball of crud. Sniffles, I do believe being impatient is perhaps the primary cause of formlists corruption. I will have to test it thoroughly when I have the time.
|
|
|
Post by Sniffles on Feb 24, 2014 12:40:20 GMT
I just got some info from my tech. This is especially for the list bangers that are trying to unflug Skyrim.
"Regarding the list mess. I have finally managed to get the game to crash predictably and reliably. I take the character into the house in Whiterun. She then inspects the contents of everything in all the containers. She then walks out the door. The game now goes straight to BSOD. What is happening in a nutshell is all those lists, some 2000+ items in the inventories of the containers, some with corrupted lists, are loaded into memory from the disk. When you leave the house, the game attempts to make an auto save. The game attempts a data dump and it dies. However, make a save just before going out the door and no crash.
What we are dealing with is a time line. All the data loaded from disk since the previous save is crammed into memory. The game spools data when the memory gets too full but never completely unloads the data. When a save is executed, NOT an autosave, the data is flushed. When it autosaves, it attempts to load the new environment as it makes the dump. All it takes is one tiny write error while executing a load and, with enough crap in the memory, it crashes. So for those playtesters fighting with corrupt lists, there is a place to start. Getting the lists, as well as the other data of course, out of memory, whether corrupt or not, will prevent game crashes.
|
|
|
Post by Falion on Feb 24, 2014 14:02:18 GMT
Best possible advice, turn of all auto saving abilities. Game will only auto save going back and forth from Solsthiem ( and everyone should delete those ) and you should never have to worry about auto / quick save related issues. Of course, there are some that will rely on the game to do the saving for them and they will end up with problems, as Beth's games have always had issues with auto saves / quick saves.
I'm a habitual cleaner, I never keep much stuff lying around in containers. If I don't fully believe I'll be using something, it's sold, which keeps my save game files somewhat smaller as well, which does help somewhat with stability, at least it has always seemed to do so for me.
|
|
|
Post by Sniffles on Feb 25, 2014 1:52:55 GMT
Best possible advice, turn of all auto saving abilities. Game will only auto save going back and forth from Solsthiem ( and everyone should delete those ) and you should never have to worry about auto / quick save related issues. Of course, there are some that will rely on the game to do the saving for them and they will end up with problems, as Beth's games have always had issues with auto saves / quick saves. I'm a habitual cleaner, I never keep much stuff lying around in containers. If I don't fully believe I'll be using something, it's sold, which keeps my save game files somewhat smaller as well, which does help somewhat with stability, at least it has always seemed to do so for me. What he has been trying to do is to emulate the crashes and bugs I experience with his very high powered computer. I finally figured out what he meant by 'string handling' which is apparently a major problem in data base programming. "Several thousand code snippets to catch any erroneous input". Obviously Bethseda doesn't have the time or programmers to build an ironclad defense against goofy stuff like that and even welcomes errors by supporting mods. But anyway, it seems that -load and dump- at the same time is the major cause of game crashes. Eliminate autosaves, or make pre save saves seems to solve many of the issues. At least for inveterate hoarders of junk such as myself.
|
|
|
Post by Falion on Feb 25, 2014 12:18:17 GMT
|
|