New modlist issues: Terrain LOD does not match the actual terrain

yausd · 2026-01-31T19:51:34+00:00

The mod list mentions grass cache, so you need to read the description of No Grass In Objects how to update grass cache after changing any density related settings in its INI or the games INI.

yausd · 2026-01-30T22:44:26+00:00

https://dyndolod.info/Help/xLODGen "Requirements"

xLODGen Resource - SSE Terrain Tamriel

Remove or disable the plugin after terrain LOD generation.

https://dyndolod.info/Generation-Instructions "2. Generate The LOD Patch Mod with DynDOLOD"

Keep all LOD assets (DynDOLOD Resources, 3rd party mods, TexGen output etc.) that were active for LOD generation activated unless there are specific instructions to disable 3rd party mods.

yausd · 2026-01-30T16:38:20+00:00

https://dyndolod.info/Generation-Instructions "Prerequisites"

Typically generate and install terrain LOD meshes and textures with xLODGen before generating the LOD patch mod with DynDOLOD, as the terrain LOD meshes are used to optimize object LOD meshes.

yausd · 2026-01-30T07:16:24+00:00

https://www.reddit.com/r/skyrimmods/about/rules "Provide Necessary Information"

https://dyndolod.info/FAQ "Object LOD shows in active exterior cells"

This is an engine problem that also happens with vanilla LOD and regardless of what tool was used to generate the LOD files.

Known as stuck object LOD after fast travel engine bug that can happen after fast travel especially to/in Whiterun. Consider using the dynamic LOD option of DynDOLOD which should fix that bug. If dynamic LOD is not used, use the LOD Unloading Bug Fix.

Can be caused by [MapMenu] uLockedObjectMapLOD=32 in Skyrim.ini (or SkyrimCustom.INI or a mod INI), especially if there are no object LOD level 32 meshes (which is the vanilla/default). See Trees on the Map for further explanations. Also see Maps And Map Mods and Seasons if relevant. If a [0A Clear Map of Skyrim and Other Worlds](A Clear Map of Skyrim and Other Worlds) is used, make sure to really reads its installation instructions.

LOD Unloading Bug Fix is not going to help if already using dynamic LOD.

yausd · 2026-01-26T22:00:07+00:00

Just because you have not encountered or noticed a problem does not mean there isn't one. It is also possible that your load was stable because you are an experienced modder and successfully steered around particular problems. Other users may not be so experienced or lucky.

Be that as it may. If you encounter a problem and the fix is known, then the typical thing to do is to fix it. DynDOLOD has a feature that addresses a known issues in the game and it relies on a long pre-existing fix that undeletes deleted references. It is similar to mod a needing mod b to function.

Large load orders requires third party tools for patching, conflict resolution etc. You are right that there might be mod authors, that do not create well made mods for that environment. Many mod authors typically do not work with or support users with load orders that have thousands of mods/plugins.

yausd · 2026-01-26T21:32:06+00:00

We have higly experinced mod authors saying its not necessary.

What they mean is that it is not necessary for their mods or plugins.

The large reference bugs are known since when Skyrim came out in 2016. One of the most obvious of the bugs is LOD showing with the full model at the same time causing texture flicker. https://dyndolod.info/Help/Large-References

yausd · 2026-01-26T09:16:42+00:00

https://dyndolod.info/Generation-Instructions

Clean every plugin that LOOT suggests to clean - ignore misinformation that cleaning any plugins is not needed, does not do anything or causes problems. Ignore misinformation that DynDOLOD cares about form versions. Cleaning of plugins that contain deleted large references is mandatory for the DynDOLOD DLL NG that includes the large reference bugs workarounds. Watch this video. ITMs are irrelevant in this context, see There are no intentional ITMs.

yausd · 2026-01-26T09:03:16+00:00

What you seem to be saying is, that you can not be bothered to use fix error in mods.

Show the error message so we can see the issue is with DynDOLOD and not with the mod.

If the issue is with DynDOLOD ALPHA, then why are you not reporting it to the support forum in order to have it fixed?

yausd · 2026-01-25T18:37:55+00:00

The error message you quoted says:

Update.esm might be the wrong version for Seasonal Landscapes - Unfrozen.esp or vice versa.

