DynDOLOD 3.00 Alpha 182

[Ddm2468]

I am trying to run dyndolod  after following all of the installation instructions correctly. it runs and completes after being run through MO2 tools, but the problem is it is not registering any of my mods/plugins. it is only detecting the base game, DLC and creation content. i can provide screenshots/logs, honestly i am tearing my hair out and close to giving up, what am i doing wrong?

 

any help would be much appreciated,thanks!

 

[sheson]

12 hours ago, TomForStep said:

Interestingly, I get exactly the same crash on map opening when I disable DynDOLOD output...

These two entries always show up in the crash log whether DynDOLOD is enabled or disabled:

 [   0]    TESObjectSTAT(FormId: 00090983, File: `Better Dynamic Snow.esp <- Skyrim.esm`)
  [   0]    TESObjectREFR(FormId: 31089768, File: `Ambient Slaves SE.esp`, BaseForm: TESObjectSTAT(FormId: 00090983, File: `Better Dynamic Snow.esp <- Skyrim.esm`))

They both point to the same whdockdoortrim.nif (Persistent, Is Full Lod). That's how it looks in SSEEdit:

  Hide contents

For testing purposes, I disabled "Is Full LOD" on the xx089768 entry from Ambient Slaves. And lo and behold, no more crashes on opening the map! Does that make any sense??

The base record has show in worldmap flagged, which together with the IsFullLOD flag of the reference can cause CTD. Unset the IsFullLOD flag on the reference or create an overwrite for the base record into a new or existing plugin of your choice and unset the Show in Worldmap flag. That should stop the game from crashing when opening the map.

[sheson]

7 hours ago, Chromatic said:

Got this error during the last DynDOLOD run: 

  Reveal hidden contents

[Main Instruction]
Error: OpenGL: μη έγκυρη λειτουργία while processing textures\terrain\lodgen\maslea.esm\msgrassdementia1_000712fa_2.dds.

I am using the latest (24.3.1) AMD WHQL drivers. 

Logs: https://ufile.io/0oyqmll5

Is this error repeatable if you only generate SIworld for a test?

If problem persists check if adding RenderSingle=1 under [DynDOLOD] in E:\Mod Tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini makes a difference.

[sheson]

5 hours ago, Ddm2468 said:

I am trying to run dyndolod  after following all of the installation instructions correctly. it runs and completes after being run through MO2 tools, but the problem is it is not registering any of my mods/plugins. it is only detecting the base game, DLC and creation content. i can provide screenshots/logs, honestly i am tearing my hair out and close to giving up, what am i doing wrong?

any help would be much appreciated,thanks!

Moved to the DynDOLOD 3 Alpha thread.

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

Also see https://dyndolod.info/Installation-Instructions
Refer to the manual of the mod manager how to add the DynDOLOD/TexGen executables, for example Mod Organizer, Vortex. If the tools are started without setting a Game Mode with a command line argument, a message window will prompt for the desired Game Mode. For Steam versions of the game, use the game launcher to set the current location of the game in the Windows Registry. See Windows Registry Key for more. See Skyrim Special Edition GOG / Skyrim Anniversary Edition GOG in case the GOG version of the game is used.

Check the reported game Data Path in the TexGen/DynDOLOD log is the correct one and the same MO2 uses. If not see  https://dyndolod.info/Messages/Windows-Registry-Key

[TomForStep]

11 hours ago, sheson said:

The base record has show in worldmap flagged, which together with the IsFullLOD flag of the reference can cause CTD. Unset the IsFullLOD flag on the reference or create an overwrite for the base record into a new or existing plugin of your choice and unset the Show in Worldmap flag. That should stop the game from crashing when opening the map.

Yes, that did it. Thank you so much for your help and all your cool tools! Much appreciated!

[Chromatic]

14 hours ago, sheson said:

Is this error repeatable if you only generate SIworld for a test?

No, only selecting SIworld didn't have any problems and lod generation was successful.

14 hours ago, sheson said:

If problem persists check if adding RenderSingle=1 under [DynDOLOD] in E:\Mod Tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini makes a difference.

RenderSingle=1 didn't make a difference, this time lod generation was stuck at the same spot but no error message appeared. After letting DynDOLOD run for many hours with no progress, I had to close it manually and terminate the process in the task manager. No logs were generated this time.

