Jump to content

Recommended Posts

Posted
  On 2/11/2025 at 10:36 PM, Isewein said:

Hi, I just wanted to report a CTD on Enderal SE which (at least according to Skyrim Crash Decoder) is due to Dyndolod. I hope that this is useful!

  Reveal hidden contents
Expand  

For future reference, attach logs as files or upload them to a paste service or a file service.

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

Doublecheck the crash does not happen with the DynDOLOD output disabled. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting

Explain what needs to be done in the game to reproduce the crash.

If that is the case, test if the crash does happen if you only hide Textures\Terrain\Vyn\Objects\Vyn.Objects_n.DDS which is reported in the crash log in the DynDOLOD output.

Upload the texture in case that made a difference. Upload new crash log in case it didn't.

Posted (edited)

Hello,

Coming here to confirm what xcal68 and Goatson said. With the new DynDOLOD version i'm having a new error check with circular seasonal swap in season/unfrozen.ini.

I already removed the line: 

;WordWallHighHrothgarBroken_DynDOLOD_NOFLAG|WordWallHighHrothgarBroken_DynDOLOD_NOFLAG_SUM
0x233B2~DynDOLOD.esm|0xC53CF~Seasonal Landscapes - Unfrozen.esp

from the .ini. I tested the new test version provided some pages ago. I've redone Texgen without a synthesis patch. Nothing seems to work, i just can't pass this.  What am i supposed to do for being able to do my lods ?

Thanks you for the help.
 

Edited by Casoar
Posted

Thanks you for your answer. it was this test version that i tried first to try fix the problem. I retried with your post but nothing is doing the circular season swap problem persist.

Posted
  On 2/12/2025 at 11:44 PM, Casoar said:

Hello,

Coming here to confirm what xcal68 and Goatson said. With the new DynDOLOD version i'm having a new error check with circular seasonal swap in season/unfrozen.ini.

I already removed the line: 

;WordWallHighHrothgarBroken_DynDOLOD_NOFLAG|WordWallHighHrothgarBroken_DynDOLOD_NOFLAG_SUM
0x233B2~DynDOLOD.esm|0xC53CF~Seasonal Landscapes - Unfrozen.esp

from the .ini. I tested the new test version provided some pages ago. I've redone Texgen without a synthesis patch. Nothing seems to work, i just can't pass this.  What am i supposed to do for being able to do my lods ?

Thanks you for the help.
 

Expand  

If you look in the console window behind the error you'll see the last one dyndolod found, it will trip the warning for every one it finds and you probably have more than one.

Posted (edited)

Hi, hopefully this is the right place to ask this, but I'm having repeatable access violations when trying to run DynDOLOD after updating to 184. TexGen has worked without any issues, and I've been generating new TexGen files as I make changes just in case. This is the most recent access violation error when running dyndolod.exe: 

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 0000000000D8D2C9 in module 'DynDOLODx64.exe' (offset CED2C9).

[Content]
Read of address 0000000000000000.

They all happen right after LODGenx64Win.exe runs. It's always an access violation but sometimes the address differs (another one ended in 153d2c9). I've tried cleaning some mods with SSSEdit that showed unresolved formid's in the debug log, but some are showing up in Skyrim.esm so not sure how to address those (or if cleaning is even fixing these issues). My dyndolod folder is right under C:\.  I've also checked for missing masters/etc with Vortex's LOOT system, added dyndolod and texgen.exe as well as the whole folder itself to the Windows defender exceptions, turning off the real-time windows defender (although some windows defenders programs show up as background processes in task manager still?), and adding the line TextureCache=10 to ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI (low memory could definitely be the problem, but I just wanted to maybe get confirmation first before going down that rabbit hole). I see on the website that access violations can be from a number of issues, so I was just hoping for some guidance in order to point me in the right direction. Thanks in advance!

bugreport: Paste.ee - View paste DmuuU0VI

logs: https://mega.nz/folder/x94HCLIT#KONiTf78Q2ou6RC2tRh7Ug

Edited by ek7016
Posted
  On 2/12/2025 at 11:53 PM, ManagePasswords said:

Hello, i was having that person's exact same problem, i can confirm for myself at least, the exe in the megas helped fix the issue. Thank you!

Expand  

can confirm this helped me as well, thanks sheson

  On 2/13/2025 at 1:44 AM, ek7016 said:

Hi, hopefully this is the right place to ask this, but I'm having repeatable access violations when trying to run DynDOLOD after updating to 184. TexGen has worked without any issues, and I've been generating new TexGen files as I make changes just in case. This is the most recent access violation error when running dyndolod.exe: 

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 0000000000D8D2C9 in module 'DynDOLODx64.exe' (offset CED2C9).

[Content]
Read of address 0000000000000000.

They all happen right after LODGenx64Win.exe runs. It's always an access violation but sometimes the address differs (another one ended in 153d2c9). I've tried cleaning some mods with SSSEdit that showed unresolved formid's in the debug log, but some are showing up in Skyrim.esm so not sure how to address those (or if cleaning is even fixing these issues). My dyndolod folder is right under C:\.  I've also checked for missing masters/etc with Vortex's LOOT system, added dyndolod and texgen.exe as well as the whole folder itself to the Windows defender exceptions, turning off the real-time windows defender (although some windows defenders programs show up as background processes in task manager still?), and adding the line TextureCache=10 to ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI (low memory could definitely be the problem, but I just wanted to maybe get confirmation first before going down that rabbit hole). I see on the website that access violations can be from a number of issues, so I was just hoping for some guidance in order to point me in the right direction. Thanks in advance!

bugreport: Paste.ee - View paste DmuuU0VI

logs: https://mega.nz/folder/x94HCLIT#KONiTf78Q2ou6RC2tRh7Ug

Expand  

try the test version above

Posted

I tried the test version but still got a similar error:

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 00000000011AD2C9 in module 'DynDOLODx64.exe' (offset CED2C9).

[Content]
Read of address 0000000000000000.

Posted (edited)

Hello I'm having three issues.

 

1. LOD doesn't appear when first starting skyrim, usually have to close out and reload game for lod to finally pop in. Buildings only have windows rendered in LOD, walls are invisible. No tree LOD or anything. 

2. When LOD does appear, my roads are hovering above the ground (as seen in picture) and i have a bunch of texture popping. ( I’m not sure if this is parallax issue, I DONT have auto parallax option enabled in auto parallax ini) 

3. Sometimes game will crash and point to a bslightingshader typically. I have no idea what that means. The crash logs always have dyndolod.dll mixed with community shaders.dll so I assume it’s one of these two mods causing the issue. At first I thought it was light placer or better third person selection but I removed both of those and still have crashes. (Those mods appeared frequently in crash log) 

im using parallax gen with a bunch of complex material overhauls that didn’t exist when I modded last so maybe I’m missing something there. I also am using latest versions of dyndolod 3 and resources and dll. 
Also running grass cache and ACMOS on my lodgen. Probably giving too much useless info but maybe it will help. 
 

ive re arranged my mods to be what i hope is the best and most proper load order I can find. I doubt im having load order issue but im sure its user error since no one else seems to have this problem. 
 

 

 

Please if someone can explain how to compress debug.log I’ll upload them as well. I’ll finish uploading dyndolod log when i get home. 

https://paste.ee/p/l0YTz1SI - modlist

ScreenShot45.png

TexGen_SSE_log.txtFetching info...

Edited by izzybinbizzy
Adding files
Posted
  On 2/12/2025 at 11:44 PM, Casoar said:

Hello,

Coming here to confirm what xcal68 and Goatson said. With the new DynDOLOD version i'm having a new error check with circular seasonal swap in season/unfrozen.ini.

I already removed the line: 

;WordWallHighHrothgarBroken_DynDOLOD_NOFLAG|WordWallHighHrothgarBroken_DynDOLOD_NOFLAG_SUM
0x233B2~DynDOLOD.esm|0xC53CF~Seasonal Landscapes - Unfrozen.esp

