Possible to combine separate Dyndolod runs?

[cardician]

So I've got a mod list that has 20 world spaces. Unfortunately, if I attempt to process all 20 with my computer, about 3/4ths of the way through my computer just reboots or blue screens. So some issue with my computer. I've spent too long trying to address it and since I honestly have no issues with anything else I'm giving up. The odd thing is though that I can successfully process say 5 or 6 of the worlds at a time and Dyndolod completes successfully. So I could actually just break apart my Dyndolod processing into like 4 runs, each run processing a separate set of worlds. So my question is simple, is this possible? Is there a way to run Dyndolod so that it can name the Dyndolod.esp with a different name? Can I just rename the later Dyndolod.esps by adding a 2 or 3? Or is there some easy way for me to combine the esps? Or am I just out of luck and definitely going down the wrong path?

 

Any help is appreciated, thank you.

[sheson]

On 9/7/2025 at 7:09 PM, cardician said:

So I've got a mod list that has 20 world spaces. Unfortunately, if I attempt to process all 20 with my computer, about 3/4ths of the way through my computer just reboots or blue screens. So some issue with my computer. I've spent too long trying to address it and since I honestly have no issues with anything else I'm giving up. The odd thing is though that I can successfully process say 5 or 6 of the worlds at a time and Dyndolod completes successfully. So I could actually just break apart my Dyndolod processing into like 4 runs, each run processing a separate set of worlds. So my question is simple, is this possible? Is there a way to run Dyndolod so that it can name the Dyndolod.esp with a different name? Can I just rename the later Dyndolod.esps by adding a 2 or 3? Or is there some easy way for me to combine the esps? Or am I just out of luck and definitely going down the wrong path?

Any help is appreciated, thank you.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post Logs which DynDOLOD log and debug log to upload when making posts. It also explains how to enable the realtime log in case the logs can not be saved and upload that instead.

https://dyndolod.info/FAQ#BSOD-Blue-Screen-Of-Death
BSOD, the PC crashing or turning off is a hardware, BIOS setting, OS or driver problem.
For example, problems with overclocking, memory timings, cooling, unstable power supply etc.
Searching the Internet for the BSOD code should help troubleshooting. Check the Windows event log for hints.

Test system stability with things like prime95 and OCCT. You should really fix the actual issue with the hardware, BIOS settings or the OS. Not addressing and fixing the cause of BSOD is going down the wrong path.

See https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory and https://dyndolod.info/FAQ#Long-running-time-or-output-several-GB-in-file-size and reduce resource/memory usage while generating the LOD patch. This might help avoiding BSOD caused by unstable hardware etc.

In case reducing memory requirements as explained in the FAQs above does not help, see https://dyndolod.info/Updating#New-or-Updated-Mods-or-Plugins:
In case a new mod contains a plugin that adds new objects to a worldspace or adds a new worldspace, start DynDOLOD with the existing DynDOLOD output in the load order. The existing DynDOLOD plugins need to load after any other plugins of the same type (e.g. DynDOLOD.esm after the highest priority ESM, DynDOLOD.esp with the highest priority possible). In case Occlusion.esp exists, it needs to load after DynDOLOD.esp. Select the worldspaces affected by the plugin and generate LOD as usual. Then install the DynDOLOD output, overwriting the existing DynDOLOD output. This might not carry forward all changes made to existing worldspace or cell records made by new plugins. In that case resolve conflicts by manually forwarding conflicting records or consider generating from scratch.

To combine different worldspaces in separate sessions, update existing and installed DynDOLOD output as explained above by generating different worldspaces per update run, e.g. generate one worldspace, save & exit, install, start next session with installed output, save & exit, merge install, repeat.