mineva123123

Thanks for the link, I think I eventually narrow down the problem to not making a clean save before updating (weird that I never ran into this CTD problem before for just deleting old DynDOLOD output and replacing a new one). Thanks again for the reply!

Hello, everyone. First time posting here so please forgive me if I do something stupid. I am new to modded skyrim and I am recently learning/playing around with DynDOLOD. Very good tool, but I notice a minor bug with it: I had a save inside the player home "Tundra Homestead", and updated my DynDOLOD_output as I was fine-tunning my visual settings. After I loaded my save, I exited the player home and the game immediately triggered an event where a courier had a forced conversation with my character (for the quest "Pieces of the Past"). It seems like this forced conversation broke the in-game initialisation of DynDOLOD as trying to load any save that was saved after that forced conversation caused CTD. I fix the problem by loading an eariler save where I am not in my player home (in whiterun) and initialise DynDOLOD before the force conversation. If I then trigger the same in-game event in the overworld I think it no longer causes CTD for loading saves, therefore I think it may be a bug that causes save disruption when having a forced conversation before initialising DynDOLOD in-game. I am sorry for not able to run any diagnostic tool to see what is wrong with the corrupted saves, I am using DynDOLOD DLL SE plugin 2.45, DynDOLOD DLL SE Scripts 2.82.3, DynDOLOAD resources se Alpha-29 and DynDOLOAD 3 Alpha-104. Also I am using Alternate Conversation Camera 2.4.5-AE which may have something to do with it. I did a quick search and saw no similar report, apologies in advance if this has already been brought up.