DynDoLod is not currently installed in my current profile either. My memory block log gets to about 150 in the first block so It doesn't seem like it's anywhere near even the normal limit. Will begin digging through animation mods I have installed but they are all vanilla replacer's Edited Januby TehKaoZ This is the current load order I had at the time I am still inclined to think it is a conflict or something as a result.
I also do not remember getting this many CTD's with earlier versions of FNIS. With it I can get 1 crash every 3 loads roughly. I have the memory patch as well as enboost activated and now I have to question, what is a normal CTD range now? Without FNIS I get no crashes in 5 loads. But I can't understand why user keep a pose mod active all the time when they suffer from frequent CTDs.
Pinup Poser, for example, is a great mod.
At least temporarily reduce the number of FNIS based mods. Skyrim's problems to deal with updates of scripted mods is another big CTD cause. DefaultHeapInitialAllocMB=768ScrapHeapSizeMB=512. Make sure you have a Data/ SKSE/ skse.ini file with the following lines: This will install "sheson's memory patch", which will not totally cure Skyrim, but geatly reduce CTD likelyhood. Here my advice when you have an unacceptable CTD rate: So there is an apparent dependency between memory usage and CTD frequency. Interestingly, once Skyrim starts sucessfully, an immediate re-load of the same file will almost always succeed, even with 4000+ animations. I personally have NO load CTD with 1500 animations, about 0.5 with 3000 animations, and about 3-6 CTD with 4000 animations before the game is loaded. Skyrim's memory Management is buggy, and the more you add to Skyrim, the greater the likelyhood that you see CTDs, especially on save load. ("Load CTD") After I ran the generator, Skyrim aborts ( CTD) when loading a save file. Unfortunately when I got up FNIS I began getting crashes either on load or 5 seconds after load. While re-installing my load order via MO I began to create incremental profiles to determine the CTD issue.
0 kommentar(er)
