DynDOLOD 3.00 Alpha 198

[sheson]

42 minutes ago, Blackread said:

Is there a guide on how the *snow_lod_x.nif files are matched to the full models? I read through the Mod Authors page but couldn't find mentions about them.

Also, do the snow lod models support the same CRC system as the "normal" lod models? If I have, say, tundrastreamend01_1234ABCDsnow_lod_0.nif, will that be matched with a tundrastreamend01.nif with CRC32 1234ABCD whenever it's considered "snow", or with every use of tundrasteamend01.nif?

https://dyndolod.info/Mod-Authors#How-to-add-your-own-object-LOD-models:
For example, to match an object LOD model to a full model with the filename house.nif, the object LOD model needs to have the filename house_lod_[0|1|2|3].nif.
In case of filename collisions or in case of popular full models being replaced by many different mods - waterfalls or trees for example - the CRC32 of the full model should be added to LOD model filename in the form house_[CRC32]_lod_[0|1|2|3].nif.

There should be no special treatment for LOD model filenames containing the word 'snow' as far as I remember. If you experience something else, then make a report.

DynDOLOD 2.x used DynDOLOD_[SSE|TES5]_textures_names.txt for texture sets but that is not how things should be done with DynDOLOD 3.x anymore now that all LOD models define the full textures.

[Blackread]

36 minutes ago, sheson said:

https://dyndolod.info/Mod-Authors#How-to-add-your-own-object-LOD-models:
For example, to match an object LOD model to a full model with the filename house.nif, the object LOD model needs to have the filename house_lod_[0|1|2|3].nif.
In case of filename collisions or in case of popular full models being replaced by many different mods - waterfalls or trees for example - the CRC32 of the full model should be added to LOD model filename in the form house_[CRC32]_lod_[0|1|2|3].nif.

There should be no special treatment for LOD model filenames containing the word 'snow' as far as I remember. If you experience something else, then make a report.

DynDOLOD 2.x used DynDOLOD_[SSE|TES5]_textures_names.txt for texture sets but that is not how things should be done with DynDOLOD 3.x anymore now that all LOD models define the full textures.

This is what DynDOLOD is telling me:

Spoiler

---

