Clean save when updating DynDOLOD

[PegasusKoga]

I'm probably paying the price for adding new mods to my load order recently after finalizing it and running Dyndolod six months ago.

Because i've been getting random crashes around the settlement of Raven Rock and the wilderness for the first time since i started my hundred hour playthrough.  I have included the most recent crash log.

I was thinking of regenerating lod but it's not that simple because the Dyndolod exe i used (3.0.0.169) has expired and i need to replace it with the most recent version.  Keeping that in mind, do i need to apply the clean save method as described in it's MCM menu before running the tool since the Dyndolod scripts might have changed?  Or is it enough to simply re-run Dyndolod and TextGen.  I could not find an answer in the faq for my specific situation.

crash-2025-01-06-19-49-02-REPORT.txt

[sheson]

6 hours ago, PegasusKoga said:

I'm probably paying the price for adding new mods to my load order recently after finalizing it and running Dyndolod six months ago.

Because i've been getting random crashes around the settlement of Raven Rock and the wilderness for the first time since i started my hundred hour playthrough.  I have included the most recent crash log.

I was thinking of regenerating lod but it's not that simple because the Dyndolod exe i used (3.0.0.169) has expired and i need to replace it with the most recent version.  Keeping that in mind, do i need to apply the clean save method as described in it's MCM menu before running the tool since the Dyndolod scripts might have changed?  Or is it enough to simply re-run Dyndolod and TextGen.  I could not find an answer in the faq for my specific situation.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Do not use CLA or posts logs from it.

https://dyndolod.info/FAQ#ILS-or-CTD
The DynDOLOD and Occlusion plugins might show up in crash logs a lot, since they are typically the plugins last to overwrite worldspace and cell records, so careful reading and interpretation of the stacks and registers etc. might be required to identify the actual cause of the problem.
It is very unlikely for Occlusion.esp to cause crashes by itself. It is created by copying worldspace and cell records from the winning plugins before it, then update the TVDT Occlusion data which itself can not really cause crashes.
Ignore nonsensical suggestions that autosaves need to be disabled because of papyrus scripts not completing or similar made up stories about plugins being "known to cause CTD" when fast traveling or changing locations because of scripting etc. This is not how anything works. If disabling autosaves would be required to prevent CTD, manual saves would have the same issue and it would actually be widely known, would have been reported, troubleshooted, analyzed, fixed, had known workarounds and/or be part of every modding guide since over a decade.

The MCM already explains what to do before updating. Also https://dyndolod.info/Updating explains:
1. Before Updating
Make a clean save.

There is no ambiguity. A clean save is always required when generating a new LOD patch from scratch.