DynDOLOD 3.00 Alpha 190

[duffB]

  On 2/2/2022 at 11:05 AM, sheson said:

textures\dlc01\landscape\icelakesurface.dds is a vanilla texture in Skyrim - Textures3.BSA

As the TexGen options window says: "In case of file not found errors verify the log that all the required BSA files are loaded."

Expand  

Ah yes thanks. for anyone wondering incase having the same issue: The AE update from steam changed the textures4.bsa to not include those files anymore. Im doing a full patch downgrade now to fix this.. 

[sheson]

  On 2/2/2022 at 1:25 PM, duffB said:

Ah yes thanks. for anyone wondering incase having the same issue: The AE update from steam changed the textures4.bsa to not include those files anymore. Im doing a full patch downgrade now to fix this.. 

Expand  

Let me be more specfic.

textures\dlc01\landscape\icelakesurface.dds is a vanilla texture that is in Skyrim Textures3.BSA for 1.5.x and in Skyrim Textures4.BSA for Skyrim 1.6.x

Make sure that the vanilla BSA files are listed in the [Archive] section of Skyrim.INI like in the default INI as it is created by the launcher so they are automatically loaded by xEdit/XLODGen/DynDOLOD. The loaded BSA files will be listed in the message log.

There is no need to downgrade or upgrade anything. You only need to make sure the base game is setup properly.

[duffB]

  On 2/2/2022 at 2:26 PM, sheson said:

Let me be more specfic.

textures\dlc01\landscape\icelakesurface.dds is a vanilla texture that is in Skyrim Textures3.BSA for 1.5.x and in Skyrim Textures4.BSA for Skyrim 1.6.x

Make sure that the vanilla BSA files are listed in the [Archive] section of Skyrim.INI like in the default INI as it is created by the launcher so they are automatically loaded by xEdit/XLODGen/DynDOLOD. The loaded BSA files will be listed in the message log.

There is no need to downgrade or upgrade anything. You only need to make sure the base game is setup properly.

Expand  

my skyrim.ini looks like this: 

  Quote

 

[Archive]

sResourceArchiveList=Skyrim - Misc.bsa, Skyrim - Shaders.bsa, Skyrim - Interface.bsa, Skyrim - Animations.bsa, Skyrim - Meshes0.bsa, Skyrim - Meshes1.bsa, Skyrim - Sounds.bsa

sResourceArchiveList2=Skyrim - Voices_en0.bsa, Skyrim - Textures0.bsa, Skyrim - Textures1.bsa, Skyrim - Textures2.bsa, Skyrim - Textures3.bsa, Skyrim - Textures4.bsa, Skyrim - Textures5.bsa, Skyrim - Textures6.bsa, Skyrim - Textures7.bsa, Skyrim - Textures8.bsa, Skyrim - Patch.bsa

bLoadArchiveInMemory=1

sArchiveToLoadInMemoryList=Skyrim - Animations.bsa

 

Expand  

 

and my log of texgen looks like this at the start:

  Quote

[00:00] Background Loader: starting...
[00:00] Background Loader: [Skyrim - Misc.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Shaders.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Interface.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Animations.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Meshes0.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Meshes1.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Sounds.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Voices_en0.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures0.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures1.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures2.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures3.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures4.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures5.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures6.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures7.bsa] Loading Resources.
[00:00] Background Loader: [Skyrim - Textures8.bsa] Loading Resources.

Expand  

still getting the error. 

[sheson]

  On 2/2/2022 at 2:45 PM, duffB said:

my skyrim.ini looks like this: 

 

and my log of texgen looks like this at the start:

still getting the error. 

Expand  

Start the load order in xEdit

Start the Asset Browser with CTRL + F3

Enter the filename into the filter field. The Asset Browser shows which container(s) contain the file. The first one listed wins. Data means loose files.

textures\dlc01\landscape\icelakesurface.dds is a vanilla texture that ships with the vanilla BSA files for Skyrim Special Edition or the Dawnguard DLC or HiRes DLC for Skyrim.

If the texture is not in the vanilla BSA files, then the BSA files are not vanilla anymore / being overwritten or there are some kind of access problems.

Verify the integrity of the local game files in Steam to restore the vanilla BSA files.

Read the first post which entire logfiles to upload when making posts.

