DynDOLOD 3.00 Alpha 196

[Gamma_Metroid]

1 hour ago, sheson said:

Right now DynDOLOD would not know how to update that, so currently the best method would be to move the references, base records and form lists into a separate plugin that can be disabled/removed.

Once you made such a plugin and send it to me, I can use it to test updating the DynDOLOD patcher so it reuses the records and overwrites things if required. Once that works, it should also work if the records exist in other plugins, like the main plugin.

The underside mesh should not show in child worldspaces that share the SkyCell but do not use the parent world space for LOD so that it does not become visible because the matching terrain LOD to cover it up is not loaded. MarkarthWorld for example. The script accomplishes that. That script can be included in BSAs that are loaded via INI or ESMs.

This is the plugin I am using. I just took the form list, base record, and reference from the DynDOLOD generated plugin.

underside.esp

[aazz]

DynDOLOD

Access violation at address 0000000001855732 in module 'DynDOLODx64.exe' (offset F65732).

Read of address 0000000000000000 while processing Update.esm [REFR:010012AD] (Places TreeFloraMountainFlower02Purple "e"¤ê½f" [TREE:000B91F8] in WhiterunWind District02 [CELL:0001A27B] (in WhiterunWorld "i™"I'IŠ ëΫ" [WRLD:0001A26F] at 5,-1))

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.
 

 

Hello. I keep getting this error. What could be the problem?

https://mega.nz/file/7EQFkYhT#x4ScbwEA5YwSt4gsqATyI8r8i9OMf3yUtlsOwkBgO2c

I've attached the log here. Thank you as always.

[sheson]

On 10/2/2025 at 8:30 AM, Gamma_Metroid said:

This is the plugin I am using. I just took the form list, base record, and reference from the DynDOLOD generated plugin.

underside.esp 1.11 kB · 1 download

Get the latest test version of DynDOLOD from https://dyndolod.info/Downloads/Test-Versions

Generate underside as usual for the first time and add the base records, form lists and references to your master plugin. This necessary because the EditorIDs of those records changed going forward to include the term _DynDOLOD_ to properly identify these records.

Then it should be possible to generate a LOD patch with DynDOLOD as usual. If the Underside option is checked, the records will be overwritten only if there are any changes to them. There should be no new duplicate records created. The mesh will always be generated.

[sheson]

11 hours ago, aazz said:

DynDOLOD

Access violation at address 0000000001855732 in module 'DynDOLODx64.exe' (offset F65732).

Read of address 0000000000000000 while processing Update.esm [REFR:010012AD] (Places TreeFloraMountainFlower02Purple "e"¤ê½f" [TREE:000B91F8] in WhiterunWind District02 [CELL:0001A27B] (in WhiterunWorld "i™"I'IŠ ëΫ" [WRLD:0001A26F] at 5,-1))

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.
 

 

Hello. I keep getting this error. What could be the problem?

https://mega.nz/file/7EQFkYhT#x4ScbwEA5YwSt4gsqATyI8r8i9OMf3yUtlsOwkBgO2c

I've attached the log here. Thank you as always.

Check if the test version of DynDOLOD from https://dyndolod.info/Downloads/Test-Versions runs through.

Upload new logs if issue persists.

[aazz]

Thank you for your continued support.

https://mega.nz/file/eRZAzRoR#GhNwKFl8udBKR_OPu6mu-ed_uQI9OfR4FBdzWEWjo00

 

LODGenx64Win.exe failed to generate object LOD for one or more worlds.

Check for error messages in the listed LODGen log(s)

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

 

When I remove the "-memory" argument, I get this error

As far as I remember, if there is no error indicated in the LODGen log, I think it is a memory issue. So I think I added "-memory".

I scanned my PC with prime95 and OCCT, but nothing abnormal was found.

What else should I look into??

[sheson]

15 minutes ago, aazz said:

Thank you for your continued support.

https://mega.nz/file/eRZAzRoR#GhNwKFl8udBKR_OPu6mu-ed_uQI9OfR4FBdzWEWjo00

 

LODGenx64Win.exe failed to generate object LOD for one or more worlds.

Check for error messages in the listed LODGen log(s)

Click on this link for additional explanations and help for this message

For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.

 

When I remove the "-memory" argument, I get this error

As far as I remember, if there is no error indicated in the LODGen log, I think it is a memory issue. So I think I added "-memory".

I scanned my PC with prime95 and OCCT, but nothing abnormal was found.

What else should I look into??

The DynDOLOD log reports deleted references. The reported plugins need to be cleaned. Read https://dyndolod.info/Messages/Deleted-Reference.

The DynDOLOD log reports references attached to wrong cells. The plugins need to be fixed with an xEdit scripts. Read https://dyndolod.info/Messages/Reference-Attached-to-Wrong-Cell.

As explained in https://dyndolod.info/Help/LODGen C0000005 can be a sign of hardware issues or high memory usage.

High main memory usage and the memory usage of individual (sub) process can be checked with the Windows task manager for example.

The -memory argument for TexGen/DynDOLOD only makes sense if the OS runs out of main memory because TexGenx64.exe or DynDOLODx64.exe use a lot.

