Greetings! Looking for support with DynDOLOD Alpha 187.
I have a 951 mod, quite stable Skyrim SSE/AE 1.6.1170 setup that I decided to try with DynDOLOD for the first time this week. I have tried using Alpha 185, 186, and 187 (I started trying to use DynDOLOD when 185 was current, then I tried 186, and then 187 as each was released...issue is generally the same with all three). With each new release, I recreated my Texgen and DynDOLOD output with the latest version and removed the old .zip / installed new .zip to Skyrim and then started a new character for testing.
With DynDOLOD mod enabled and active in-game, I experience the following CTD and ILS issues:
The automatic loading of the last save game after dying will almost always CTD. It was 100% of the time with 185, is slightly better with 186 and 187. Interestingly, it is better with Papyrus bEnableTrace=1 and DynDOLOD_NG_Worlds debug=true. I wonder if the problem is a timing issue and logging/debug is slowing some process down slightly. I do have an extremely fast computer (Intel i9-14900K, GeForce RTX 4090, 96 GB RAM).
With a new character leaving Whiterun (starting in Whiterun using Alternate Start - Live Another Life), the first time I try to leave the city with the new character, I will almost always get an ILS (not 100%, but close to it). I started saving before leaving the city, and after restarting the game and reloading that save, I will no longer get an ILS leaving the city with that character. Very odd.
I have tried the troubleshooting steps listed on this site and in the readme for DynDOLOD (in DynDOLOD\docs folder).
Some troubleshooting results:
If I uncheck "DynDOLOD is active" in the MCM and then make a save game and then die, that save game will auto load successfully after I die 100% of the time.
I tried removing all of the *.bto files from the Meshes\Terrain\Tamriel\Objects folder. All save games will then load successfully after I die 100% of the time, even with DynDOLOD active in the MCM. If I add any of the *.bto files back to the Tamriel world Object folder, same issue with save games almost always causing CTD after the auto load after death.
I can load any save game successfully, with DynDOLOD active, if I manually choose to load a save game when I'm not dead. It is the autoload after death that causes CTD.
Skyrim seems less stable with DynDOLOD active (non-scientific observation). I have had more CTD with DynDOLOD active than before I installed it. I've been testing this mod list and load order extensively the last few weeks to prepare for a new run through Skyrim, and while I would have some crashes, the CTD since installing DynDOLOD are more frequent, and seem to go back to pre-DynDOLOD when I uncheck "DynDOLOD is active" in the MCM. I use Crash Logger SSE. It has not helped me to identify any consistent reason for the instability. The items in the stack are never the same from one crash to the next but are always "EXCEPTION_ACCESS_VIOLATION" unhandled exceptions at non-repeating addresses.
I have attached the requested logs. I am happy to provide any additional data points. If I have missed something, am doing something wrong, etc., please let me know and I will upload additional logs, try recommended configuration changes, etc.
DynDOLOD_SSE_log.txt: https://ufile.io/572l0cnk
DynDOLOD_SSE_Debug_log.txt: https://ufile.io/ak4hpco6
Papyrus.0.log: https://ufile.io/0tgz2jvj
Crash Logger log: https://ufile.io/4a8lesx1
My sincere thanks for any help. The visuals from DynDOLOD in my game are breathtakingly awesome...I so want to keep using them and am hoping I can figure out what is causing this instability.
CarlWG2