DynDOLOD 3.00 Alpha 182

[mostwanted11]

10 minutes ago, sheson said:

https://dyndolod.info/Official-DynDOLOD-Support-Forum#xEdit-Screenshots
If not everything of interested fits into a single screenshot, do several to show the whole record, scrolling to the bottom, too.
Do not trim anything. Do not filter anything, make sure everything is shown. Unfold elements (in particular when they link to other records) in case their content is not shown in the folded view.

Lookup the base records 00051577, 4A13010E, and the ones in DynDOLOD.esm 22014813, 2201CABB Post unfiltered screenshots of those.

I can't find 22014813 through xedit

BTW parallax txst is from parallax blending fixes mod

Edited July 14 by mostwanted11

[sheson]

8 minutes ago, mostwanted11 said:

I can't find 22014813 through xedit

BTW parallax txst is from parallax blending fixes mod

22014813 is the base record reported in the first screenshot.

Report with version of Embers XD you have installed. Version 3.0.3 does not contain a giantcampfire01burning.nif with a CRC of 61BB8719 as reported in DynDOLOD_SSE_Object_Report.txt

[mostwanted11]

2 minutes ago, sheson said:

22014813 is the base record reported in the first screenshot.

Report with version of Embers XD you have installed. Version 3.0.3 does not contain a giantcampfire01burning.nif with a CRC of 61BB8719 as reported in DynDOLOD_SSE_Object_Report.txt

i'm using 3.0.3 yeah

[sheson]

Just now, mostwanted11 said:

i'm using 3.0.3 yeah

Did you maybe change the full model with NifSkope or CAO? If so upload it. Otherwise doublecheck the source it came from.

Provide xEdit screenshot(s) of base record 22014813 that is used by the reference in the first screenshot.

[mostwanted11]

apologies about those references, they're older screenshots from the dyndolod output right before the current one, although they both have the same issue. I uploaded recent screenshots of the same 2 campfires with an SS of the base and the references. one of the campfires has fire and the other does not. As for which model I'm using, I'm using the one by https://www.nexusmods.com/skyrimspecialedition/mods/103807. However, the model got modified by Parallaxgen https://www.nexusmods.com/skyrimspecialedition/mods/120946. Not sure if this affects things? Should I try running dyndolod with both mods disabled or is it unrelated? (they both have fires as long as dyndolod is disabled)

 

The FYX Fire Reacts to Wind file: https://fastupload.io/337ad0b8ed5b60a6

The same file but edited by Parallaxgen: https://fastupload.io/8a3d43e38ab7f0b4

Edited July 14 by mostwanted11

[sheson]

8 hours ago, mostwanted11 said:

apologies about those references, they're older screenshots from the dyndolod output right before the current one, although they both have the same issue. I uploaded recent screenshots of the same 2 campfires with an SS of the base and the references. one of the campfires has fire and the other does not. As for which model I'm using, I'm using the one by https://www.nexusmods.com/skyrimspecialedition/mods/103807. However, the model got modified by Parallaxgen https://www.nexusmods.com/skyrimspecialedition/mods/120946. Not sure if this affects things? Should I try running dyndolod with both mods disabled or is it unrelated? (they both have fires as long as dyndolod is disabled)

 

The FYX Fire Reacts to Wind file: https://fastupload.io/337ad0b8ed5b60a6

The same file but edited by Parallaxgen: https://fastupload.io/8a3d43e38ab7f0b4

Change the mesh mask rule Reference setting to "Original" to see if the issue also happens without the references being replaced.

If that is the case, search https://www.nexusmods.com/skyrimspecialedition/mods/37085?tab=posts for discussions about iMaxDesired.

https://stepmodifications.org/wiki/Guide:SkyrimPrefs_INI/Particles
You can change the setting also in the game with setini "iMaxDesires:Particles" x

For the vanilla fires DynDOLOD Resources includes dynamic LOD models with removed/reduced particle counts. Using lots of full models that are not optimized in that regard for LOD might be the problem. For vanilla meshes, the flames are usually not particles either.

[mostwanted11]

7 hours ago, sheson said:

Change the mesh mask rule Reference setting to "Original" to see if the issue also happens without the references being replaced.

