DynDOLOD 3.00 Alpha 180

[sheson]

7 hours ago, dionysist said:

I couldn't find anything useful in the MO2 debug log.

I changed the setting to use profile specific ini files. I then deleted the terrain manager settings. The DynDOLOD MCM still shows those same values. I can't for the life of me figure out where they are pulling from.

DynDOLOD shows the same value as the game has stored which you have verified with the console command.
The console command shows the same value regardless of DynDOLOD being active in the load order or not, correct?

[dionysist]

A quick thank you to sheson and z929669 for the assistance.

First of all, it is not DynDOLOD. After disabling that and running getini, the value was the same 100,000. I then disabled all mods that I have installed since my last play through, as well as deleting all three of the ini files so they would be recreated. The issue persisted!

I then created a new profile, just base game no mods. The getini command showed the correct value of 53248! So yes, it is some mod. I have search within text files enabled on my PC and searched for "fblocklevel0distance" in all files, still couldn't find the culprit.

I'll keep working to figure this out.

Again, huge thank you and my apologies for taking your time. I thought it might be something with the latest version of DynDOLOD since I had just upgraded before seeing the issue.

Edited August 22 by dionysist

[aljoxo]

Alpha 178 consistently gets stuck and stalls on "exporting terrain height data" step. These logs are from me having let the program sit for ~20-30 minutes without any activity before closing the process.

I have tried doing a clean reinstall of DynDOLOD, restarting my PC, and redoing my Antivirus exceptions (Windows Defender). However, I am not quite sure what else I should be doing to try and troubleshoot this. If anyone has any thought or advice I would love to hear it.

 

Debug Log 1: https://drive.google.com/file/d/1ipqJGMscVJn_81En3AI8Tr6t1qAE06kQ/view?usp=sharing

Debug Log 2: https://drive.google.com/file/d/1RQCUuzLbnX404yeLTCP3vD7IsUryRJ_v/view?usp=sharing

DynDOLOD_SSE_log.txt DynDOLOD_SSE_log.txt

[sheson]

1 hour ago, aljoxo said:

Alpha 178 consistently gets stuck and stalls on "exporting terrain height data" step. These logs are from me having let the program sit for ~20-30 minutes without any activity before closing the process.

I have tried doing a clean reinstall of DynDOLOD, restarting my PC, and redoing my Antivirus exceptions (Windows Defender). However, I am not quite sure what else I should be doing to try and troubleshoot this. If anyone has any thought or advice I would love to hear it.

 

Debug Log 1: https://drive.google.com/file/d/1ipqJGMscVJn_81En3AI8Tr6t1qAE06kQ/view?usp=sharing

Debug Log 2: https://drive.google.com/file/d/1RQCUuzLbnX404yeLTCP3vD7IsUryRJ_v/view?usp=sharing

DynDOLOD_SSE_log.txt 1.44 MB · 1 download DynDOLOD_SSE_log.txt 735.37 kB · 1 download

Delete log folder and run this test version https://mega.nz/file/1YBEnIhC#aMSqSq3y89SvUl4vLICxWh6sLPYkEqTgGIx5w-n89ds

Upload new DynDOLOD log and debug log if issue persists.

[aljoxo]

6 hours ago, sheson said:

Delete log folder and run this test version https://mega.nz/file/1YBEnIhC#aMSqSq3y89SvUl4vLICxWh6sLPYkEqTgGIx5w-n89ds

Upload new DynDOLOD log and debug log if issue persists.

Seems the issue is still persisting. DynDOLOD is still using Memory, but the CPU usage drops down to like 1/4th to 1/5th the usage prior to the step (this is consistent with the way it was behaving on 178 as well).

Debug Log: https://drive.google.com/file/d/1MAxSqLX5BcxHnSFwfCkmygUGof-TVKGJ/view?usp=sharing

DynDOLOD_SSE_log.txt

 

Edit: tested alpha 173 and it seems to at least be making progress on the "exporting terrain height" step that 178/179test were stuck on, successfully moving on to creating texture atlases and generating tree LOD + dynamic LOD. Should note I am using the x64 version on Alpha 173.