https://dyndolod.info/Help/LODGen#Out-of-Memory, especially:
Let Windows handle virtual memory automatically.

It seems you exited or stopped DynDOLOD manually.

I suggest to do this:
Do not check Occlusion, since it will fail if there are xLODGen errors. However, the DynDOLOD patch plugins, SKSE data and textures are typically generated fine if only xLODGen fails and Occlusion was not selected. Keep an eye on memory usage with Window task manager. If you notice lots of xLODGen process running at the same time, consider change the MaxLODGen as explained in https://dyndolod.info/Help/LODGen#Out-of-Memory.

If there are still xLODGen errors next run, do this to try to generate each failed worldspace one by one or in small batches - from https://dyndolod.info/Help/LODGen:
To restart LODGen generation for a worldspace in case there is no LODGen_[GAME MODE]_[WORLDSPACE]_log.txt or it does not contain a useful error message, start DynDOLOD in expert mode, select the desired worldspace and click Execute LODGen. Bring the LODGen command prompt window to the front to see if it prints more details to the console. If that does not give more detail, check the Windows Event Viewer for additional messages from the .Net Framework or the .NET Desktop Runtime.

If xLODGen fails then, rename ..\DynDOLOD\Edit Scripts\LODGenx64Win.exe to LODGenx64Win.bak, so it will use LODGenx64.exe next start up, then try above steps again.

If you can generate object LOD meshes for all failed worldspaces like this you will end up and have successfully generated the DynDOLOD plugins, SKSE and textures, you should have a complete LOD patch output that you can install and for which you can generate Occlusion separately by only checking the Occlusion checkbox in advance mode. https://dyndolod.info/Help/Occlusion-Data#Generation

[mostwanted11]

Where are these numbers saved? the direct/ambient ones at least

[aazz]

8 hours ago, sheson said:

The DynDOLOD log reports deleted references. The reported plugins need to be cleaned. Read https://dyndolod.info/Messages/Deleted-Reference.

The DynDOLOD log reports references attached to wrong cells. The plugins need to be fixed with an xEdit scripts. Read https://dyndolod.info/Messages/Reference-Attached-to-Wrong-Cell.

As explained in https://dyndolod.info/Help/LODGen C0000005 can be a sign of hardware issues or high memory usage.

High main memory usage and the memory usage of individual (sub) process can be checked with the Windows task manager for example.

The -memory argument for TexGen/DynDOLOD only makes sense if the OS runs out of main memory because TexGenx64.exe or DynDOLODx64.exe use a lot.

https://dyndolod.info/Help/LODGen#Out-of-Memory, especially:
Let Windows handle virtual memory automatically.

It seems you exited or stopped DynDOLOD manually.

I suggest to do this:
Do not check Occlusion, since it will fail if there are xLODGen errors. However, the DynDOLOD patch plugins, SKSE data and textures are typically generated fine if only xLODGen fails and Occlusion was not selected. Keep an eye on memory usage with Window task manager. If you notice lots of xLODGen process running at the same time, consider change the MaxLODGen as explained in https://dyndolod.info/Help/LODGen#Out-of-Memory.

If there are still xLODGen errors next run, do this to try to generate each failed worldspace one by one or in small batches - from https://dyndolod.info/Help/LODGen:
To restart LODGen generation for a worldspace in case there is no LODGen_[GAME MODE]_[WORLDSPACE]_log.txt or it does not contain a useful error message, start DynDOLOD in expert mode, select the desired worldspace and click Execute LODGen. Bring the LODGen command prompt window to the front to see if it prints more details to the console. If that does not give more detail, check the Windows Event Viewer for additional messages from the .Net Framework or the .NET Desktop Runtime.

If xLODGen fails then, rename ..\DynDOLOD\Edit Scripts\LODGenx64Win.exe to LODGenx64Win.bak, so it will use LODGenx64.exe next start up, then try above steps again.

If you can generate object LOD meshes for all failed worldspaces like this you will end up and have successfully generated the DynDOLOD plugins, SKSE and textures, you should have a complete LOD patch output that you can install and for which you can generate Occlusion separately by only checking the Occlusion checkbox in advance mode. https://dyndolod.info/Help/Occlusion-Data#Generation

I set everything you said and tried again about 5 times and it worked!

Now I just need to adjust the grass lighting a bit. Thank you so much for your help. Today is a holiday in our country. Have a nice day. Thank you.

[sheson]

On 10/6/2025 at 1:23 AM, mostwanted11 said:

Where are these numbers saved? the direct/ambient ones at least

https://dyndolod.info#Quickstart
Click the Help buttons in the GUI or browse Help to open contextual help and explanations for a tool or topic.

https://dyndolod.info/Official-DynDOLOD-Support-Forum
Do not post screenshots of the tools, unless it is about visual issues with the user interface.

Is there something I am supposed to look at in the screenshot other than verifying that the "Help" button is present? Clicking it should open https://dyndolod.info/Help/TexGen, which explains:
Once the Start button is clicked, the current settings are saved as a preset to ..\DynDOLOD\Edit Scripts\DynDOLOD\Presets\DynDOLOD_[GAME MODE]_TexGen_Default.ini for the next time TexGen is started.