If that is the case, search https://www.nexusmods.com/skyrimspecialedition/mods/37085?tab=posts for discussions about iMaxDesired.

https://stepmodifications.org/wiki/Guide:SkyrimPrefs_INI/Particles
You can change the setting also in the game with setini "iMaxDesires:Particles" x

For the vanilla fires DynDOLOD Resources includes dynamic LOD models with removed/reduced particle counts. Using lots of full models that are not optimized in that regard for LOD might be the problem. For vanilla meshes, the flames are usually not particles either.

Solved it, it was Mists of tamriel's distant animated fogs. Sorry for wasting your time

[sheson]

1 hour ago, mostwanted11 said:

Solved it, it was Mists of tamriel's distant animated fogs. Sorry for wasting your time

Don't worry about it. Is raising iMaxDesired not helping at all? Only disabling the (animated) fogs?

[mostwanted11]

1 hour ago, sheson said:

Don't worry about it. Is raising iMaxDesired not helping at all? Only disabling the (animated) fogs?

Yeah unfortunately not, looks like like its a hard incompatibility

[TomForStep]

On 7/3/2024 at 1:10 PM, sheson said:

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs 
See https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots

Static object LOD meshes and textures is not affected by what DLL is used for dynamic LOD.

How the static object LOD mountains look, is defined by the object LOD mesh and the textures it uses. Information about that can be found by searching for the base record form ID or the editor ID in ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt and then looking up in MO2 right windows data tab which mods contain the used assets.
See https://dyndolod.info/Help/Object-LOD
With the filenames of the used assets it is possible to determine which mods they come from.
Also see https://dyndolod.info/Mods/Majestic-Mountains - when using that mod, the LOD models should come from it. The used textures should come from it and/or TexGen.

The color/brightness of the snow LOD shaders is defined by the records mentioned in https://dyndolod.info/Help/Snow-Ash-LOD-Shader
The vertex colors are set in the LOD models. The vertex color alpha value does not affect brightness or color, tough. It controls the amount of snow cover. The lowoer, the more rock can be seen. The higher the more of the rock is covered.

Thanks to your valuable input, I have solved the issue with the too dark mountain snow LOD.

I have used v1.03a of Majestic Mountains-BDS With LOD Fix, which was too dark in my game. With its older version v1.03, snow LOD is looking fine :-)

[yofamgaming]

Hello,

I'm writing in reference to Harbourside Manor, available from Nexus here:
https://www.nexusmods.com/skyrimspecialedition/mods/8053

This is a no-load-door house, built up of multiple individual pieces. In short, its windows and columns do not appear at long distance, and its walls are invisible at long and medium distance.

This link will take you to a .7z with all the relevant logs I could find, and several screen shots.
https://drive.google.com/file/d/11-t-Gz0f1E8WdOizS9kMGIl0fOgRMNSX/view?usp=sharing

Mostly, the screens demonstrate the approach to the home, and the two waves of pop-in. Cell coordinates are included in the filenames. With DynDOLOD Output disabled, the entire homestead only appears at very close range.