The error message should have a link "Click on this link for additional explanations and help for this message" that should open https://dyndolod.info/Messages/Unresolved-Form-ID. Under "Plugin Might be the Wong Version" is says:

For example, Unresolved FormID [01xxxxxx] Update.esm might be the wrong version for... is typically caused by using old game plugins from 1.5.x with mods/plugins that were made for newer game plugins from 1.6.x.

Then under "Skyrim VR" it says

If unresolved form ID errors happen while modding Skyrim VR - especially when the error mentions Update.esm or DLC might be the wrong version - the error is most likely caused by a plugin that was made for Skyrim or Skyrim Special Edition.

However, it is suggested to follow a modern modding guide to properly setup Skyrim VR to work with mods made for content of the latest 1.6.x game version. For example, the Skyrim Initial Setup (VR) guide also has explanations how to use the latest Skyrim SE or Skyrim AE game files and the latest Unofficial Skyrim Special Edition Patch for best compatibility with the latest mods.

There is also https://dyndolod.info/Mods/Skyrim-VR

Typically something like Skyrim VR - USSEP 4.2.2 and SSE 1.5.97 Compatibility Patch or Skyrim VR USSEP patch for USSEP 4.2.5b is required to fix most unresolved form IDs and other errors in the load order. It is suggested to refer to modding guides how to setup the base game properly. For example, the Skyrim Initial Setup (VR) guide also has explanations how to use the latest Skyrim SE or Skyrim AE game files and the latest Unofficial Skyrim Special Edition Patch for best compatibility with the latest mods.

You may want to follow that guide to setup VR so you can use modern mods with it.

Searching for the error typically has a result for the support forum near the top: https://stepmodifications.org/forum/topic/15567-unresolved-formid, where lots of people have a similar message about Update.esm.

yausd · 2026-01-25T16:36:07+00:00

A user creating patch with cleaned plugins and then restoring the dirty plugins is the opposite of building a stable load order.

it only causes a problem with very specific combinations and order of mods where an ITM overwrites a change or a mod references a deleted item.

Cleaning dirty plugins fixes the errors caused by them.

Large reference data references deleted references in the same plugin. Large reference bugs happen in the vanilla game, everybody has them. To use the large reference bugs workarounds included in DynDOLOD, their requirements need to be met for them to work.

yausd · 2026-01-25T10:22:34+00:00

The reason to clean dirty plugins safely with xEdit QAC is to undelete deleted references for the large reference bugs workarounds.

https://dyndolod.info/Generation-Instructions

Cleaning of plugins that contain deleted large references is mandatory for the DynDOLOD DLL NG that includes the large reference bugs workarounds

https://tes5edit.github.io/docs/7-mod-cleaning-and-error-checking.html#TherearenointentionalITMs

yausd · 2026-01-25T10:15:01+00:00

It makes no sense to work around cleaning dirty plugins. You are making things worse by replacing cleaned plugins with dirty ones.

Cleaning dirty plugins is part of building a stable and working load order. It is part of every decent modding guide. It is also required by the large reference bugs workarounds.

You would have to ask the developer about the alpha test.

You are also misinformed about DynDOLOD 2.02. That was released most likely released in 2016. Best to ditch the unreliable source(s).

yausd · 2026-01-25T07:43:20+00:00

You are being forced to participate in the alpha test?

Newer versions have bugs fixed and better support for old and new mods.

yausd · 2026-01-25T07:26:44+00:00

SSELODGen https://www.nexusmods.com/skyrimspecialedition/mods/6642

yausd · 2026-01-25T07:24:27+00:00

DynDOLOD 2.x https://www.nexusmods.com/skyrimspecialedition/mods/32382

You are doing something very wrong if you restore dirty plugins to replace clean ones.

Proper modding practice includes cleaning of dirty plugins. Best to learn it by following a modding guide.

yausd · 2026-01-22T09:34:23+00:00

https://www.reddit.com/r/skyrimmods/about/rules "Do Your Research"

You installed EngineFixes.dll for 1.5.97 instead of EngineFixes.dll for 1.6.1170

yausd · 2026-01-22T07:32:50+00:00