from the .ini. I tested the new test version provided some pages ago. I've redone Texgen without a synthesis patch. Nothing seems to work, i just can't pass this.  What am i supposed to do for being able to do my lods ?

Thanks you for the help.

Expand  

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

The error can be only reported for files that still contain at least one erroneous line. Use notepad to remove all lines that mention a DynDOLOD plugin. If you believe a file is reported in error, upload the file.

Posted
  On 2/12/2025 at 11:53 PM, ManagePasswords said:

Hello, i was having that person's exact same problem, i can confirm for myself at least, the exe in the megas helped fix the issue. Thank you!

Expand  

Thank you for reporting that the test version fixes that Access Violation as well.

  On 2/13/2025 at 2:09 AM, cornmeal said:

can confirm this helped me as well, thanks sheson

Expand  

Thank you for verifying the test version fixes the issue for you. 

  • sheson changed the title to DynDOLOD 3.00 Alpha 185
Posted
  On 2/13/2025 at 1:44 AM, ek7016 said:

Hi, hopefully this is the right place to ask this, but I'm having repeatable access violations when trying to run DynDOLOD after updating to 184. TexGen has worked without any issues, and I've been generating new TexGen files as I make changes just in case. This is the most recent access violation error when running dyndolod.exe: 

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 0000000000D8D2C9 in module 'DynDOLODx64.exe' (offset CED2C9).

[Content]
Read of address 0000000000000000.

They all happen right after LODGenx64Win.exe runs. It's always an access violation but sometimes the address differs (another one ended in 153d2c9). I've tried cleaning some mods with SSSEdit that showed unresolved formid's in the debug log, but some are showing up in Skyrim.esm so not sure how to address those (or if cleaning is even fixing these issues). My dyndolod folder is right under C:\.  I've also checked for missing masters/etc with Vortex's LOOT system, added dyndolod and texgen.exe as well as the whole folder itself to the Windows defender exceptions, turning off the real-time windows defender (although some windows defenders programs show up as background processes in task manager still?), and adding the line TextureCache=10 to ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].INI (low memory could definitely be the problem, but I just wanted to maybe get confirmation first before going down that rabbit hole). I see on the website that access violations can be from a number of issues, so I was just hoping for some guidance in order to point me in the right direction. Thanks in advance!

bugreport: Paste.ee - View paste DmuuU0VI

logs: https://mega.nz/folder/x94HCLIT#KONiTf78Q2ou6RC2tRh7Ug

Expand  

Use search to find similar posts and answers as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search
This was reported before and a test version made available in this post https://stepmodifications.org/forum/topic/20141-dyndolod-300-alpha-185/page/692/#findComment-284475

The updates in that test version are now released as Alpha-185.

Upload new logs if the issue persists.

  On 2/13/2025 at 2:28 AM, ek7016 said:

I tried the test version but still got a similar error:

[Window Title]
DynDOLOD

[Main Instruction]
Access violation at address 00000000011AD2C9 in module 'DynDOLODx64.exe' (offset CED2C9).

[Content]
Read of address 0000000000000000.

Expand  

The post of the test asks you to do this:
Delete all old logs and bugreport first. Report results, upload new logs and bugreport if issue persists.

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

Posted
  On 2/13/2025 at 4:37 AM, izzybinbizzy said:

Hello I'm having three issues.

 

1. LOD doesn't appear when first starting skyrim, usually have to close out and reload game for lod to finally pop in. Buildings only have windows rendered in LOD, walls are invisible. No tree LOD or anything. 

2. When LOD does appear, my roads are hovering above the ground (as seen in picture) and i have a bunch of texture popping. ( I’m not sure if this is parallax issue, I DONT have auto parallax option enabled in auto parallax ini) 

3. Sometimes game will crash and point to a bslightingshader typically. I have no idea what that means. The crash logs always have dyndolod.dll mixed with community shaders.dll so I assume it’s one of these two mods causing the issue. At first I thought it was light placer or better third person selection but I removed both of those and still have crashes. (Those mods appeared frequently in crash log) 

