Where Does DynDOLOD Store Output?
DynDOLOD output mods, logs and overwrite folders for Bethesda games.
Last updated
DynDOLOD writes generated LODs as fake mods into output folders beside its executable, meant for the mod manager overwrite or a dedicated output mod. Logs beside them diagnose every failed generation.
Never generate into the game Data folder directly. Output mods keep generations removable and reorderable.
Where DynDOLOD stores this, by platform
<DynDOLOD folder>\DynDOLOD_Output
Generated meshes, textures and plugins per run; sibling TexGen_Output holds its own pass. Point both at empty folders before each run. Logs in the Logs subfolder name the plugins that failed. Install outputs as regular mods afterward.
Frequently asked questions
DynDOLOD or TexGen output first?
TexGen textures first, then DynDOLOD meshes referencing them. Both output folders above stay separate by design.
Why is DynDOLOD output enormous?
High-detail LOD packs run tens of gigabytes. Point outputs at a roomy drive before starting.
Notice an outdated path? Let us know.