DynDOLOD Beta for Skyrim Special Edition, Skyrim VR and Enderal SE 2.98

[manguz]

  On 1/28/2020 at 12:29 PM, sheson said:

The building appears to be perfectly. Why do you believe DynDOLOD adds it?

Have you looked up the form id in xEdit to find its true source?

Yeah, I searched through my installation and this should come from Skyrim Witcher Experience Enhanced mod.

the building is half broken mixed with lod nif's.

But It is placed there by dyndolod I think, I don't know why dyndolod picked this up and placed it there , as I am not really into the

internals of how dyndolod really works :D (magic).

I will find a way to exclude this mod from next dyndolod generation or I think I can just disable it in my save.

Thanks for your amazing work

Edited January 28, 2020 by manguz

[sheson]

  On 1/28/2020 at 1:09 PM, manguz said:

Yeah, I searched through my installation and this should come from Skyrim Witcher Experience Enhanced mod.

the building is half broken mixed with lod nif's.

But It is placed there by dyndolod I think, I don't know why dyndolod picked this up and placed it there , as I am not really into the

internals of how dyndolod really works :D (magic).

I will find a way to exclude this mod from next dyndolod generation or I think I can just disable it in my save.

Thanks for your amazing work

It is not a single buildings, but at least 3 parts. It is possible that not all parts are in the loaded cells, hence some parts might be already LOD.

 

DynDOLOD only places objects if t hey already exist in other plugins.

 

The reference form id (the number shows in the game console when clicking a loaded object) will solve the mystery in seconds:

 

The first two digest are the hex load order of the plugin that adds it.

If that happens to be DynDOLOD, look up the form id in xEdit and check the EditorID which will be [plugin name]_[original form id]

 

Based on that either remove the mod entirely if you don't like it, or create rules for DynDOLOD so things are ignored for LOD.

Edited January 28, 2020 by sheson

[manguz]

  On 1/28/2020 at 1:56 PM, sheson said:

It is not a single buildings, but at least 3 parts. It is possible that not all parts are in the loaded cells, hence some parts might be already LOD.

 

DynDOLOD only places objects if t hey already exist in other plugins.

 

The reference form id (the number shows in the game console when clicking a loaded object) will solve the mystery in seconds:

 

The first two digest are the hex load order of the plugin that adds it.

If that happens to be DynDOLOD, look up the form id in xEdit and check the EditorID which will be [plugin name]_[original form id]

 

Based on that either remove the mod entirely if you don't like it, or create rules for DynDOLOD so things are ignored for LOD.

 

 

Will do, thank you very much

[xcal68]

Hi there,

 

When I comment out "LabyrinthianMazeWorld (Shalidor's Maze) - Skyrim.esm" in "DynDOLOD_SSE_worldspace_ignore.txt" I no longer see it appear on the DynDOLOD Worlds list.  I have "BSHeartland (Tamriel) - bsheartland.esm" commented and that appears on the list as expected.

 

In previous versions, when I commented LabyrinthianMazeWorld, it did appear on the list.  I have reinstalled DynDOLOD.  Anything else I should try?

 

Regards.

[sheson]

  On 2/5/2020 at 2:05 AM, xcal68 said:

Hi there,

 

When I comment out "LabyrinthianMazeWorld (Shalidor's Maze) - Skyrim.esm" in "DynDOLOD_SSE_worldspace_ignore.txt" I no longer see it appear on the DynDOLOD Worlds list.  I have "BSHeartland (Tamriel) - bsheartland.esm" commented and that appears on the list as expected.

 

In previous versions, when I commented LabyrinthianMazeWorld, it did appear on the list.  I have reinstalled DynDOLOD.  Anything else I should try?

 

Regards.

Only world with a valid LOD settings file will be considered for LOD generation. The vanilla game has no LOD setting file for LabyrinthianMazeWorld.

The unofficial patch includes a LOD settings file for it.

 

There is no point in generating LOD for LabyrinthianMazeWorld. It is too small and there are no visual improvements.

[Sharlikran]

307.202002061758

Latest nightly with the DynDoLod friendly changes. Currently using the changes that remove libloot python but I have seen it work correctly. If there are any bash tags not being recognized please post that in the Wrye Bash discord after looking at the LOOT masterlist first. There are different versions of the masterlist for the different syntaxes.

 

Zanderat and DarthVitrial see how that version works for you.

Edited February 6, 2020 by Sharlikran

[Zanderat]

  On 2/6/2020 at 6:23 PM, Sharlikran said:

307.202002061758

 

Latest nightly with the DynDoLod friendly changes. Currently using the changes that remove libloot python but I have seen it work correctly. If there are any bash tags not being recognized please post that in the Wrye Bash discord after looking at the LOOT masterlist first. There are different versions of the masterlist for the different syntaxes.

 

Zanderat and DarthVitrial see how that version works for you.

On it.

[Zanderat]

@Sharlikran#0541 I am getting an error with the version you asked me to test.  I never had to give WB admin rights before.   Path is C:\Steam Games\steamapps\common\Skyrim Special Edition\Data. 

 

Edited February 6, 2020 by Zanderat

[Zanderat]

I can't edit above.  Will follow up on Discord.

[Zanderat]

Ok. After a reboot, I was able to save. So, something was borked on my end. For me, this WB build is good. Thanks.

[CVSickle]

I've run DynDOLOD on multiple occasions and never ran into anything like this. I'm looking for some help to point me in the right direction to figure this out.

 

Here's my LOG and BUG REPORT

 

The log makes it look like it's failing when it's processing patches from Cutting Room Floor, but it also mentions file ID 90, which is a merge of several audio patches I've put together. The weird part is that when I remove the conflict resolution patch I'm building at the bottom of the load order, DynDOLOD runs fine.

 

xEdit is not finding any errors for the conflict resolution patch or the merged audio patches. Can someone point me in the right direction to figure this out? Will any more information be helpful?

 

BTW: the merged audio patches includes Dreams and Nightmares, which does edit worldspace and cell records to change the music type, but I've included that same mod inside of a merge in a previous load order and DynDOLOD worked fine then.

 

Thanks!

[sheson]

  On 2/7/2020 at 1:41 AM, CVSickle said:

I've run DynDOLOD on multiple occasions and never ran into anything like this. I'm looking for some help to point me in the right direction to figure this out.

 

Here's my LOG and BUG REPORT

 

The log makes it look like it's failing when it's processing patches from Cutting Room Floor, but it also mentions file ID 90, which is a merge of several audio patches I've put together. The weird part is that when I remove the conflict resolution patch I'm building at the bottom of the load order, DynDOLOD runs fine.

 

xEdit is not finding any errors for the conflict resolution patch or the merged audio patches. Can someone point me in the right direction to figure this out? Will any more information be helpful?

 

BTW: the merged audio patches includes Dreams and Nightmares, which does edit worldspace and cell records to change the music type, but I've included that same mod inside of a merge in a previous load order and DynDOLOD worked fine then.

 

Thanks!

From the log:

 

Exception in unit userscript line 249: Load order FileID [90] can not be mapped to file FileID for file "DynDOLOD.esp"

Check log lines above the exception for additional hints. Check the FAQ and search official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/ for those errors.

 

 

 

FAQ: DynDOLOD.exe: Load order FileID [xx] can not be mapped to file FileID for file xxx.esp

 

A: There is a plugin in the load order with errors. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help. 

 

 

 

Probably caused by plugin # 90 Audio Patches Merged.esp

 

Remove it and see if it runs through. If it does it means the plugin is broken and needs to be created again.

 

If created with Wrye Bash, use newer version from couple posts above https://forum.step-project.com/topic/13894-dyndolod-beta-for-skyrim-special-edition-and-skyrim-vr-281/page-125?p=239247&do=findComment&comment=239247

Edited February 7, 2020 by sheson

[Sharlikran]

  On 2/7/2020 at 1:41 AM, CVSickle said:

I've run DynDOLOD on multiple occasions and never ran into anything like this. I'm looking for some help to point me in the right direction to figure this out.

 

Here's my LOG and BUG REPORT

 

The log makes it look like it's failing when it's processing patches from Cutting Room Floor, but it also mentions file ID 90, which is a merge of several audio patches I've put together. The weird part is that when I remove the conflict resolution patch I'm building at the bottom of the load order, DynDOLOD runs fine.

 

xEdit is not finding any errors for the conflict resolution patch or the merged audio patches. Can someone point me in the right direction to figure this out? Will any more information be helpful?

 

BTW: the merged audio patches includes Dreams and Nightmares, which does edit worldspace and cell records to change the music type, but I've included that same mod inside of a merge in a previous load order and DynDOLOD worked fine then.

 

Thanks!

