Jump to content

Recommended Posts

Posted
  On 8/20/2023 at 12:45 PM, sheson said:

Please upload the papyrus log and ..\skse\plugins\DynDOLOD_Data\DynDOLOD_NG_Tamriel.txt

Expand  

Same test as previous (Drunken Hunstman >  Whiterun > ride to Heljarchen Hall) was performed with Papyrus logging enabled.

I don't see any Papyrus log entries from DynDOLOD? Except this single line:

[08/20/2023 - 03:28:12PM] DynDOLOD 

Everything else is junk from badly coded mods.

Papyrus.0.log.7zFetching info... DynDOLOD_NG_Tamriel.7zFetching info...

Posted
  On 8/20/2023 at 1:47 PM, Mousetick said:

Same test as previous (Drunken Hunstman >  Whiterun > ride to Heljarchen Hall) was performed with Papyrus logging enabled.

I don't see any Papyrus log entries from DynDOLOD? Except this single line:

[08/20/2023 - 03:28:12PM] DynDOLOD 

Everything else is junk from badly coded mods.

Papyrus.0.log.7z 18.53 kB · 0 downloads DynDOLOD_NG_Tamriel.7z 45.93 kB · 0 downloads

Expand  

Check with this attached test version of the DynDOLOD DLL NG.

DynDOLOD.7zFetching info...

Posted

I generated dynamic lod for seasons and I have noticed lods consistently fail to unload during winter season, especially often in Whiterun tundra but also in some other regions. This mostly affects tree lods, but also some other objects similar behavior. This is not simply failing to unload after fast traveling. I have uLockedObjectMapLOD=32 in skyrim.ini with Level32=1 DynDOLOD_SSE.ini. If I use lod unloading bugfix mcm to reload the cell, it fixes the issue for the exact location I'm in but if I keep running around again after the unload bug reappears. Does not seem to ever happen outside of winter. I'm using latest DynDOLOD dll NG, with DynDOLOD 3 alpha 134. Is there more infromation I can provide?

 

Bugreport.txt

LODGen_SSE_Tamriel_WIN_log.txt

DynDOLOD_SSE_log.txt

TexGen_SSE_log.txt

Papyrus.0.log

(Dyndolod_degub_log.txt was empty and TexGen_Debug_log.txt was far too big to post as a file or text sharing, which why those were not included.)

 

Update on the above. The issue was caused by po3's seasons of skyrim. Downgrading to version 1.7.2 of that mod fixed the issue without needing to reryn DynDOLOD.

Posted
  On 8/21/2023 at 10:58 AM, Ylikollikas said:

I generated dynamic lod for seasons and I have noticed lods consistently fail to unload during winter season, especially often in Whiterun tundra but also in some other regions. This mostly affects tree lods, but also some other objects similar behavior. This is not simply failing to unload after fast traveling. I have uLockedObjectMapLOD=32 in skyrim.ini with Level32=1 DynDOLOD_SSE.ini. If I use lod unloading bugfix mcm to reload the cell, it fixes the issue for the exact location I'm in but if I keep running around again after the unload bug reappears. Does not seem to ever happen outside of winter. I'm using latest DynDOLOD dll NG, with DynDOLOD 3 alpha 134. Is there more infromation I can provide?

 

Bugreport.txt

LODGen_SSE_Tamriel_WIN_log.txt

DynDOLOD_SSE_log.txt

TexGen_SSE_log.txt

Papyrus.0.log

(Dyndolod_degub_log.txt was empty and TexGen_Debug_log.txt was far too big to post as a file or text sharing, which why those were not included.)

 

Update on the above. The issue was caused by po3's seasons of skyrim. Downgrading to version 1.7.2 of that mod fixed the issue without needing to reryn DynDOLOD.

Expand  

1.7.5.2 worked in this case https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-134/page/516/#comment-273025

Posted

I'm sure I'm going to mess up a procedure somehow in seeking support-- I apologize in advance. Never had an issue generating LOD before, but getting this error now:

[Main Instruction]
Access violation at address 00000000011D5C5C in module 'DynDOLODx64.exe'.

[Content]
Read of address 0000000000000000.

I have tried different settings, all my ITMS are clean, turning off antivirus, downclocking my CPU/Ram for more stability, disabling mods I didn't have in the past. Anything else I can do to get this working? 

 

Posted
  On 8/21/2023 at 4:59 PM, yourmusicsucks said:

I'm sure I'm going to mess up a procedure somehow in seeking support-- I apologize in advance. Never had an issue generating LOD before, but getting this error now:

[Main Instruction]
Access violation at address 00000000011D5C5C in module 'DynDOLODx64.exe'.

[Content]
Read of address 0000000000000000.

I have tried different settings, all my ITMS are clean, turning off antivirus, downclocking my CPU/Ram for more stability, disabling mods I didn't have in the past. Anything else I can do to get this working? 

Expand  

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

Disabling mods is a troubleshooting step and not a fix.

Posted

Hey there, dumb question but I couldn't find a recent answer anywhere --

How do I re-generate my Dyndolod without also doing occlusion? Unless something has changed, it used to be that you could rerun dyndolod without also doing occlusion (which you only need to do the first time you run dyndolod + any time you change worldspaces or something). 

Am I missing something? Occlusion's box is checked but greyed out so I can't uncheck it.

Posted
  On 8/21/2023 at 10:35 PM, spacepillow said:

Hey there, dumb question but I couldn't find a recent answer anywhere --

How do I re-generate my Dyndolod without also doing occlusion? Unless something has changed, it used to be that you could rerun dyndolod without also doing occlusion (which you only need to do the first time you run dyndolod + any time you change worldspaces or something). 

Am I missing something? Occlusion's box is checked but greyed out so I can't uncheck it.

Expand  

Remove Occlusion.esp from the data folder and also do not check the Occlusion data checkbox. After LOD generation put it back.

Posted (edited)

Hopefully I got this right. A bit under the weather! Sorry and thank you. My whole log folder: https://drive.google.com/file/d/1z5QOCFZc8vy5fOqkkw6lqmVU-Wpe76bx/view?usp=drive_link

And the ones I think are needed here:

TexGen_SSE_log.txtFetching info... DynDOLOD_SSE_log.zipFetching info... TexGen_SSE_Debug_log.txtFetching info... LODGen_SSE_Tamriel_log.zipFetching info...

Edited by yourmusicsucks
Posted
  On 8/22/2023 at 7:02 AM, yourmusicsucks said:
Expand  

As explained by https://dyndolod.info/Generation-Instructions, the load order should be cleaned and error checked with xEdit before generating LOD. As further explained pay to attention to all log messages. See https://dyndolod.info/Messages.

Log messages like this reported in the DynDOLOD log are the cause of the access violation. They would also have been reported by the xEdit error check:
 <Error: Unresolved FormID [E70048D3] RealisticWaterTwo.esp might be the wrong version. Error in RealisticWaterTwo - Unique Region Names - MissingEZs_AllExteriors.esp POIReach03 [CELL:00007040] (in Tamriel "Skyrim" [WRLD:0000003C] at -38,11)>
See https://dyndolod.info/Messages/Unresolved-Form-ID. RealisticWaterTwo.esp is probably the wrong version for the patch RealisticWaterTwo - Unique Region Names - MissingEZs_AllExteriors.esp or vice versa. It should run through without an access violation once all the CELLs that have unresolved form ID have been fixed.

Posted

Hey Sheson think I have found an issue between DynDOLOD and wSkeevers - Windhelm Entrance Offset Fix - Base Object Swapper https://www.nexusmods.com/skyrimspecialedition/mods/98207

here are the Logs since they are too big to upload directly - https://drive.google.com/file/d/1_N8OCrkrNstxpnevJ2FrHdP2fDPcUr-l/view?usp=sharing

 

As you can see from my screenshot there is an issue with Windhelm wall when look towards windhelm near Kynesgrove sawmill

ScreenShot2790.pngScreenShot2791.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.