DynDOLOD 3.00 Alpha 198

[TheDude]

On 8/7/2023 at 1:38 PM, sheson said:

The Whiterun/Solitude Exterior patch files in older DynDOLOD Resources that got replaced were made for the vanilla references. They do not account for mods changing child or parent worldspaces.
The patches can still be used with latest alpha versions, however they should not be used with the new parent to child worldspace copying together, hence their removal from the latest DynDOLOD Resources. I will make them available as a separate download. It needs additional checks in case users try to use both regardless of instructions.

If performance in Whiterun is a concern, do not install the Whiterun Exterior Grass patch to enable grass.

The large reference bugs workarounds offer an option to regain some performance in child worldspaces by disabling large references in child worldspaces. Regardless of any other options. It will help a it with performance in cities in any case.

HI Sheson, just a quick question regarding the Whiterun/Solitude Exterior patch files in older DynDOLOD Resources: https://dyndolod.info/Help/Child-Parent-Worldspace-Copies

I've downloaded and installed the patch and I understand that it should not be used together with the new "parent to child wordlspace" but what about the "child > parent"- option? I guess I should use that together wtih the old patch since the description says this: 

"The Child > parent option copies references that could have LOD from the child worldspaces to the parent worldspace. The copied reference usually uses the LOD model similar to the vanilla game."

[Mousetick]

36 minutes ago, sheson said:

I can not find the form IDs from the error check in the debug log you uploaded. Can you error check the esp for errors for which you uploaded the debug and give a few form ids that have that error?

The debug log I uploaded is from the exact same session that generated the DynDOLOD.esp I checked in xEdit. I was hoping the log would contain some hints. But if there are none, there isn't much more I can do

 

36 minutes ago, sheson said:

I can not find the form IDs from the error check in the debug log you uploaded. Can you error check the esp for errors for which you uploaded the debug and give a few form ids that have that error?

Perhaps another way to trace these phantom references would be to search for the form ids of valid references that precede or follow them. For example:

buvarpsereesp_001326_Tamriel_DynDOLOD_OBJECT [REFR:26271D9A] (places WalkwayStairs4_DynDOLOD_BASE [STAT:2409C83A]
[REFR:26271D9B] (places NULL - Null Reference [00000000]
[REFR:26271D9C] (places NULL - Null Reference [00000000]
[REFR:26271D9D] (places NULL - Null Reference [00000000]
[REFR:26271D9E] (places NULL - Null Reference [00000000]
legacyofthedragonbornv5esm_13DC20_Tamriel_DynDOLOD_OBJECT [REFR:26271D9F] (places _DA_Dock_ScaffoldBase4Sided2_DynDOLOD_BASE [STAT:2409CA07])
[... and so on ...]

Hope this helps.

[sheson]

2 minutes ago, TheDude said:

HI Sheson, just a quick question regarding the Whiterun/Solitude Exterior patch files in older DynDOLOD Resources: https://dyndolod.info/Help/Child-Parent-Worldspace-Copies

I've downloaded and installed the patch and I understand that it should not be used together with the new "parent to child wordlspace" but what about the "child > parent"- option? I guess I should use that together wtih the old patch since the description says this: 

"The Child > parent option copies references that could have LOD from the child worldspaces to the parent worldspace. The copied reference usually uses the LOD model similar to the vanilla game."

The documentation explains the things that need and/or can be done. The documentation does not explain the million things that do not need to be done or can not be done.

There is no instruction to disable it, which means it does not need to be disabled. The feature is irrelevant to how parent to child world copies work.

[sheson]

31 minutes ago, Mousetick said:

The debug log I uploaded is from the exact same session that generated the DynDOLOD.esp I checked in xEdit. I was hoping the log would contain some hints. But if there are none, there isn't much more I can do

 

Perhaps another way to trace these phantom references would be to search for the form ids of valid references that precede or follow them. For example:

buvarpsereesp_001326_Tamriel_DynDOLOD_OBJECT [REFR:26271D9A] (places WalkwayStairs4_DynDOLOD_BASE [STAT:2409C83A]
[REFR:26271D9B] (places NULL - Null Reference [00000000]
[REFR:26271D9C] (places NULL - Null Reference [00000000]
[REFR:26271D9D] (places NULL - Null Reference [00000000]
[REFR:26271D9E] (places NULL - Null Reference [00000000]
legacyofthedragonbornv5esm_13DC20_Tamriel_DynDOLOD_OBJECT [REFR:26271D9F] (places _DA_Dock_ScaffoldBase4Sided2_DynDOLOD_BASE [STAT:2409CA07])
[... and so on ...]

Hope this helps.

Run this test version https://mega.nz/file/8MIXnQgS#yykWl7NTkQKhW0qvTJWrbINvTNMNjRMmhIX2OS2IurE

It should hopefully fix it. If not upload new logs.

[RainingTacco]

If Dyndolod knows that there are UDRs, so it finds them, why it can't provide a log which plugins have them? That way i dont need to run the PACT tool on my whole load order and waste time.

[sheson]

16 minutes ago, RainingTacco said:

If Dyndolod knows that there are UDRs, so it finds them, why it can't provide a log which plugins have them? That way i dont need to run the PACT tool on my whole load order and waste time.

https://dyndolod.info/Generation-Instructions#https://dyndolod.info/Generation-Instructions
Clean every plugin that LOOT suggests to clean ..
The Batch Plugin Cleaner for Mod Organizer or the xEdit Cleaning Extension for Vortex help to automate some of that.

Following the instructions and proper modding practices there typically shouldn't be (m)any plugins with deleted references in the load order.
Cleaning plugins is not a waste of time. It only needs to be done to a plugin once.

DynDOLOD prints a line to the log for every deleted reference since years. https://dyndolod.info/Messages/Deleted-Reference

If you happen to use the experimental large reference workarounds and maybe have a plugin with deleted references that is not reported by LOOT, then check the debug log as explained at https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

[Mousetick]

55 minutes ago, sheson said:

Run this test version https://mega.nz/file/8MIXnQgS#yykWl7NTkQKhW0qvTJWrbINvTNMNjRMmhIX2OS2IurE

It should hopefully fix it. If not upload new logs.

It's fixed.

[sheson]

13 minutes ago, Mousetick said:

It's fixed.

That's great!

[MisterMorden]

Sheson I was curious, if one doesn't clean every plugin and tries to use the large reference bug workarounds will the result be that those plugins not cleaned will still produce the flickering seen with the large reference bug?  Or will the process simple error out?

[sheson]

14 minutes ago, MisterMorden said:

Sheson I was curious, if one doesn't clean every plugin and tries to use the large reference bug workarounds will the result be that those plugins not cleaned will still produce the flickering seen with the large reference bug?  Or will the process simple error out?

https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds
In case a deleted large reference is found and the log and error message report Deleted references: yes, the debug log will contain a line like this ..

There will be an error message about the requirements for large reference bugs workarounds not being met.

[Hardwehr]

4 hours ago, sheson said:

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log and debug log to upload when making posts.

Im sorry i thought cause its performance related i dont to do it. It was overall an unnecessary post. The generated LOD with complex material Majestic Mountains just seems to be very performance heavy. And turnign grass density to 100 is just over the top and unnecessary performance loss. 

Edited September 11, 2023 by Hardwehr

[BuddyKidd]

[Window Title]
DynDOLOD

[Main Instruction]
Error: Load order FileID [F6] can not be mapped to file FileID for file "DynDOLOD.esm"

[Content]

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.

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

https://www.dropbox.com/t/Chx57uqUBL4CwrdU

https://www.dropbox.com/t/BQkEG9r1aT7y2T6H

https://mega.nz/file/IrhGRbCb#hMlSg9aTqQXOt5-fNaxF6d6roHS5Ivw2Kuy8S7wqQnQ

 

I am using DynDOLOD 3 Alpha 146, DynDOLOD Resource Alpha 44

 

[leostevano]

hello, I would like to report using the latest Dyndolod Version 3.00 Alpha 146 and Resource SE Alpha 44

I'm using Seasons of Skyrim, and during the winter seasons all tree LODs still stuck in their respective summer mode

Here's my logs : Full Logs

Modwatch : https://modwat.ch/u/leostevano

Edited September 12, 2023 by leostevano

[sheson]

2 hours ago, BuddyKidd said:

[Window Title]
DynDOLOD

[Main Instruction]
Error: Load order FileID [F6] can not be mapped to file FileID for file "DynDOLOD.esm"

[Content]

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.

[OK] [Exit DynDOLOD]

[Footer]
Online Help | Support Forum | Copy message to clipboard

https://www.dropbox.com/t/Chx57uqUBL4CwrdU

https://www.dropbox.com/t/BQkEG9r1aT7y2T6H

https://mega.nz/file/IrhGRbCb#hMlSg9aTqQXOt5-fNaxF6d6roHS5Ivw2Kuy8S7wqQnQ

 

I am using DynDOLOD 3 Alpha 146, DynDOLOD Resource Alpha 44

Check if it works with this test version https://mega.nz/file/0AISlJiT#6HeRPRBywsWS1o54e3Yau6cVbiUEs-wDZzQurX9YCVU

[sheson]

26 minutes ago, leostevano said:

hello, I would like to report using the latest Dyndolod Version 3.00 Alpha 146 and Resource SE Alpha 44

I'm using Seasons of Skyrim, and during the winter seasons all tree LODs still stuck in their respective summer mode

Here's my logs : Full Logs

Modwatch : https://modwat.ch/u/leostevano

Unfortunately the debug log of DynDOLOD has been overwritten by starting the tool and closing it again.

Make a useful screenshot of a full model tree that has wrong LOD with more informative console as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots so we have at least one base record form id to check.

Also upload ..\DynDOLOD\Edit Scripts\Export\LODGen_SSE_Export_Tamriel.txt and LODGen_SSE_Export_Tamriel_WIN.txt