Warning: Textures do not match for "L1_RocksTundraStreamEnd": textures\landscape\mountains\mountainslab01.dds in tundrastreamend01.nif -> textures\landscape\mountains\mountainslab02.dds in tundrastreamend01snow_lod_0.nif for BSHeartland.esm CYRTundraStreamEnd01Snow01 [STAT:280E4387]
Warning: Textures do not match for "L2_RootsandRocks:1 - L1_Rock:1": textures\landscape\mountains\mountainslab01.dds in tundrapond01.nif -> textures\landscape\mountains\mountainslab02.dds in tundrapond01snow_lod_0.nif for Update.esm TundraPond01Snow01 [STAT:0008CD45]
Warning: Textures do not match for "MountainCliffCrevasse:0": textures\landscape\mountains\mountainslab01.dds in mountaincliffcrevasse.nif -> textures\landscape\mountains\mountainslab02.dds in mountaincliffcrevasse_lod_0h.nif for MajesticMountains.esp MountainCliffCrevasse_HeavySN [STAT:00104B43]
Warning: Textures do not match for "RockTundraLand02:0": textures\landscape\dirt02.dds in rocktundraland02.nif -> textures\landscape\snow02.dds in rocktundraland02snow_lod_0.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand02:0": textures\landscape\dirt02.dds in rocktundraland02.nif -> textures\landscape\snow02.dds in rocktundraland02snow_lod_1.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand02:0": textures\landscape\dirt02.dds in rocktundraland02.nif -> textures\landscape\snow02.dds in rocktundraland02snow_lod_2.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand02:1 - L1_Rocks:1": textures\landscape\mountains\mountainslab01.dds in rocktundraland02.nif -> textures\landscape\mountains\mountainslab02.dds in rocktundraland02snow_lod_0.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand02:1 - L1_Rocks:1": textures\landscape\mountains\mountainslab01.dds in rocktundraland02.nif -> textures\landscape\mountains\mountainslab02.dds in rocktundraland02snow_lod_1.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand02:1 - L1_Rocks:1": textures\landscape\mountains\mountainslab01.dds in rocktundraland02.nif -> textures\landscape\mountains\mountainslab02.dds in rocktundraland02snow_lod_2.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand02:3": textures\landscape\mountains\mountainslab02.dds in rocktundraland02.nif -> textures\landscape\mountains\mountainslab01.dds in rocktundraland02snow_lod_0.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand02:3": textures\landscape\mountains\mountainslab02.dds in rocktundraland02.nif -> textures\landscape\mountains\mountainslab01.dds in rocktundraland02snow_lod_1.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand02:3": textures\landscape\mountains\mountainslab02.dds in rocktundraland02.nif -> textures\landscape\mountains\mountainslab01.dds in rocktundraland02snow_lod_2.nif for LegacyoftheDragonborn.esm WWWRockTundraLand02_LightSN [STAT:0E128D30]
Warning: Textures do not match for "RockTundraLand03:0": textures\landscape\dirt02.dds in rocktundraland03.nif -> textures\landscape\snow02.dds in rocktundraland03snow_lod_1.nif for MajesticMountains.esp RockTundraLand03Snow01Snow [STAT:000B6266]
Warning: Textures do not match for "RockTundraLand03:0": textures\landscape\dirt02.dds in rocktundraland03.nif -> textures\landscape\snow02.dds in rocktundraland03snow_lod_2.nif for MajesticMountains.esp RockTundraLand03Snow01Snow [STAT:000B6266]
Warning: Textures do not match for "RockTundraLand03:1 - L2_RootsRocks:1 - L1_Rocks:1": textures\landscape\mountains\mountainslab01.dds in rocktundraland03.nif -> textures\landscape\mountains\mountainslab02.dds in rocktundraland03snow_lod_1.nif for MajesticMountains.esp RockTundraLand03Snow01Snow [STAT:000B6266]
Warning: Textures do not match for "RockTundraLand03:1 - L2_RootsRocks:1 - L1_Rocks:1": textures\landscape\mountains\mountainslab01.dds in rocktundraland03.nif -> textures\landscape\mountains\mountainslab02.dds in rocktundraland03snow_lod_2.nif for MajesticMountains.esp RockTundraLand03Snow01Snow [STAT:000B6266]
Warning: Textures do not match for "RockTundraLand03:3": textures\landscape\mountains\mountainslab02.dds in rocktundraland03.nif -> textures\landscape\mountains\mountainslab01.dds in rocktundraland03snow_lod_1.nif for MajesticMountains.esp RockTundraLand03Snow01Snow [STAT:000B6266]
Warning: Textures do not match for "RockTundraLand03:3": textures\landscape\mountains\mountainslab02.dds in rocktundraland03.nif -> textures\landscape\mountains\mountainslab01.dds in rocktundraland03snow_lod_2.nif for MajesticMountains.esp RockTundraLand03Snow01Snow [STAT:000B6266]
Warning: Textures do not match for "TundraPond01:0": textures\landscape\dirt02.dds in tundrapond01.nif -> textures\landscape\snow01.dds in tundrapond01snow_lod_0.nif for Update.esm TundraPond01Snow01 [STAT:0008CD45]
Warning: Textures do not match for "TundraStreamEnd01:0": textures\landscape\dirt02.dds in tundrastreamend01.nif -> textures\landscape\snow01.dds in tundrastreamend01snow_lod_0.nif for BSHeartland.esm CYRTundraStreamEnd01Snow01 [STAT:280E4387]

If I'm reading it right, it's trying to match xxx.nif with xxxsnow_lod_[0|1|2|3].nif even though xxx_lod_[0|1|2|3].nif is also present.

Logs: https://mega.nz/file/sLNWAKSL#MkTheTPb1ywwjcndCPjcp4TwWiGrHTKXYn8FA2w-Y-w

[sheson]

1 hour ago, Blackread said:

This is what DynDOLOD is telling me:

If I'm reading it right, it's trying to match xxx.nif with xxxsnow_lod_[0|1|2|3].nif even though xxx_lod_[0|1|2|3].nif is also present.

Logs: https://mega.nz/file/sLNWAKSL#MkTheTPb1ywwjcndCPjcp4TwWiGrHTKXYn8FA2w-Y-w

Also upload C:\Pelit\Skyrim Special Edition Mod Tools\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt

[Blackread]

7 minutes ago, sheson said:

Also upload C:\Pelit\Skyrim Special Edition Mod Tools\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt

Here: https://mega.nz/file/ZGlHnDYZ#8Yu6xGt9aEVE6di0UEedQJSv7Sz7qj9lpgAAilIixhs

[TZV4344]