[duffB]

  On 2/2/2022 at 2:55 PM, sheson said:

Start the load order in xEdit

Start the Asset Browser with CTRL + F3

Enter the filename into the filter field. The Asset Browser shows which container(s) contain the file. The first one listed wins. Data means loose files.

textures\dlc01\landscape\icelakesurface.dds is a vanilla texture that ships with the vanilla BSA files for Skyrim Special Edition or the Dawnguard DLC or HiRes DLC for Skyrim.

If the texture is not in the vanilla BSA files, then the BSA files are not vanilla anymore / being overwritten or there are some kind of access problems.

Expand  

That helped figuring out that my BSAs were appearently corrupted.. I re verified my files and it works again. Thank you for your time!

Edited February 2, 2022 by duffB

[Omniguous]

hi! good news this time!

i had been messing around with the lodgen.. trying all sorts of combinations. i was recommended to lower fblocklevel0 lod distance to below 50,000 units. suddenly: everything worked. even with the tree plugin.

just happily reporting ^^

- omniguous

Edited February 2, 2022 by Omniguous
clarification

[Mousetick]

A similar question was asked earlier but was not answered. Asking from the point of view of a mod user, not a mod author:

Am I correct in assuming that flagging an 'Initially disabled large reference' UDR in a non-ESM plugin as Deleted would turn it into a 'Overwritten large reference' 'Deleted Reference' warning? Disregarding the implications of a Deleted reference, would that actually prevent the Large Reference Bugs?

Thanks.

[sheson]

  On 2/3/2022 at 7:19 PM, Mousetick said:

A similar question was asked earlier but was not answered. Asking from the point of view of a mod user, not a mod author:

Am I correct in assuming that flagging an 'Initially disabled large reference' UDR in a non-ESM plugin as Deleted would turn it into a 'Overwritten large reference' 'Deleted Reference' warning? Disregarding the implications of a Deleted reference, would that actually prevent the Large Reference Bugs?

Thanks.

Expand  

Any large reference that is overwritten by an ESP triggers large reference bugs and if the deleted flag is set can cause CTD if anything else tries to access that reference.

To "delete" a large reference, create an overwrite in an ESM flagged plugin (can be ESL flagged, too) and move it underground z=-30000. No initially Disabled flag, no enable parent.

That is what the https://dyndolod.info/Help/Mesh-Mask-Reference-Rules Reference dropdown = Delete does. It will try to use DynDOLOD.esm for the overwrite if possible.

[Mousetick]

  On 2/3/2022 at 7:53 PM, sheson said:

Any large reference that is overwritten by an ESP triggers large reference bugs

Expand  

Sorry for being thick in the head, but this is ambiguous...  Are you considering a REFR marked Deleted in an ESP as an overwrite or not in the statement above? Again, ignoring the fact that Deleted references are dangerous, a Deleted-flagged REFR can be interpreted as "not existing", rather than "existing and overwritten". Does a Deleted-flagged REFR in an ESP at the highest priority in the load order cause the Large Reference Bugs?

Can you please clarify, thanks.

Going on a tangent here, considering that all DLCs and Update.esm are part of the vanilla SSE game, aren't you concerned that issuing all these Deleted Reference warnings for Dawnguard.esm, HearthFires.esm and Update.esm is merely "noise" that doesn't really help and can confuse users? If these references are used by SSE mods and cause CTDs, it's a bug in the mod, not in the vanilla game. For all intents and purposes, these REFR don't exist in the vanilla SSE game - they should not be used. There is no need to "clean" them either.

The WIP version of the STEP guide for SSE/SAE doesn't advise users to clean the vanilla masters. They'll be faced with a ton of Deleted Reference warnings and wondering if they've done something wrong, perhaps flooding you with stupid support questions in the process.

[broncofan0211]

Hi, I am using DynDOLOD 3 and have the latest version, plus the latest Dyndolod Resources installed. I have a problem when running Dyndolod (Texgen works fine), where it will just close on me in the middle of the process. It closes at different times (ie, MarkarthWorld, SkuldafnWorld, FalmerValley, etc). It's inconsistent. After trying 4 or 5 times, it will eventually complete successfully. I've got my mods folder exempt from antivirus, and have even tried with antivirus disabled completely. Any ideas what is causing this? Thanks in advance!