[Gamma_Metroid]

On 10/4/2025 at 6:03 AM, sheson said:

Get the latest test version of DynDOLOD from https://dyndolod.info/Downloads/Test-Versions

Generate underside as usual for the first time and add the base records, form lists and references to your master plugin. This necessary because the EditorIDs of those records changed going forward to include the term _DynDOLOD_ to properly identify these records.

Then it should be possible to generate a LOD patch with DynDOLOD as usual. If the Underside option is checked, the records will be overwritten only if there are any changes to them. There should be no new duplicate records created. The mesh will always be generated.

This works great, thank you!

[sheson]

On 10/8/2025 at 10:03 AM, Gamma_Metroid said:

This works great, thank you!

Thanks for letting us know. The updates will be part of the next alpha version as usual.

[Glanzer]

I noticed that the giant campfires no longer burn my character when using Fire Hurts NG. I traced the problem to the fact that the base object ID of the campfire was changed and replaced by an object that is now in the DynDOLOD.esm plugin (see attached screenshot).

I then found the following rule in the DynDOLOD_SSE_embersxdesp.ini (yes I do use EmbersXD):

[Skyrim LODGen]
LODGen1=giantcampfire01,,,,Far Full,Replace,0

If I'm reading that correctly, it looks like the LOD is being used for the closeup model. I'm getting that from here where it says "Replace" means that when the cell is attached (when the character enters the cell?) the original reference is disabled and the LOD continues to be used. Am I reading that correctly? If so, why was that done? It breaks the giant campfires for the Fire Hurts mod.

[sheson]

13 hours ago, Glanzer said:

I noticed that the giant campfires no longer burn my character when using Fire Hurts NG. I traced the problem to the fact that the base object ID of the campfire was changed and replaced by an object that is now in the DynDOLOD.esm plugin (see attached screenshot).

I then found the following rule in the DynDOLOD_SSE_embersxdesp.ini (yes I do use EmbersXD):

[Skyrim LODGen]
LODGen1=giantcampfire01,,,,Far Full,Replace,0

If I'm reading that correctly, it looks like the LOD is being used for the closeup model. I'm getting that from here where it says "Replace" means that when the cell is attached (when the character enters the cell?) the original reference is disabled and the LOD continues to be used. Am I reading that correctly? If so, why was that done? It breaks the giant campfires for the Fire Hurts mod.

What the rules does is use the full model (in this case from EmbersXD) for LOD instead of the usual dynamic LOD model included in DynDOLOD Resources, since that is for the vanilla model and doesn't match well. Typically there is no need to switch from the full model to the same full model used for LOD, so that is why the rule uses "Replace", to use the "LOD" reference continuously.

For now, change the rule from "Replace" to "Unchanged", so the original reference is used in the active cells and the LOD reference in the LOD area.

See https://dyndolod.info/Help/Mesh-Mask-Reference-Rules.

I will see if I can add support for FireHurts to automatically create a proper JSON file for it if a new base record added is added in the DynDOLOD plugins. Check the changelog of the next couple alpha release for support. Then you can use the EmbersXD rule with "Replace" again.

[Glanzer]

2 hours ago, sheson said:

For now, change the rule from "Replace" to "Unchanged", so the original reference is used in the active cells and the LOD reference in the LOD area...

I will see if I can add support for FireHurts to automatically create a proper JSON file for it if a new base record added is added in the DynDOLOD plugins.

Thank you! For now I just created a new JSON file with the updated formids and that worked. If you do create a dynamic JSON file be sure to give each of the 3 bounds in it a value of at least 300 due to the size of the firelog mesh. I'm using 400 but I like to get burnt early since it's such a big fire.

[Goldhawk]

Hi, I'm having an issue with DynDOLOD together with some mods affecting Solitude in Skyrim SE. Specifically, I'm using Grand Solitude, Legacy of the Dragonborn, Blue Palace Terrace, and the official patches for them. All versions are the latest as of the time of posting. With DynDOLOD disabled, everything looks fine in the areas touched by these mods. But after running DynDOLOD with these mods installed and installing the output, the area around the back of the museum, facing the terrace, is missing most of its geometry, with a parts of the museum just floating in the air. Selecting the floating pieces of the museum with the console confirms they were modified by DynDOLOD.esm.

Here's how the area looks with everything except DynDOLOD output installed:

https://ibb.co/xtFwLxp1 

https://ibb.co/BVjZ7yRS

And here's how it looks with DynDOLOD active:

https://ibb.co/0Vtp2G1q

I looked in xEdit and I can see DynDOLOD.esm overriding many of the entries from LotD and Blue Palace Terrace:

https://ibb.co/b59y69Gx

Any idea what's going on here? From my (limited) understanding of how DynDOLOD works, I think this is related to large references and Parent > Child worldspace copies, but I'm not really sure.

Logs from the most recent run (let me know if you need to see any others):

DynDOLOG_SSE_log

ChildworldMatches

ChildworldCopies_Tamriel

ModelsUsed_Tamriel

Bug Report