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

[Greg]

  On 4/19/2021 at 10:54 AM, sheson said:

LOD does not cast or receive shadows in the vanilla game. The "not" must be missing in the post. Post the link so I can update it.

Expand  

First post at the top of page 146 in the paragraph starting with "As explained many times, DynDOLOD does not change how LOD works."

 

[sheson]

  On 4/19/2021 at 11:47 AM, Greg said:

First post at the top of page 146 in the paragraph starting with "As explained many times, DynDOLOD does not change how LOD works."

 

Expand  

Thanks. Updated.

[heroofkvackers]

Latest version 2.95 is causing problems with Vortex in regards to cyclic interactions between Dyndolod and a specific mod, Cutting Room Floor. The program works as intended otherwise though.

Is there anything I can do to fix this kind of issue? My load order is fine otherwise.

[sheson]

  On 4/22/2021 at 11:56 PM, heroofkvackers said:

Latest version 2.95 is causing problems with Vortex in regards to cyclic interactions between Dyndolod and a specific mod, Cutting Room Floor. The program works as intended otherwise though.

Is there anything I can do to fix this kind of issue? My load order is fine otherwise.

Expand  

The latest version 2.95 works perfectly fine with just Cutting Room Floor. Other plugins or patches or LOOT rules might be interfering.

Make sure to use the latest versions all mods/plugins involved.

From the first post:

Because of the need to have an ESM for things to work properly, there is a chance that some records have to copy as "underwrite" into the ESM and as normal overwrite into the ESP at the same time. The DynDOLOD.esm should never have any unflagged ESP as a master and only get its records/data from masterfiles (including flagged ESP). Post a report with log in case the DynDOLOD.esm has an unflagged ESP as master. LOOT typically will let you know one way or another (reporting cyclic interaction or crash for example). Do not use such plugins for anything as they are broken.

Also post the exact error message.

[Cangar]

  On 4/19/2021 at 10:54 AM, sheson said:

LOD does not cast or receive shadows in the vanilla game. The "not" must be missing in the post. Post the link so I can update it.

Expand  

Ok cool, that explains it. Thanks! Too bad though, but I guess it would be too problematic for performance?

[sheson]

  On 4/27/2021 at 7:40 AM, Cangar said:

Ok cool, that explains it. Thanks! Too bad though, but I guess it would be too problematic for performance?

Expand  

ENB has a distance shadow effect you might want to check out.

[lupus_hegemonia]

Sorry, but each new update has more issues that the previous ones.
I used to running DynDOLOD with my prefered settings and after 40-45 minutes I was done. Now... I'm keep getting error messages.
I ran the tool and I've got this:

Creating atlas textures F:\DynDOLOD Output\Textures\DynDOLOD\LOD\DynDOLOD_Tamriel.dds from 298 textures [00:06:28.926]
[00:06:28.926] Exception in unit userscript line 350: Access violation at address 004B40A9 in module 'DynDOLOD.exe'. Write of address 00000000 [00:06:28.926]
[00:06:28.926] Check log lines above the exception for additional hints. Check the FAQ and search official forum https://stepmodifications.org/forum/forum/223-shesons-dyndolod-xlodgen/ for those errors. [00:06:28.926]
[00:06:28.926] If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum https://stepmodifications.org/forum/forum/223-shesons-dyndolod-xlodgen/ [00:06:28.928] Error: Access violation at address 004B40A9 in module 'DynDOLOD.exe'. Write of address 00000000

 

Step Modifications | Change The Game

There were nothing serious above the exception.

[lupus_hegemonia]

There were nothing serious above the exception.

I ran it again as admin, nothing - same errors.

[lupus_hegemonia]

I spoke to Avrie and he told me "he smells security issues". I have no idea what that means.

[sheson]

  On 4/29/2021 at 12:17 PM, lupus_hegemonia said:

Sorry, but each new update has more issues that the previous ones.

Expand  

Without posting about the supposedly more issues these types of statement are useless. I can guarantee every update improves something and rarely to never introduces new issues. In case an update breaks something, users make actual useful error report within hours and thus any regression is fixed shortly.

  On 4/29/2021 at 12:17 PM, lupus_hegemonia said:

I used to running DynDOLOD with my prefered settings and after 40-45 minutes I was done. Now... I'm keep getting error messages.
I ran the tool and I've got this:

Creating atlas textures F:\DynDOLOD Output\Textures\DynDOLOD\LOD\DynDOLOD_Tamriel.dds from 298 textures [00:06:28.926]
[00:06:28.926] Exception in unit userscript line 350: Access violation at address 004B40A9 in module 'DynDOLOD.exe'. Write of address 00000000 [00:06:28.926]
[00:06:28.926] Check log lines above the exception for additional hints. Check the FAQ and search official forum https://stepmodifications.org/forum/forum/223-shesons-dyndolod-xlodgen/ for those errors. [00:06:28.926]
[00:06:28.926] If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum https://stepmodifications.org/forum/forum/223-shesons-dyndolod-xlodgen/ [00:06:28.928] Error: Access violation at address 004B40A9 in module 'DynDOLOD.exe'. Write of address 00000000

 

Step Modifications | Change The Game

Expand  

Search official forum finds these:

Carefully read every line of the message that was posted. Then follow their advice.

Search official forum finds these:

  On 4/29/2021 at 12:17 PM, lupus_hegemonia said:

There were nothing serious above the exception.

Expand  

If problem persists, post error report with entire contents (not just the last couple lines) of ..\DynDOLOD\bugreport.txt and ..\DynDOLOD\logs\DynDOLOD_SSE_log.txt to official forum

[lupus_hegemonia]

Im already using the x64 version, is not the case.

In both these posts, you saying to use the x64. I never used anything but that, since I have 64bit system.

Obviously, you never crossed such problem before and this is a new issue.

[lupus_hegemonia]

And except the 64 system I have, I also have 64 GBs of RAM in my PC.
So, trust me, is not a memory issue.

[sheson]

  On 4/29/2021 at 3:06 PM, lupus_hegemonia said:

Obviously, you never crossed such problem before and this is a new issue.

Expand  

I doubt you know what I came across before and what I didn't.

  On 4/29/2021 at 3:11 PM, lupus_hegemonia said:

And except the 64 system I have, I also have 64 GBs of RAM in my PC.
So, trust me, is not a memory issue.

Expand  

I only trust log messages. Maybe look at them and follow their advice.

[z929669]

  On 4/29/2021 at 3:11 PM, lupus_hegemonia said:

And except the 64 system I have, I also have 64 GBs of RAM in my PC.
So, trust me, is not a memory issue.

Expand  

I have 32 Gb RAM and found that DynDOLOD64 2.xx will consume all of it at times during generation. This was sometimes an issue for me under that version.

AFAIK, 64-bit apps will consume whatever memory they need, so there might be a memory issue if the app wants it. If Windows is not "system managed" with respect to pagefile on a drive suited to it (SSD with free space seems best), or if you don't have the proper 'manual' allocation, you might hit the ceiling.

Under DynDOLOD 3.00 alpha 33, this is no longer an issue for me. I found that increasing LODGenThreadSplit in DynDOLOD_SSE.ini to my core # or just under (12/16 in my case) drastically reduced max memory usage on my system during generation.

With LODGenThreadSplit=12 on my system, I don't seem to use more than 6-ish Gb RAM during gen, but I would still get your pagefile set correctly if it isn't, particularly under 2.xx of DynDOLOD (assuming that the LODGenThreadSplit setting is not an option in that version).

[sheson]

  On 4/29/2021 at 5:03 PM, z929669 said:

I have 32 Gb RAM and found that DynDOLOD64 2.xx will consume all of it at times during generation. This was sometimes an issue for me under that version.

AFAIK, 64-bit apps will consume whatever memory they need, so there might be a memory issue if the app wants it. If Windows is not "system managed" with respect to pagefile on a drive suited to it (SSD with free space seems best), or if you don't have the proper 'manual' allocation, you might hit the ceiling.

Under DynDOLOD 3.00 alpha 33, this is no longer an issue for me. I found that increasing LODGenThreadSplit in DynDOLOD_SSE.ini to my core # or just under (12/16 in my case) drastically reduced max memory usage on my system during generation.

With LODGenThreadSplit=12 on my system, I don't seem to use more than 6-ish Gb RAM during gen, but I would still get your pagefile set correctly if it isn't, particularly under 2.xx of DynDOLOD (assuming that the LODGenThreadSplit setting is not an option in that version).

Expand  

We only know there was an error while generating the object LOD atlas. The cause is unknown so far without the entire logfile and bugreport being posted.