im using parallax gen with a bunch of complex material overhauls that didn’t exist when I modded last so maybe I’m missing something there. I also am using latest versions of dyndolod 3 and resources and dll. 
Also running grass cache and ACMOS on my lodgen. Probably giving too much useless info but maybe it will help. 
 

ive re arranged my mods to be what i hope is the best and most proper load order I can find. I doubt im having load order issue but im sure its user error since no one else seems to have this problem. 

Please if someone can explain how to compress debug.log I’ll upload them as well. I’ll finish uploading dyndolod log when i get home. 

https://paste.ee/p/l0YTz1SI - modlist

ScreenShot45.png

TexGen_SSE_log.txt 684.45 kB · 1 download

Expand  

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

https://dyndolod.info/FAQ#Entire-LOD-missing
Can be caused by [MapMenu] uLockedObjectMapLOD=32 in Skyrim.ini (or SkyrimCustom.INI or a mod INI), especially if there are no object LOD level 32 meshes (which is the vanilla/default). See Trees on the Map for further explanations.

https://stepmodifications.org/forum/topic/19903-lods-not-appearing/

https://dyndolod.info/FAQ#Entire-LOD-missing#Object-LOD-shows-in-active-exterior-cells
Can be caused by [MapMenu] uLockedObjectMapLOD=32 in Skyrim.ini (or SkyrimCustom.INI or a mod INI), especially if there are no object LOD level 32 meshes (which is the vanilla/default). See Trees on the Map for further explanations. Also see Maps And Map Mods and Seasons if relevant

https://stepmodifications.org/forum/topic/20455-lod-and-full-models-overlapping/

The above problems are most likely caused by not following the instructions of ACMOS.

https://dyndolod.info/FAQ#ILS-or-CTD
Install a crash logger and troubleshoot the real cause of crashes as explained in the ..DynDOLOD\Docs\DynDOLOD-README.txt.
In case any help is required with analyzing the crash log or to report actual problems, make a post on the official DynDOLOD support forum. This includes believing having found an issue with DynDOLOD and in particular when using a workaround or fix like disabling mod or plugins, changing certain settings etc.

  • Thanks 1
Posted (edited)
  On 2/13/2025 at 1:00 AM, MisterMorden said:

If you look in the console window behind the error you'll see the last one dyndolod found, it will trip the warning for every one it finds and you probably have more than one.

Expand  

Hi, thanks for your help (you too Sheson). I'm sorry to still coming, maybe i'm super dumb but the problem persist. I did what you told me, to know checking the window behind. It had a warning with snow in snowy ships- seasonal but i removed the mod for LOD generation. The problem still persist i got an error with circular seasonal swaps in Unfrozen_SUM.ini. Which i don't understand because i removed all lines with LOD or DynDOLOD in the file. I'm a bit lost i admit.

Sorry to bother.

Unfrozen_SUM.iniFetching info...

Edited by Casoar
Posted
  On 2/13/2025 at 10:28 AM, Casoar said:

Hi, thanks for your help (you too Sheson). I'm sorry to still coming, maybe i'm super dumb but the problem persist. I did what you told me, to know checking the window behind. It had a warning with snow in snowy ships- seasonal but i removed the mod for LOD generation. The problem still persist i got an error with circular seasonal swaps in Unfrozen_ini. Which i don't understand because i removed all lines with LOD or DynDOLOD in the file. I'm a bit lost i admit.

Sorry to bother.

Unfrozen_SUM.ini 134.04 kB · 0 downloads

Expand  

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

https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD
Disabling plugins, mods, meshes or textures is a troubleshooting step and not a fix. In case of problems or questions, use the official DynDOLOD support forum for qualified help and advice.

If you have a problem with errors or warnings from something else as well, then ask for help with it in order to fix it if necessary.

The uploaded file Unfrozen_SUM.ini does not contain any references to DynDOLOD plugins. The file name does not match the filename you write about "i got an error with circular seasonal swaps in Unfrozen_ini.", though that filename is probably not the one that was reported. If the file that is reported seems to be fine when you check it, it typically means you are not looking at the exact same file the game and tool use.

Without logs it is not really possible to help or troubleshoot the issue properly.

  • Like 1

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.