maydragon75

Hopefully the old design will be an optional theme going forward. I find the new design takes away from trying to view/interact with a mod page. A good design should not demand attention, but instead focuses attention on the content in the web page, and is intuitive to navigate. IMO the new design fails in those regards. It's overly complicated, and takes attention away from the content of the mod page.

I am SOOOO grateful for this thread!! I have been having this issue for a couple of months and just found this thread yesterday. Having read through most of it, it seems to confirm what I thought the issue was, which is a memory overload of some sort (caused by a combination of many mods, large numbers of loose files and scripts triggering etc), not really related to any one mod. Like others have reported here I was experiencing this about every twenty minutes, first dialogue would start to disappear then the save would appear corrupted, but exiting and re-entering the game and the save no longer showed as corrupted and could be loaded fine. I could make it happen almost instantly by crafting. I was using SKUI 2.2 and the achievement unlocker, along with most of the other suspects that have been discussed in this thread. Following advice given here I have now uninstalled SKYUI2.2 and the achievement unlocker (but am still using the uncapper which runs off the same DLL loader) and so far no more corrupted saves (four hours of play and several long crafting sessions). So at the very least this seems to have reduced the likelihood (and/or frequency) of occurrence for me. I don't think either mod is to blame and both are fantastic mods. I think it is more that with these mods installed, and the rest of my very script heavy load order Skyrim without SKSE just can't handle it. I think that this issue is not widely reported yet because most of those who heavily modded their games are still playing legendary edition, and will continue to do so until SKSE64 comes out. Well that's my two cents worth. I will report back here if the issue reemerges in my game. Thank you again to those who created this thread and those who worked really hard to try and understand what the problem is, and how to fix it.