I've recently encountered the "CTD on Save bug". I've determined that it isn't being caused by string count or memory block excesses, but I can't determine what is causing it. My install is SRLE plus hunterborn, moonpath and a bunch of follower mods. It works fine off a new install (not a single crash for about 20 hours) until I get this bug. There isn't a lot of information on the web or step about what causes it but that using the player.kill fix (https://forums.steamp...d.php?t=2994022) does work. My questions are two fold....what could be causing it? (or at least what should I be looking for since I've ruled out more obvious things) and why does the player.kill method work? (What is it doing to the game to allow one to continue playing as if the problem never existed?)
Question
maedrhos
I've recently encountered the "CTD on Save bug". I've determined that it isn't being caused by string count or memory block excesses, but I can't determine what is causing it. My install is SRLE plus hunterborn, moonpath and a bunch of follower mods. It works fine off a new install (not a single crash for about 20 hours) until I get this bug. There isn't a lot of information on the web or step about what causes it but that using the player.kill fix (https://forums.steamp...d.php?t=2994022) does work. My questions are two fold....what could be causing it? (or at least what should I be looking for since I've ruled out more obvious things) and why does the player.kill method work? (What is it doing to the game to allow one to continue playing as if the problem never existed?)
Link to comment
Share on other sites
2 answers to this question
Recommended Posts