Current modlist won't be a perfect match. I'm fine-tuning the L.O. but I haven't touched that worldspace. Modwatch has been down all day, but here's a text version (good for 21 days. I'll update if I can get something better going).
https://pastebin.mozilla.org/erNLpgDn

I did open the Harbourside plugin with SSEedit. It looks to me like those walls are using a vanilla interior mesh. I don't know if that means anything, and it wouldn't explain the windows. Seems worth noting anyway. A couple of SSEedit screens are included too.

Please let me know if I can add details, more screens, whatever is helpful. I really appreciate the work you put in. Many thanks!

[sheson]

5 hours ago, yofamgaming said:

Hello,

I'm writing in reference to Harbourside Manor, available from Nexus here:
https://www.nexusmods.com/skyrimspecialedition/mods/8053

This is a no-load-door house, built up of multiple individual pieces. In short, its windows and columns do not appear at long distance, and its walls are invisible at long and medium distance.

This link will take you to a .7z with all the relevant logs I could find, and several screen shots.
https://drive.google.com/file/d/11-t-Gz0f1E8WdOizS9kMGIl0fOgRMNSX/view?usp=sharing

Mostly, the screens demonstrate the approach to the home, and the two waves of pop-in. Cell coordinates are included in the filenames. With DynDOLOD Output disabled, the entire homestead only appears at very close range.

Current modlist won't be a perfect match. I'm fine-tuning the L.O. but I haven't touched that worldspace. Modwatch has been down all day, but here's a text version (good for 21 days. I'll update if I can get something better going).
https://pastebin.mozilla.org/erNLpgDn

I did open the Harbourside plugin with SSEedit. It looks to me like those walls are using a vanilla interior mesh. I don't know if that means anything, and it wouldn't explain the windows. Seems worth noting anyway. A couple of SSEedit screens are included too.

Please let me know if I can add details, more screens, whatever is helpful. I really appreciate the work you put in. Many thanks!

https://dyndolod.info/FAQ#Something-does-not-have-LOD
For something to have LOD, a LOD model or a LOD Billboard is required to be installed in the load order. Check the ..\DynDOLOD\Logs\DynDOLOD_[GAME MODE]_Object_Report.txt to find which LOD models have been found and which models are used for LOD representation.
If a LOD model does not exist, mesh mask / reference rules can be used to use the full model for LOD.

See https://dyndolod.info/Help/Mesh-Mask-Reference-Rules and https://dyndolod.info/Mod-Authors

Based on the screenshots, mesh mask rules like this will instruct to use the full model for LOD similar to the Hearthfires objects:
Mesh mask: smdfwalsol01.nif
LOD4 and LOD8: Full
LOD16 and LOD32: None
Grid: FarFull
Reference: Unchanged
Repeat for any other full model that does not have LOD.

The window seems to have transparent glass, so a rule for it should set all 4 static LOD to None:
Mesh mask: glasspanelg_noedge.nif
LOD4, LOD8 LOD16 and LOD32: None
Grid: FarFull
Reference: Unchanged

[Dunmermage]

Okay got TexGEN64 running, 50% goal
 

Texgen64 and Dyndolod64 are started from Vortex with arguments, here texgen64 is okay with the arguments and dyndolod64 show the registry key bug.

-m:"D:\Users\ew-te\Documents\My Games\Skyrim Special Edition GOG\"  

-p:"C:\Users\ew-te\AppData\Local\Skyrim Special Edition GOG\plugins.txt"  

-d:"D:\Program Files\GOG Galaxy\Games\Skyrim Anniversary Edition\Data\"

 

Had a look in the logs folder, placed 'Notice=1' into the DynDOLOD_SSE.ini, begging i got a log from it. The game registry key seems to be here and i dunno if this is something new?

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GOG.com\Games\1711230643

 

Next question, why is TexGEN64 okay with the -d argument and DyDOLOD64 has a problem with it?

 

 

 

[sheson]

5 hours ago, Dunmermage said:

Okay got TexGEN64 running, 50% goal
 

Texgen64 and Dyndolod64 are started from Vortex with arguments, here texgen64 is okay with the arguments and dyndolod64 show the registry key bug.

-m:"D:\Users\ew-te\Documents\My Games\Skyrim Special Edition GOG\"  

-p:"C:\Users\ew-te\AppData\Local\Skyrim Special Edition GOG\plugins.txt"  

-d:"D:\Program Files\GOG Galaxy\Games\Skyrim Anniversary Edition\Data\"

Had a look in the logs folder, placed 'Notice=1' into the DynDOLOD_SSE.ini, begging i got a log from it. The game registry key seems to be here and i dunno if this is something new?

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GOG.com\Games\1711230643

Next question, why is TexGEN64 okay with the -d argument and DyDOLOD64 has a problem with it?

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

No copy/pasted command line arguments or a screenshot showing the entry in the Vortex settings has been provided.

The reason why TexGen works is that the command line arguments were entered correctly. The reason that DynDOLOD does not work is most likely because the command line arguments have not been entered correctly.

xEdit (and thus  xLODGen, TexGen and DynDOLOD) only looks for the Steam registry key, hence why the explanations to add the 3 command line arguments exist. Read https://dyndolod.info#Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG or https://dyndolod.info/Mods/Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG.

[Dunmermage]

Really thanks for this hint,

had two spaces between the 3 arguments in Vortex argument line, because of the tiny font. That's so stupid, because last week i did the same with MO2 under Linux and did not fail the argument line.

Thanks thanks thanks