[Adven221]

Hi, why is it that when i load the game, initially i see grass lod as far as the eye can see, but after a few seconds, when the popup "DynDOLOD has successfully initialized" appears, my grass lod suddenly becomes reduced by a lot. 

[sheson]

  On 2/3/2022 at 8:45 PM, Mousetick said:

Sorry for being thick in the head, but this is ambiguous...  Are you considering a REFR marked Deleted in an ESP as an overwrite or not in the statement above? Again, ignoring the fact that Deleted references are dangerous, a Deleted-flagged REFR can be interpreted as "not existing", rather than "existing and overwritten". Does a Deleted-flagged REFR in an ESP at the highest priority in the load order cause the Large Reference Bugs?

Can you please clarify, thanks.

Going on a tangent here, considering that all DLCs and Update.esm are part of the vanilla SSE game, aren't you concerned that issuing all these Deleted Reference warnings for Dawnguard.esm, HearthFires.esm and Update.esm is merely "noise" that doesn't really help and can confuse users? If these references are used by SSE mods and cause CTDs, it's a bug in the mod, not in the vanilla game. For all intents and purposes, these REFR don't exist in the vanilla SSE game - they should not be used. There is no need to "clean" them either.

The WIP version of the STEP guide for SSE/SAE doesn't advise users to clean the vanilla masters. They'll be faced with a ton of Deleted Reference warnings and wondering if they've done something wrong, perhaps flooding you with stupid support questions in the process.

Expand  

This is an absolute statement: Any large reference that is overwritten by an ESP triggers large reference bugs.
The deleted flag does not change the fact that the large reference is being overwritten.
The ignore flag makes a record non-existent. The record does not have any affect with the ignore flag. If a record has no effect it does not overwrite anything.

See https://dyndolod.info/Help/Large-References

Message about deleted references are statements of facts.
Cleaning is a prerequisite before generating LOD. https://tes5edit.github.io/docs/7-mod-cleaning-and-error-checking.html

Update, DLC and CC plugins change between game updates and there are older mods/plugins out there that have not been made with the (future) changes / additions of plugins in mind.
If a guide wants to skip the simple and save process of cleaning to save a few minutes time in a setup that takes hours / days, then it should provide a patch that fixes such problems and other issues in the load order.
If you believe warning and error messages are noise, I suggest to simply fix the cause of the problem nonetheless. Incidentally taking care of known problems - regardless of how mundane they seem - helps greatly with stability and troubleshooting later on.

[sheson]

  On 2/3/2022 at 9:17 PM, broncofan0211 said:

Hi, I am using DynDOLOD 3 and have the latest version, plus the latest Dyndolod Resources installed. I have a problem when running Dyndolod (Texgen works fine), where it will just close on me in the middle of the process. It closes at different times (ie, MarkarthWorld, SkuldafnWorld, FalmerValley, etc). It's inconsistent. After trying 4 or 5 times, it will eventually complete successfully. I've got my mods folder exempt from antivirus, and have even tried with antivirus disabled completely. Any ideas what is causing this? Thanks in advance!

Expand  

Read the first post of the the DynDOLOD 3 alpha thread where to make post. I moved  the post.

Read the first post which log files, debug log and bugreport.txt to upload when reporting problems.

If there is no bugreport.txt it might mean the program is forcefully terminated by the OS. Check the Windows event log for entries.

  On 2/3/2022 at 9:24 PM, Adven221 said:

Hi, why is it that when i load the game, initially i see grass lod as far as the eye can see, but after a few seconds, when the popup "DynDOLOD has successfully initialized" appears, my grass lod suddenly becomes reduced by a lot. 

Expand  

Change the object LOD Level 4 distance (fBlockLevel0Distance) in the DynDOLOD SkyUI MCM to the desired distance.

Make sure to use the latest version of the DynDOLOD 3 Alpha Standalone and the DynDOLOD Resources SE 3 Alpha. In case DynDOLOD DLL is used make sure to use the latest version of the DynDOLOD DLL Scripts.

[Mousetick]

  On 2/3/2022 at 9:26 PM, sheson said:

This is an absolute statement: Any large reference that is overwritten by an ESP triggers large reference bugs.
The deleted flag does not change the fact that the large reference is being overwritten.

