DynDOLOD 3.00 Alpha 182

[NoCleverness]

3 hours ago, sheson said:

However, the message most likely means there are old DynDOLOD plugins are active in the load order that were generated without DynDOLOD DLL NG and Scripts being active. This message can not really show when starting a new game with the plugins from the generation shown in the log. Make sure there are no old DynDOLOD plugins in the load order, also not renamed ones and that the output from the log is overwriting everything.

I deleted my entire Data folder and started from scratch. There is no possible way that there was an old, pre-NG plugin active. I probably will start a new game and test Riverwood, just to be sure.

[sheson]

7 hours ago, NoCleverness said:

I deleted my entire Data folder and started from scratch. There is no possible way that there was an old, pre-NG plugin active. I probably will start a new game and test Riverwood, just to be sure.

Requested logs were not uploaded. It is still unclear if a new game was started or a save was loaded.

The plugins generated with DynDOLOD DLL NG and Scripts active do not use any papyrus scripts that print messages like "DynDOLOD can not find * in DynDOLOD_Worlds" and "DynDOLOD can not find master data in". Only plugins that were generated without DynDOLOD DLL NG and Scripts in the load order use a papyrus script that prints those messages. If there was no old plugin in the data folder, then maybe another tool made copies of records from an old DynDOLOD plugin. Do not create patches after generating LOD, make them beforehand as explained in the generation instructions.

Since you gave up troubleshooting and deleted the data folder, I suggest to follow a modding guide that explains how to properly setup the game and how to use a mod manager like MO2.

[NoCleverness]

7 hours ago, sheson said:

Requested logs were not uploaded. It is still unclear if a new game was started or a save was loaded.

The plugins generated with DynDOLOD DLL NG and Scripts active do not use any papyrus scripts that print messages like "DynDOLOD can not find * in DynDOLOD_Worlds" and "DynDOLOD can not find master data in". Only plugins that were generated without DynDOLOD DLL NG and Scripts in the load order use a papyrus script that prints those messages. If there was no old plugin in the data folder, then maybe another tool made copies of records from an old DynDOLOD plugin. Do not create patches after generating LOD, make them beforehand as explained in the generation instructions.

Since you gave up troubleshooting and deleted the data folder, I suggest to follow a modding guide that explains how to properly setup the game and how to use a mod manager like MO2.

I did upload the logs. They're in a ufile link above. If you mean the papyrus log, here are a few.

Papyrus.0.log Papyrus.1.log

Edited 22 hours ago by NoCleverness

[sheson]

45 minutes ago, NoCleverness said:

I did upload the logs. They're in a ufile link above. Please read them. If you mean the papyrus log, here are a few.

Papyrus.0.log 2.13 kB · 1 download Papyrus.1.log 247.78 kB · 0 downloads

The also requsted DynDOLOD.log from DynDOLOD.DLL was not provided.
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to uplaod the DynDOLOD.log from the DynDOLOD.DLL.
If a DynDOLOD.DLL is being used or installed, also upload the entire DynDOLOD.log:
c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log.

The linked logs only contain a DynDOLOD_SSE_Debug_log.txt  and DynDOLOD_SSE_log_truncated.txt. So I also requsted the papyrus log and DynDOLOD.log from DynDOLOD.DLL afterwards. That request was ignored. I checked the uploaded logs from the DynDOLOD generation as I wrote: The uploaded DynDOLOD logs show that DynDOLOD output was generated with DynDOLOD DLL NG and Scripts installed.

Still not clear if an existing save game or new game was started when those message shows.
The Papyrus.0.log does not show much seems like main menu only, no message related to DynDOLOD.
The Papyrus.1.log looks like what happens when a save that is not cleaned is being loaded.

Load whatever save that needs cleaning without any DynDOLOD output, Resources, DLLs etc. files whatsoever active in the load oder. Go into an interior if not in one. Save the game. Make a backup. Use the Clean option Remove unattached instances and Remove undefined elements for Scripts and Script Instances starting with #SHESON_DynDOLOD_* with Resaver from FallrimTools - Script cleaner and more on that save. Then load that save and save again. Then enable DynDOLOD Resources, DynDOLOD DLL NG and Scripts and the DynODLOD output make for it. Load the last save.

[NoCleverness]

46 minutes ago, sheson said:

The also requsted DynDOLOD.log from DynDOLOD.DLL was not provided.
Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to uplaod the DynDOLOD.log from the DynDOLOD.DLL.
If a DynDOLOD.DLL is being used or installed, also upload the entire DynDOLOD.log:
c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log.

The linked logs only contain a DynDOLOD_SSE_Debug_log.txt  and DynDOLOD_SSE_log_truncated.txt. So I also requsted the papyrus log and DynDOLOD.log from DynDOLOD.DLL afterwards. That request was ignored. I checked the uploaded logs from the DynDOLOD generation as I wrote: The uploaded DynDOLOD logs show that DynDOLOD output was generated with DynDOLOD DLL NG and Scripts installed.

Still not clear if an existing save game or new game was started when those message shows.
The Papyrus.0.log does not show much seems like main menu only, no message related to DynDOLOD.
The Papyrus.1.log looks like what happens when a save that is not cleaned is being loaded.

Load whatever save that needs cleaning without any DynDOLOD output, Resources, DLLs etc. files whatsoever active in the load oder. Go into an interior if not in one. Save the game. Make a backup. Use the Clean option Remove unattached instances and Remove undefined elements for Scripts and Script Instances starting with #SHESON_DynDOLOD_* with Resaver from FallrimTools - Script cleaner and more on that save. Then load that save and save again. Then enable DynDOLOD Resources, DynDOLOD DLL NG and Scripts and the DynODLOD output make for it. Load the last save.

Sorry about that, here's the log. I'm not particularly attached to the save file, which got corrupted anyway when the Xbox game overlay decided to freeze my computer. I'll start a new game later today to see if that works.

DynDOLOD.log

[sheson]

30 minutes ago, NoCleverness said:

Sorry about that, here's the log. I'm not particularly attached to the save file, which got corrupted anyway when the Xbox game overlay decided to freeze my computer. I'll start a new game later today to see if that works.

DynDOLOD.log 327 B · 0 downloads

The DynDOLOD.log shows what happens when starting the game to the main menu only. The one that is recorded with whatever was done to produce Papyrus.1.log above would be of intertest.

If you do not care about the save, then test what happens when starting a new game (from main menu with coc riverwood for example) and in case there are issues, upload the corresponding Papyrus log and DynDOLOD.log from DynDOLOD.DLL.

[NoCleverness]

8 hours ago, sheson said:

The DynDOLOD.log shows what happens when starting the game to the main menu only. The one that is recorded with whatever was done to produce Papyrus.1.log above would be of intertest.

If you do not care about the save, then test what happens when starting a new game (from main menu with coc riverwood for example) and in case there are issues, upload the corresponding Papyrus log and DynDOLOD.log from DynDOLOD.DLL.

Having completely restarted the game, there seems to be no issues beyond the extra bumpiness of the initial carriage ride caused by having a bunch of mods initializing at once. Guess there really was something screwy with the original installation. Thank you for your patience.