[sheson]

3 hours ago, Chromatic said:

No, only selecting SIworld didn't have any problems and lod generation was successful.

RenderSingle=1 didn't make a difference, this time lod generation was stuck at the same spot but no error message appeared. After letting DynDOLOD run for many hours with no progress, I had to close it manually and terminate the process in the task manager. No logs were generated this time.

Keep RenderSingle=1 and add both GLDebug=1 and RealTimeLog=1 under [DynDOLOD]

Upload new log, debug log and bugreport.txt if it exists or DynDOLOD_SSE_realtime_log.txt in case it wasn't able to save the log and debug log.

[Ravandhika]

Hello, good day
I need help with my current LOD setup, so i managed to succesfully generate my LOD setup from Xlodgen with ACMOS to Texgen and Dyndolod. The first time i use the Dyndolod 3 DLL SE (not the NG) and the LOD is working alongside with ACMOS. but the problem is i'm having a crash problem whenever i loading a different save, loading previous save after dying and quitting to main menu. After i dig some information on reddit, it has link to this post

so i changed my Dyndolod DLL SE to Dyndolod DLL NG. But here is the real problem start to show, after i regenerate Dyndolod with the new script my LOD is messed up, but the weird thing is i have succesfully generate it no error or whatsoever. The problems can be seen on image below
LOD Images

So what causing this and what is the solution, i'm in a dead end here. i've been regenerating dyndolod for few times and never stumble anything like this.
What i've done so far to fix this (no luck):

1. Regenerating All lod from Terrain with Xlodgen, Road Generator with ACMOS, Texgen and dyndolod.
2. Resetting Beth Ini lod
3. Reinstalling Dyndolod

here is my Dyndolod and Texgen log

Dyndolod.log
Texgen.log

[sheson]

On 6/25/2024 at 3:22 AM, Ravandhika said:

Hello, good day
I need help with my current LOD setup, so i managed to succesfully generate my LOD setup from Xlodgen with ACMOS to Texgen and Dyndolod. The first time i use the Dyndolod 3 DLL SE (not the NG) and the LOD is working alongside with ACMOS. but the problem is i'm having a crash problem whenever i loading a different save, loading previous save after dying and quitting to main menu. After i dig some information on reddit, it has link to this post

so i changed my Dyndolod DLL SE to Dyndolod DLL NG. But here is the real problem start to show, after i regenerate Dyndolod with the new script my LOD is messed up, but the weird thing is i have succesfully generate it no error or whatsoever. The problems can be seen on image below
LOD Images

So what causing this and what is the solution, i'm in a dead end here. i've been regenerating dyndolod for few times and never stumble anything like this.
What i've done so far to fix this (no luck):

1. Regenerating All lod from Terrain with Xlodgen, Road Generator with ACMOS, Texgen and dyndolod.
2. Resetting Beth Ini lod
3. Reinstalling Dyndolod

here is my Dyndolod and Texgen log

Dyndolod.log
Texgen.log

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

See and follow https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting.

As explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs, upload the crash log when having crashes for help with proper troubleshooting or to properly report the problem while participating in the alpha test.
What is the purpose of linking to months old unrelated posts on a social media website that has nothing to do with any of your issues?
Instead of randomly changing things because of crashes, troubleshoot the actual problem or report it properly here for qualified help and advice. Otherwise, there is no point in mentioning them. https://dyndolod.info/FAQ#ILS-or-CTD

In regards to what might be shown in the screenshot, verify and/or increase LOD distances in the DynDOLOD SkyUI MCM - Settings and/or with BethINIs.

[CustardCyanide]

Hello,

I have been attempting to use DynDOLOD for Seasons of Skyrim and Seasonal Landscapes for some time, but each time I run the program it seizes up upon trying to generate the texture atlas for MarkarthWorldTreeLOD. The only mod that affects the trees in my load order (that I am aware of) is Happy Little Trees. Opening the task manager shows CPU and Disk usage dropping to 0%, while RAM usage seems to remain as usual - even after waiting 20+ minutes for progress. Any ideas on how to resolve this?

[Chromatic]

On 6/23/2024 at 6:31 PM, sheson said:

Keep RenderSingle=1 and add both GLDebug=1 and RealTimeLog=1 under [DynDOLOD]