Expand  

Thanks for the clarification. So in the case of a Deleted-flagged large reference in an ESP, shouldn't DynDOLOD issue 2 warnings for the same record: one "Deleted reference" warning on , and one "Overwritten large reference" warning?

From https://dyndolod.info/Help/Large-References (emphasis added):

  Quote

A plugin that is not flagged as ESM overwrites the large reference record always triggers the bugs. It is the cause for the example shown video below - one or more large references are being overwritten by a ESP. A warning message Overwritten large reference is written to the message log.

Expand  

Apparently that's not the case. I just tested this scenario: I created an ESP in xEdit and flagged a large reference of Skyrim.esm as Deleted in the ESP. There is no other plugin overwriting this large reference.

With Alpha-65 I only got a "Deleted reference" warning on the Deleted References page. And that's it. Nothing on the Large Reference Bugs page.

[broncofan0211]

  On 2/3/2022 at 9:43 PM, sheson said:

  On 2/3/2022 at 9:17 PM, broncofan0211 said:

Hi, I am using DynDOLOD 3 and have the latest version, plus the latest Dyndolod Resources installed. I have a problem when running Dyndolod (Texgen works fine), where it will just close on me in the middle of the process. It closes at different times (ie, MarkarthWorld, SkuldafnWorld, FalmerValley, etc). It's inconsistent. After trying 4 or 5 times, it will eventually complete successfully. I've got my mods folder exempt from antivirus, and have even tried with antivirus disabled completely. Any ideas what is causing this? Thanks in advance!

Expand  

Read the first post of the the DynDOLOD 3 alpha thread where to make post. I moved  the post.

Read the first post which log files, debug log and bugreport.txt to upload when reporting problems.

If there is no bugreport.txt it might mean the program is forcefully terminated by the OS. Check the Windows event log for entries.

Expand  

Sorry about posting incorrectly. Yeah I don't get a bugreport log. But I did go to Windows Events. Details from the Application Error:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Application Error" />

  <EventID Qualifiers="0">1000</EventID>

  <Version>0</Version>

  <Level>2</Level>

  <Task>100</Task>

  <Opcode>0</Opcode>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2022-02-04T02:26:09.4438969Z" />

  <EventRecordID>103507</EventRecordID>

  <Correlation />

  <Execution ProcessID="0" ThreadID="0" />

  <Channel>Application</Channel>

  <Computer>PC</Computer>

  <Security />

  </System>

- <EventData>

  <Data>DynDOLODx64.exe</Data>

  <Data>3.0.0.0</Data>

  <Data>61e81ae6</Data>

  <Data>KERNELBASE.dll</Data>

  <Data>10.0.19041.1466</Data>

  <Data>e01c7650</Data>

  <Data>0eedfade</Data>

  <Data>0000000000034f69</Data>

  <Data>fa68</Data>

  <Data>01d8196c968499ea</Data>

  <Data>D:\TOOLS\DynDOLOD\DynDOLODx64.exe</Data>

  <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>

  <Data>1f743b0b-fd14-422a-ac99-46bd397b276d</Data>

  <Data />

  <Data />

  </EventData>

  </Event>

 

And also, leading up to the Error there are multiple warnings that say "The backing-file for the real-time session "Admin_PS_Provider" has reached its maximum size. As a result, new events will not be logged to this session until space becomes available. This error is often caused by starting a trace session in real-time mode without having any real-time consumers"

With these details:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}" />

  <EventID>1</EventID>

  <Version>0</Version>

  <Level>3</Level>

  <Task>1</Task>

  <Opcode>10</Opcode>

  <Keywords>0x8000000000000010</Keywords>

  <TimeCreated SystemTime="2022-02-04T02:24:58.3346641Z" />

  <EventRecordID>17203</EventRecordID>

  <Correlation />

  <Execution ProcessID="4" ThreadID="13592" />

  <Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>

  <Computer>PC</Computer>

  <Security UserID="" />

  </System>

- <EventData>

  <Data Name="SessionName">Admin_PS_Provider</Data>

  <Data Name="ErrorCode">3221225864</Data>

  <Data Name="LoggingMode">8388864</Data>

  </EventData>

  </Event>

 

Not sure if any of this is useful or not. Thanks again.

Edited February 4, 2022 by broncofan0211