Edit 2: alpha 173 blue screened my PC

Edit 3: successfully generated LODs on alpha 177

Edited August 23 by aljoxo
added information regarding running a test on alpha173 and alpha177

[Gamma_Metroid]

I am having some trouble getting the material names config file to work in the latest version. The check for lod models containing the "sw-moss" string only seems to be happening when the full model doesn't have a corresponding lod model supplied by vanilla skyrim or DynDOLOD.

I tried reverting to the test version that worked before but had the same problem, which would seem to indicate that it's something on my end, but I can't figure out what is wrong. Here are my logs: https://ufile.io/ydz5b5n7

For example, 05101261 has the material shader applied but is not being checked for the "sw-moss" variant lod model.

[z929669]

Warning: File not found textures\effects\fxwhitewater02_falls_n.dds. Used by meshes\lod\waterfalls\fxwaterfallbodytall02passthru_lod.nif Skyrim.esm FXWaterfallBodyTall02_static [STAT:001091F0]

This happened with Alpha 177 and now 178. DynDOLOD Resources alpha-51 seems to provide this model, so I assume the normal is missing from DynDOLOD Resources or the TexGen output, since it's not provided by the game as far as I can see.

Logs

[sheson]

9 hours ago, aljoxo said:

Seems the issue is still persisting. DynDOLOD is still using Memory, but the CPU usage drops down to like 1/4th to 1/5th the usage prior to the step (this is consistent with the way it was behaving on 178 as well).

Debug Log: https://drive.google.com/file/d/1MAxSqLX5BcxHnSFwfCkmygUGof-TVKGJ/view?usp=sharing

DynDOLOD_SSE_log.txt 735.56 kB · 1 download

 

Edit: tested alpha 173 and it seems to at least be making progress on the "exporting terrain height" step that 178/179test were stuck on, successfully moving on to creating texture atlases and generating tree LOD + dynamic LOD. Should note I am using the x64 version on Alpha 173.

Edit 2: alpha 173 blue screened my PC

Edit 3: successfully generated LODs on alpha 177

The logs show that it is stuck on something it does after exporting terrain height.
I am really just interested in problems with the latest alpha and the requested tests and their results, so there is no need to run older versions.

https://dyndolod.info/FAQ#BSOD-Blue-Screen-Of-Death
BSOD are a hardware, BIOS setting, OS or driver problem.
For example, problems with overclocking, memory timings, cooling, unstable power supply etc.
Searching the Internet for the BSOD code should help troubleshooting.

Delete old logs, run this test version https://mega.nz/file/wZwCFJhB#Z2VjOUNVKQpvcMt2RdVlYLTECo0owVZvKwwReEUWv3c and upload new log and debug log if issues persists.

[sheson]

5 hours ago, Gamma_Metroid said:

I am having some trouble getting the material names config file to work in the latest version. The check for lod models containing the "sw-moss" string only seems to be happening when the full model doesn't have a corresponding lod model supplied by vanilla skyrim or DynDOLOD.

I tried reverting to the test version that worked before but had the same problem, which would seem to indicate that it's something on my end, but I can't figure out what is wrong. Here are my logs: https://ufile.io/ydz5b5n7

For example, 05101261 has the material shader applied but is not being checked for the "sw-moss" variant lod model.

Run this test version https://mega.nz/file/wZwCFJhB#Z2VjOUNVKQpvcMt2RdVlYLTECo0owVZvKwwReEUWv3c

If there is still a problem, upload new logs and a screenshot of that STAT base record in xEdit.

[sheson]

3 hours ago, z929669 said:

Warning: File not found textures\effects\fxwhitewater02_falls_n.dds. Used by meshes\lod\waterfalls\fxwaterfallbodytall02passthru_lod.nif Skyrim.esm FXWaterfallBodyTall02_static [STAT:001091F0]

This happened with Alpha 177 and now 178. DynDOLOD Resources alpha-51 seems to provide this model, so I assume the normal is missing from DynDOLOD Resources or the TexGen output, since it's not provided by the game as far as I can see.