LOOT does not analyze plugins. So when you see warnings like, "this plugins has errors" then that's hand entered text that shows up when the plugin is in your data folder. xEdit check for errors checks for things like out of order subrecords, missing references which show up as , and records that should not be part of certain subrecords like when you see Found a NULL reference, expected: ACHR,ACRE,PBEA.

 

There could be 10 really important issues that users should be aware of in any plugin and I will bet xEdit doesn't check for any of them. The only tool with actual error checking is the CK.

 

I suggest reviewing The Method. There is a new section with dangers on compacting plugins. Because sheson's answer was RTM and possibly rebuild the mreged mods. No modding tool authors can work with broken plugins.

Edited February 7, 2020 by Sharlikran

[CVSickle]

  On 2/7/2020 at 7:46 AM, sheson said:

 

From the log:

 

Exception in unit userscript line 249: Load order FileID [90] can not be mapped to file FileID for file "DynDOLOD.esp"

Check log lines above the exception for additional hints. Check the FAQ and search official forum http://forum.step-project.com/forum/101-shesons-dyndolod-support/ for those errors.

 

 

 

FAQ: DynDOLOD.exe: Load order FileID [xx] can not be mapped to file FileID for file xxx.esp

 

A: There is a plugin in the load order with errors. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help. 

 

 

 

Probably caused by plugin # 90 Audio Patches Merged.esp

 

Remove it and see if it runs through. If it does it means the plugin is broken and needs to be created again.

 

If created with Wrye Bash, use newer version from couple posts above https://forum.step-project.com/topic/13894-dyndolod-beta-for-skyrim-special-edition-and-skyrim-vr-281/page-125?p=239247&do=findComment&comment=239247

 

Thanks for the reply!

 

Like I mentioned, DynDOLOD works just fine with the merged audio patches plugin so long as I remove the Conflict Resolution plugin at the end. I've been patching everything by hand in xEdit, which is where the conflict resolution plugin comes from. And like I said, xEdit reports no errors between those two plugins.  What type of errors am I looking for, specifically?  With the entire load order, I have a few tint mask issues to sort out and the normal errors that some of Enai's mods give you, but nothing that would effect cell or worldspace records, which I assume would be the problem.

 

Thanks again for the help!

  On 2/7/2020 at 8:47 AM, Sharlikran said:

LOOT does not analyze plugins. So when you see warnings like, "this plugins has errors" then that's hand entered text that shows up when the plugin is in your data folder. xEdit check for errors checks for things like out of order subrecords, missing references which show up as < Error: Could not be resolved >, and records that should not be part of certain subrecords like when you see Found a NULL reference, expected: ACHR,ACRE,PBEA.

 

There could be 10 really important issues that users should be aware of in any plugin and I will bet xEdit doesn't check for any of them. The only tool with actual error checking is the CK.

 

I suggest reviewing The Method. There is a new section with dangers on compacting plugins. Because sheson's answer was RTM and possibly rebuild the mreged mods. No modding tool authors can work with broken plugins.

Thanks, I'll try to check for errors using the CK and see if that shows anything. The merged mod causes no problems for DynDOLOD as long as my conflict resolution plugin is disabled, so it seems like a winning record of some kind in there is causing the problem. Just trying to figure out which one.

[sheson]

  On 2/7/2020 at 12:55 PM, CVSickle said:

Thanks for the reply!

 

Like I mentioned, DynDOLOD works just fine with the merged audio patches plugin so long as I remove the Conflict Resolution plugin at the end. I've been patching everything by hand in xEdit, which is where the conflict resolution plugin comes from. And like I said, xEdit reports no errors between those two plugins.  What type of errors am I looking for, specifically?  With the entire load order, I have a few tint mask issues to sort out and the normal errors that some of Enai's mods give you, but nothing that would effect cell or worldspace records, which I assume would be the problem.

 

Thanks again for the help!

 

Thanks, I'll try to check for errors using the CK and see if that shows anything. The merged mod causes no problems for DynDOLOD as long as my conflict resolution plugin is disabled, so it seems like a winning record of some kind in there is causing the problem. Just trying to figure out which one.

If the error still happens at "Processing 5 patches from DynDOLOD\DynDOLOD_SSE_cuttingroomflooresp_tamriel.patch", check the plugin is at the load order hex number that is mentioned in the error message.

If that does not help check the last plugin to overwrites 0001A280 or 0001A26F.

 

xEdit checks for some typical logical errors made by CK and people. Patchers, tools can create wrong data when saving/creating plugins which only trigger checks in xEdit or cause problems if records are accessed for copying.