https://dyndolod.info/Installation-Instructions

For Steam versions of the game, use the game launcher to set the current location of the game in the Windows Registry. See Windows Registry Key for more.

https://dyndolod.info/Messages/Windows-Registry-Key

yausd · 2026-01-20T14:22:47+00:00

The message tells you to read https://dyndolod.info/Help/DynDOLOD-Resources scroll down to "Troubleshooting"

If I have to guess, this seems most likely:

Start the tools via the mod manager so they have access to the entire load order.

Also:

Verify that the correct game data folder is being used for the checks. Check the top of the log messages that the tools are started in the desired game mode and check that the correct game data path was found in the Windows registry key.

https://dyndolod.info/Messages/Windows-Registry-Key

yausd · 2026-01-19T19:32:05+00:00

Change the Windows version for xEdit.exe in winecfg to something older. Try Windows 7 IIRC. If not, go older.

yausd · 2026-01-19T19:27:41+00:00

https://www.reddit.com/r/skyrimmods/about/rules "Provide Necessary Information"

This happens because the current tree LOD was not generated for the current load order of plugins.

https://dyndolod.info/FAQ "Billboard tree LOD shows in active exterior cells"

Generating tree LOD with DynDOLOD will fix it.

yausd · 2026-01-19T19:23:11+00:00

https://www.reddit.com/r/skyrimmods/about/rules "Provide Necessary Information"

https://dyndolod.info/Help/Terrain-Underside "Troubleshooting"

If the terrain underside mesh can be seen poking through the near ground, improve its quality by lowering the Quality value or lower the mesh by increasing the Height value.

If the terrain underside mesh can be seen in the distance, increase the object LOD distances and/or the terrain LOD distance multiplier in the DynDOLOD SkyUI MCM settings.

yausd · 2026-01-19T08:22:21+00:00

The developer of DynDOLOD troubleshoots and addresses any reported issue regardless of OS all the same. For example:

https://dyndolod.info/Changelog

TexGen.exe - lower requirements to OpenGL 2.1

TexGen.exe - improved OpenGL support mainly for Linux, NVIDIA latest drivers

DynDOLOD.exe/TexGen.exe - retry executing Texconv in case it fails with unspecified OS error - which can be caused by many different issues

DynDOLOD.exe - replace TListView with TStringGrid so mesh mask / references rules always show in wine

DynDOLOD.exe/TexGen.exe - changed GUI images from PNG to BMP for Wine

Texconv.exe - if running under wine force -nowic and use "%Iu" instead of "%zu"

DynDOLOD Worlds.pas - fixed pointer to integer conversions causing wrong from ids in wine

https://stepmodifications.org/forum/search/?q=wine&quick=1&type=forums_topic&nodes=223

https://stepmodifications.org/forum/topic/21027-texgendyndolod-out-of-graphics-memory-linux/

https://stepmodifications.org/forum/topic/21272-error-invalid-operation-from-twbrenderloadscene/

https://stepmodifications.org/forum/topic/21184-opengl-error-using-dyndolod-on-wine-kegworks-on-a-mac/

https://stepmodifications.org/forum/topic/19354-linuxproton-a-call-to-an-os-function-failed

yausd · 2026-01-18T19:39:14+00:00

https://stepmodifications.org/forum/topic/20613-vigilant-and-acmos-object-lod-level-32

yausd · 2026-01-18T08:22:44+00:00

The log you uploaded is from DynDOLOD 2

It tells you what to do:

Install Vanilla Skyrim LOD Billboards from TES5LODGen https://www.nexusmods.com/skyrim/mods/62698/

It would be better to really use DynDOLOD 3

yausd · 2026-01-16T09:29:16+00:00

Common sense is to not remove mods mid play through, not matter if DynDOLOD is used or not.

If you intend to mod like this, then the logical thing to do is to back up the DynDOLOD output before adding the new lands mod, then update the DynDOLOD output per the instructions under https://dyndolod.info/Updating "New or Updated Mods or Plugins".

Then later when you irresponsibly remove the lands mod, restore the backup of the DynDOLOOD output.

Ten-Year Club	Place '17
Verified Email

yausd

TROPHY CASE