DynDOLOD 3.00 Alpha 190

[Vingen]

  On 4/11/2025 at 5:23 PM, sheson said:

Upload the entire load log starting from the first line SSEEdit ... starting session

Are you using a recent version of xEdit? Get 4.1.5m from #xedit-builds channel of the xEdit Discord. Redo the error check in case you used an older version.

Start xEdit enter 000094E2 top left and hit enter to open the cell record -5,6 in Tamriel. Do the same with 000094E3 for -6,6.
Check if they look OK. Report which are the last plugins (most right) to overwrite them.

Expand  

Hello, just wanted to say that I figured it out — turned out to be an odd mix of things.

I think somethings that I cleaned using "Undelete and Disable References" in an older version of SSEEdit caused issues to it (I was using version 4.0.4). The latest versions of SSEEdit and DynDOLOD would just close or crash without a warning message. I was able to gradually chip away by disabling different plugins, and after I did reinstall some of them, they worked fine again.

Not really sure what went wrong, but probably a mix of version conflict and me being stupid while editing. Either way, thanks for the help beforehand — you definitely pointed me in the right direction.

[sheson]

  On 4/11/2025 at 2:30 AM, Jonado said:

I am getting snow on some seasonal LOD objects that are not supposed to have it. See screenshots (left one is close-up view, the right one is when viewed from a distance). This time I think I know what is going on, and it is likely a bug on the DynDOLOD side. Searching for 0200CE5E in the debug log tells me that the object is getting swapped to GlacierRubbleTrim02 (FormID 00065CA2) in summer. Well, you can see from the screenshot that this is not correct, so I did a file search for that form swap. It turns out the only reference to it is in the file zzz_Icebergs_SUM.ini.vortex_backup, i.e. a backup copy of a Seasons config file, which is not used by Seasons of Skyrim. I can of course remove the file to fix the issue (I don't really need it), but since Vortex tends to create backup copies like that, I thought it is better you fix this on the DynDOLOD end.

Logs can be found here: Logs.7z

Expand  

Try with test version https://mega.nz/file/NYgUwAxB#2u1CY-r9pXwYpG8TNvCNVx-KqBFO7vyhniaZAKQtkgk.
It should ignore the renamed *.INI files and also add a snow version for the dynamic LOD docks. Report results.

[Jonado]

  On 4/12/2025 at 1:53 PM, sheson said:

Try with test version https://mega.nz/file/NYgUwAxB#2u1CY-r9pXwYpG8TNvCNVx-KqBFO7vyhniaZAKQtkgk.
It should ignore the renamed *.INI files and also add a snow version for the dynamic LOD docks. Report results.

Expand  

Okay, I'll test it next time I run DynDOLOD (not sure when that will happen though). I found another issue, though. I am getting duplicate windmill sails on the Solitude Windmill - this time for the autumn object (from Seasonal Landscapes). Checking what happens in xEdit, it looks like in the screenshot. That doesn't look right.

[sheson]

  On 4/13/2025 at 9:49 AM, Jonado said:

Okay, I'll test it next time I run DynDOLOD (not sure when that will happen though). I found another issue, though. I am getting duplicate windmill sails on the Solitude Windmill - this time for the autumn object (from Seasonal Landscapes). Checking what happens in xEdit, it looks like in the screenshot. That doesn't look right.

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.l

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful screenshots with more informative console of the 2 windmills in action.

When making screenshots of xEdit, make sure to unfold every element to to show everything as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#xEdit-Screenshots

This looks like the DynDOLOD.esp may have been generated for a different load order or there was a problem with the full model.

[Jonado]

You already got the logs. It is the same generation as in my other recent posts. There is also nothing else that is conflicting for that record - literally all information is in the screenshot I sent you, and that applies to my entire load order as well.

But to be fair, I have changed the load order a bit since I last generated LOD. Seasonal Landscapes is FE0A4 in the logs. The relevant reference (with double windmills) is 00050C5A. What I am reacting to is that DynDOLOD is trying to apply the texture swaps to 3D index -1 for all the trishapes - they should be 11, 12, 13, and 14 respectively, just as for the regular SWindmill object. There is nothing wrong with the model. I also haven't had any issues with this model before - likely because Seasonal Landscapes already removed the Windmill fan and Dyndolod didn't do anything to change that.

[Vraylle]

I'm attaching the realtime log, as that's the only one I can generate.

I'm running TexGen for SSE under Proton 9.0.4 on Linux. The PC has 64GB RAM and 8GB swap.

After scanning the load order, TexGen displays "Gathering base records for billboards". Then memory usage (RAM and SWAP) go to 100% and the entire system freezes. After about 15 minutes, the entire Wine prefix dies/crashes. Memory is recovered but the swap remains about half full. I can see from the realtime log that it seems to be doing work, but since it uses everything it looks like the OS is killing the process when it gets the chance (again, about 15 minutes later).

I've been looking for a way to restrict the memory available to that process to just let it run and see what happens, but haven't had any luck yet.

I will say this is the first time I've run it on this particular PC, but I've run it many, many times prior.

[sheson]

  On 4/13/2025 at 1:40 PM, Jonado said:

You already got the logs. It is the same generation as in my other recent posts. There is also nothing else that is conflicting for that record - literally all information is in the screenshot I sent you, and that applies to my entire load order as well.

But to be fair, I have changed the load order a bit since I last generated LOD. Seasonal Landscapes is FE0A4 in the logs. The relevant reference (with double windmills) is 00050C5A. What I am reacting to is that DynDOLOD is trying to apply the texture swaps to 3D index -1 for all the trishapes - they should be 11, 12, 13, and 14 respectively, just as for the regular SWindmill object. There is nothing wrong with the model. I also haven't had any issues with this model before - likely because Seasonal Landscapes already removed the Windmill fan and Dyndolod didn't do anything to change that.

Expand  

For example, the xEdit screenshot does not show the model information.

Use this test version https://mega.nz/file/YA4WEDJK#h_nXE34JLaMexrwDwVN3AeJVs-d0BG9wZb6g4pvYff0

[sheson]

  On 4/14/2025 at 2:07 AM, Vraylle said:

I'm attaching the realtime log, as that's the only one I can generate.

I'm running TexGen for SSE under Proton 9.0.4 on Linux. The PC has 64GB RAM and 8GB swap.

After scanning the load order, TexGen displays "Gathering base records for billboards". Then memory usage (RAM and SWAP) go to 100% and the entire system freezes. After about 15 minutes, the entire Wine prefix dies/crashes. Memory is recovered but the swap remains about half full. I can see from the realtime log that it seems to be doing work, but since it uses everything it looks like the OS is killing the process when it gets the chance (again, about 15 minutes later).

I've been looking for a way to restrict the memory available to that process to just let it run and see what happens, but haven't had any luck yet.

I will say this is the first time I've run it on this particular PC, but I've run it many, many times prior.

Expand  

Did you change MaxTextureSize in TexGen_SSE.ini? Change it back to 16384 or try lowering it to 8192.

[Vraylle]

  On 4/14/2025 at 9:31 AM, sheson said:

Did you change MaxTextureSize in TexGen_SSE.ini? Change it back to 16384 or try lowering it to 8192.

Expand  

I had not changed it, but did try lowering it to 8192 as you suggested. It seemed to take a second longer to eat all memory and freeze the system.

Just for grins, I lowered it to 256 and tried again...same result, and about as quickly as 8192 did.

[sheson]

  On 4/14/2025 at 9:07 PM, Vraylle said:

I had not changed it, but did try lowering it to 8192 as you suggested. It seemed to take a second longer to eat all memory and freeze the system.

Just for grins, I lowered it to 256 and tried again...same result, and about as quickly as 8192 did.

Expand  

In that case try changing MaxMultiSamples to 8 or 4.

[Vraylle]

  On 4/14/2025 at 9:49 PM, sheson said:

In that case try changing MaxMultiSamples to 8 or 4.

Expand  

OK, set MaxTextureSize to 8192 and MaxMultiSamples to 4. This time it ate all the memory and froze the system for a few seconds then crashed. Again no logs except the realtime log. It looks very similar except it has 11576 lines instead of 2891. Too large to send to paste.ee.

[sheson]

  On 4/15/2025 at 2:03 AM, Vraylle said:

OK, set MaxTextureSize to 8192 and MaxMultiSamples to 4. This time it ate all the memory and froze the system for a few seconds then crashed. Again no logs except the realtime log. It looks very similar except it has 11576 lines instead of 2891. Too large to send to paste.ee.

Expand  

Read the first post, my signature or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to zip and upload large log files to a file service.

[Vraylle]

  On 4/15/2025 at 5:03 AM, sheson said:

Read the first post, my signature or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs how to zip and upload large log files to a file service.

Expand  

The file service link there hasn't worked for me in the last two days (website seems to behave normally, but uploads never complete).

Uploaded to an alternate service.

[sheson]

  On 4/15/2025 at 1:06 PM, Vraylle said:

The file service link there hasn't worked for me in the last two days (website seems to behave normally, but uploads never complete).

Uploaded to an alternate service.

Expand  

Use this test version https://mega.nz/file/FAIiWY4Z#3KPR2-46dTmtBx-hAmMlK2SKknbEuBoPk9vnqrewcuA

Add MaxRenderResolution=4096 to TexGen_SSE.ini under [TexGen] to see if it makes a difference.

[Vraylle]

  On 4/16/2025 at 6:26 AM, sheson said:

Use this test version https://mega.nz/file/FAIiWY4Z#3KPR2-46dTmtBx-hAmMlK2SKknbEuBoPk9vnqrewcuA

Add MaxRenderResolution=4096 to TexGen_SSE.ini under [TexGen] to see if it makes a difference.

Expand  

Behavior was much the same (with both the test file and the INI change you mentioned), but it seemed to immediately crash when maxing out the memory, rather than have a lengthy delay.

New realtime log.