Another person reported a very long run time issue with Alpha166 a few days ago, and after trying with Alpha167, I don't think the issue has been resolved yet.
If I use a mod list and settings that take about 35 minutes to generate in Alpha165 and then generate in Alpha167, the generation does not finish even after 90 minutes (it is still generating as I write this).
(It is still generating as I write this, and I don't know when it will finish.)

In addition, it is frequently using up to its on-board memory limit.
This did not happen with Alpha165.
However, generation does not stop due to lack of memory.

[sheson]

23 minutes ago, TZV4344 said:

Another person reported a very long run time issue with Alpha166 a few days ago, and after trying with Alpha167, I don't think the issue has been resolved yet.
If I use a mod list and settings that take about 35 minutes to generate in Alpha165 and then generate in Alpha167, the generation does not finish even after 90 minutes (it is still generating as I write this).
(It is still generating as I write this, and I don't know when it will finish.)

In addition, it is frequently using up to its on-board memory limit.
This did not happen with Alpha165.
However, generation does not stop due to lack of memory.

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

See https://dyndolod.info/Updating#New-DynDOLOD-Version

See https://dyndolod.info/FAQ#High-memory-usage-Out-of-memory
See https://dyndolod.info/FAQ#Long-running-time-or-output-several-GB-in-file-size

[TZV4344]

I followed the update procedure.
Perform a completely new installation, but not overwrite, and modify the configuration files for the new version without copying the configuration files. Then use winmerge to do a diff comparison with the old version to make sure you are not using a different configuration. I was using in alpha165.

And even if I run it with the exact same configuration and mods as alpha165, alpha167 takes an unusually long time.
I have read the page on memory usage and if I am using the exact same settings as alpha165 where the memory usage trends were normal, do I need to change the settings in alpha167?

I will submit the logs as soon as I finish, but I am not entirely sure when the generation in alpha167 will be finished, so I would appreciate it if you could wait.

P.S.
I decided to stop the generation once, set RealTimeLog=1, and run it again to log the data.

 

Edited February 6, 2024 by TZV4344

[TZV4344]

This is a log to help you confirm the issue of Alpha167 taking too long to generate.
Generation stopped after about an hour.
I uploaded the log at that point.

https://ufile.io/4qs3huw0

[Blackread]

On 2/5/2024 at 5:17 PM, Blackread said:

Is there a guide on how the *snow_lod_x.nif files are matched to the full models? I read through the Mod Authors page but couldn't find mentions about them.

Also, do the snow lod models support the same CRC system as the "normal" lod models? If I have, say, tundrastreamend01_1234ABCDsnow_lod_0.nif, will that be matched with a tundrastreamend01.nif with CRC32 1234ABCD whenever it's considered "snow", or with every use of tundrasteamend01.nif?

One more related question, what are these h and l suffixes on the files? Do they stand for high and low, or something else?

[sheson]

7 hours ago, TZV4344 said:

This is a log to help you confirm the issue of Alpha167 taking too long to generate.
Generation stopped after about an hour.
I uploaded the log at that point.

https://ufile.io/4qs3huw0

Restore Verbose=0 in D:\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and try again.

[sheson]

26 minutes ago, Blackread said:

One more related question, what are these h and l suffixes on the files? Do they stand for high and low, or something else?

See https://dyndolod.info/Help/Snow-Ash-LOD-Shader
The HD shaders make use of the vertex color alpha value. It controls the intensity. A value of 0.0 is low while 1.0 is high. The vanilla game uses ~0.4 for light snow (object LOD meshes ending in *l.NIF) and ~0.5 for heavy snow (object LOD meshes ending in *h.NIF) .

They are typically used if the flag Uses HD LOD Texture is set. *h.nif is usually used if the editor ID indicates 'heavy' snow.

Still looking into / updating some things for the other thing.

[ikonomov]

I think I found an issue with the dragon mound above Rorikstead.  In the LOD it shows as unopened, but when the cell loads it is opened.  I've also killed that dragon, but somehow I missed the sequence of it being raised by Alduin.  I've used Version 3.00 Alpha 166 to generate the files.

[sheson]

20 minutes ago, ikonomov said:

I think I found an issue with the dragon mound above Rorikstead.  In the LOD it shows as unopened, but when the cell loads it is opened.  I've also killed that dragon, but somehow I missed the sequence of it being raised by Alduin.  I've used Version 3.00 Alpha 166 to generate the files.

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.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful screenshots with more informative console.
The cover should be dynamic LOD and thus be a clickable reference.

Double check if the LOD comes back after visiting the full cell.

[TZV4344]

2 hours ago, sheson said:

Restore Verbose=0 in D:\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and try again.

I ran the program with Verbose=0 and the generation was completed in about 30 minutes.
I am not sure how long I have had this setting turned on, but I will turn it off in the future.
Thank you very much.
I will submit the LOG just in case.

https://ufile.io/gaaze14u

Edited February 6, 2024 by TZV4344

[TomForStep]

On 2/5/2024 at 1:56 PM, z929669 said:

In the Step SSE guide, we provide suggested settings that work well for Cathedral Weathers and Cathedral Landscapes with or without complex grass/ENB.

We set the RGB values to a a uniform, moderate value to avoid tint bias and use TexGen direct/ambient to set a good exposure for grass LOD. TexGen ettings vary, depending upon weather and grass used, but the principle should work similarly. The idea is to reduce Ambient to the lowest value possible and increase Direct exposure whilst keeping RBG flat and unbiased (be sure to expand the Modify Grass Tint/Brightness spoiler).

Thank you both for your support! With the provided values in the guide, grass LOD already looks much better. Somehow I had used values before from an older guide version I had copied locally...