DynDOLOD not detecting resources

[CultureBomb]

When I run DynDOLOD following all the instructions in the Skyrim SE STEP guide 1.0.0 I receive the error in the attached image before it finishes initializing.

[Greg]

Did you install the DynDOLOD Resources SE mod and is it active in the left pane?

[z929669]

4 hours ago, CultureBomb said:

When I run DynDOLOD following all the instructions in the Skyrim SE STEP guide 1.0.0 I receive the error in the attached image before it finishes initializing.

You need to enable the DynDOLOD resources as described in the guide. In fact, you need to enable all mods that you install. Please revisit the mod instructions for DynDOLOD under 03-Resources.

[CultureBomb]

I'm receiving the error in spite of the fact that DynDOLOD Resources SE is installed and enabled. Could this have to do with the fact that it is overwritten by other mods? It's overwritten by Skyrim Realistic Overhaul, Majestic Mountains, Enhanced Vanilla Trees SE, and my TexGen Output.

[z929669]

3 minutes ago, CultureBomb said:

I'm receiving the error in spite of the fact that DynDOLOD Resources SE is installed and enabled. Could this have to do with the fact that it is overwritten by other mods? It's overwritten by Skyrim Realistic Overhaul, Majestic Mountains, Enhanced Vanilla Trees SE, and my TexGen Output.

Overwriting should not be an issue, especially if you installed the Resources where indicated by the guide. Revisit that to be sure it is in the correct priority in MO. Otherwise, this can happen if you have DynDOLOD 3 alpha versus 2.xx (as used in the SE 1.0.0 guide) with the wrong resources downloaded and installed. It can also happen if you did not set up DynDOLOD with the correct game switch as instructed in the Tools section of the System Setup Guide. Alternatively, the file name itself can be changed to the game type, but that's not how we instruct to do it in the guide.

[CultureBomb]

Thanks for the help. turns out the issue is that DynDOLOD was outdated. Installing the latest 2.xx version of DynDOLOD solved the issue. I was running version 2.61 when the latest was 2.96.