Upload new log, debug log and bugreport.txt if it exists or DynDOLOD_SSE_realtime_log.txt in case it wasn't able to save the log and debug log.

New logs: https://ufile.io/atzdmuam 

No bugreport.txt was generated this time.

[sheson]

4 hours ago, CustardCyanide said:

Hello,

I have been attempting to use DynDOLOD for Seasons of Skyrim and Seasonal Landscapes for some time, but each time I run the program it seizes up upon trying to generate the texture atlas for MarkarthWorldTreeLOD. The only mod that affects the trees in my load order (that I am aware of) is Happy Little Trees. Opening the task manager shows CPU and Disk usage dropping to 0%, while RAM usage seems to remain as usual - even after waiting 20+ minutes for progress. Any ideas on how to resolve this?

Moved to the DynDOLOD 3 Alpha 3.

See 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 or how to enable the realtime log in case the program is terminated before it can write the logs.

See https://dyndolod.info/FAQ#TexGen-DynDOLOD-stuck-while-creating-textures

[sheson]

3 hours ago, Chromatic said:

New logs: https://ufile.io/atzdmuam 

No bugreport.txt was generated this time.

Can you test if updating to the latest AMD driver (24.5.1 I believe) makes a difference.

Can you try to keep an eye on used video memory at the time it starts generating for SIworld?

[Chromatic]

7 hours ago, sheson said:

Can you test if updating to the latest AMD driver (24.5.1 I believe) makes a difference.

Not possible. 24.3.1 is actually the latest release for my GPU (RX Vega 56) since AMD has put their older cards on a different driver release schedule, as stated here: 

Spoiler

https://www.techpowerup.com/315547/amd-puts-radeon-vega-and-polaris-gpus-on-a-slower-driver-update-track?cp=4

AMD is weaning the market off its older gaming graphics card series that predate the Radeon RX 5000 series. The company is reportedly putting older GPUs based on the "Vega" and "Polaris" graphics architectures on a slower driver update track, which means driver updates to these GPUs will be less frequent. The company's RX 5000, RX 6000, and RX 7000 series, on the other hand, will continue on with the current driver update track that includes one or more driver releases each month, including releases to fix glaring game bugs, or day-zero performance updates.

 

7 hours ago, sheson said:

Can you try to keep an eye on used video memory at the time it starts generating for SIworld?

I can't say I noticed any excessive video memory usage during the entire time DynDOLOD was running, the maximum amount I saw was ~1GB. 

Latest logs: https://ufile.io/h074r74a

No bugreport was generated this time either, the debug log is empty but I included it just in case.

 

[sheson]

8 hours ago, Chromatic said:

Not possible. 24.3.1 is actually the latest release for my GPU (RX Vega 56) since AMD has put their older cards on a different driver release schedule, as stated here: 

  Reveal hidden contents

https://www.techpowerup.com/315547/amd-puts-radeon-vega-and-polaris-gpus-on-a-slower-driver-update-track?cp=4

AMD is weaning the market off its older gaming graphics card series that predate the Radeon RX 5000 series. The company is reportedly putting older GPUs based on the "Vega" and "Polaris" graphics architectures on a slower driver update track, which means driver updates to these GPUs will be less frequent. The company's RX 5000, RX 6000, and RX 7000 series, on the other hand, will continue on with the current driver update track that includes one or more driver releases each month, including releases to fix glaring game bugs, or day-zero performance updates.

I can't say I noticed any excessive video memory usage during the entire time DynDOLOD was running, the maximum amount I saw was ~1GB. 

Latest logs: https://ufile.io/h074r74a

No bugreport was generated this time either, the debug log is empty but I included it just in case.

That is unfortunate. If nothing else helps, I would try reinstalling driver only again as you did already or maybe try an older version, just to be sure.

Interestingly in the last log it went past SIworld and had a problem one worldapace later in MerDesFantomes.

Could it be that at the time this happens there is some kind of power saving event happening, screen saver, monitor turning off, sleep mode etc.?

There should be a related entry in the Windows Event log for Access violation at address 00007FFDF089C337 in module 'atio6axx.dll'. It probably won't help us much either, but it might indicate a driver/hardware problem. Typically problems when using the OpenGL API should be reported as OpenGL errors and not cause crashes in the driver.