Logs

Verify your assumptions by checking the NIF yourself.

This is a result of automatic texture replacements based on changed full models.

You are using a waterfall mod (probably Realistic Water Two 5.7.1) that was recently updated for which updated LOD assets have not been created/released yet. Next DynDOLOD Resources SE should contain the updated LOD assets.

See https://dyndolod.info/Mods/Waterfalls

[Gamma_Metroid]

37 minutes ago, sheson said:

Run this test version https://mega.nz/file/wZwCFJhB#Z2VjOUNVKQpvcMt2RdVlYLTECo0owVZvKwwReEUWv3c

If there is still a problem, upload new logs and a screenshot of that STAT base record in xEdit.

Turns out the problem was I had an ITM override on one of the MATO forms defined in the materials config file, which was preventing it from being picked up.

[aljoxo]

On 8/23/2024 at 1:27 AM, sheson said:

The logs show that it is stuck on something it does after exporting terrain height.
I am really just interested in problems with the latest alpha and the requested tests and their results, so there is no need to run older versions.

https://dyndolod.info/FAQ#BSOD-Blue-Screen-Of-Death
BSOD are a hardware, BIOS setting, OS or driver problem.
For example, problems with overclocking, memory timings, cooling, unstable power supply etc.
Searching the Internet for the BSOD code should help troubleshooting.

Delete old logs, run this test version https://mega.nz/file/wZwCFJhB#Z2VjOUNVKQpvcMt2RdVlYLTECo0owVZvKwwReEUWv3c and upload new log and debug log if issues persists.

Hey sheson, was busy yesterday so I was unable to test. I only included the edits regarding the older versions of DynDOLOD because I had them to test and figured that there was no harm in sharing the information. The BSOD was likely unrelated to DynDOLOD anyways, I was just documenting it.

 

For the record the mega file's exe was named DynDOLOD.64.exe instead of DynDOLOD64.exe

This new test version of Alpha179

log: attached

debug log: https://drive.google.com/file/d/1m_jy_eiBPvGc9IdVvL28XKbIFzxEpatw/view?usp=sharing

DynDOLOD_SSE_log.txt

[sheson]

9 hours ago, aljoxo said:

Hey sheson, was busy yesterday so I was unable to test. I only included the edits regarding the older versions of DynDOLOD because I had them to test and figured that there was no harm in sharing the information. The BSOD was likely unrelated to DynDOLOD anyways, I was just documenting it.

 

For the record the mega file's exe was named DynDOLOD.64.exe instead of DynDOLOD64.exe

This new test version of Alpha179

log: attached

debug log: https://drive.google.com/file/d/1m_jy_eiBPvGc9IdVvL28XKbIFzxEpatw/view?usp=sharing

DynDOLOD_SSE_log.txt 735.97 kB · 1 download

Thanks. Delete old logs, then run this test version https://mega.nz/file/VVISVLwZ#BUNV8tCRdhURTDrThZWpePgGxACYOHivoCkBV8SYC9k

Upload new logs if the issue persists.

[aljoxo]

11 hours ago, sheson said:

Thanks. Delete old logs, then run this test version https://mega.nz/file/VVISVLwZ#BUNV8tCRdhURTDrThZWpePgGxACYOHivoCkBV8SYC9k

Upload new logs if the issue persists.

I was able to successfully generate LOD on this version. Thank you sheson.

 

here are the logs and debug logs in case they are of any use.

Debug Log

DynDOLOD_SSE_log.txt

[Rodocastiza]

Hello,

I have the same problem, Dyndolod is stuck at "exporting terrain height data". Eventually, it moves on, but it takes more than 30 min to advance in each worldspace. This time has taken 8.15h.

I'm running the last version, resources, DLL NG, I can run xLodGen for the terrain without problems, also TexGen. Both generate output. I've tried the test version you posted before Sheson, but with the same results.

I haven't tried the new test yet. Will do now.

Here is my log. DynDOLOD_SSE_log