Dynamic Distant Objects LOD - DynDOLOD for Skyrim and Enderal 2.98

[sheson]

1 hour ago, Hypernova1912 said:

What is the in-game effect of "never ignore neverfades in child worlds for upgrading to static or dynamic LOD" in DynDOLOD 2.94? Also, on a related note, why are there no rules for Solitude Expansion in DynDOLOD SSE? Are they just unnecessary due to changes in the SSE version of the mod or the game itself?

Also, is there a way to configure DynDOLOD to keep a LOD object loaded even when close enough for the full model to load, or alternatively load the full model of an object that a mod places in the Tamriel worldspace in a child world?

There are config settings that purposefully result in ignoring references placed in child worlds so they are not copied to the parent and not have LOD. However, this also resulted in references with IsFullLOD to not being converted to static or dynamic LOD.

Unless somebody reports issues with a mod (or I happen to notice them myself on occasion) there is no reason for it to have rules.

Check the different options for the Reference setting to change behavior of the dynamic LOD model. They are explained on the edit mesh rule option window. You are looking for "Keep" or maybe "Replace", DynDOLOD 3 has even more specific options.

If the child world to parent world copy should be the using the full model, add the source reference to ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[TES5|SSE]_childworldfull.txt
If you believe it makes sense for such an update to be included in standalone archive by default just let me know the mod and reference(s).

You'll probably benefit from reading DynDOLOD_Reference.html included in the DynDOLOD 3 archive.

[Benna96]

Hello. I use the mod Immersive Roads, which adds in some extra road statics to replace some vanilla road statics, for variety. Currently, the LOD for all these extra roads is rendered as just the default road though. For example, by default, the default road has green sides, while the road around Whiterun has orange sides. The LOD is green while the actual road is orange, the difference is quite jarring.

I've managed to make TexGen generate LOD textures for the new roads, no problem there. But I can't figure out how to make DynDOLOD acknowledge them. It's not adding the new textures to the atlas, nor is it using them in the .bto files.

[Benna96]

I realise now that I posted on the wrong thread. I'm using SE.

[sheson]

8 hours ago, Benna96 said:

Hello. I use the mod Immersive Roads, which adds in some extra road statics to replace some vanilla road statics, for variety. Currently, the LOD for all these extra roads is rendered as just the default road though. For example, by default, the default road has green sides, while the road around Whiterun has orange sides. The LOD is green while the actual road is orange, the difference is quite jarring.

I've managed to make TexGen generate LOD textures for the new roads, no problem there. But I can't figure out how to make DynDOLOD acknowledge them. It's not adding the new textures to the atlas, nor is it using them in the .bto files.

The LOD models included in DynDOLOD Resources for roads have no sides, they just have the cobble stone. TexGen should update the cobble stone to match.

Maybe provide a screenshot.

[Benna96]

5 hours ago, sheson said:

The LOD models included in DynDOLOD Resources for roads have no sides, they just have the cobble stone. TexGen should update the cobble stone to match.

Maybe provide a screenshot.

The "sides" I'm talking about are included in the texture, no mesh changes, just textures. In vanilla, roads use road01.dds, road01fallforest01.dds, or road01reach01.dds. The mod adds in roads using road01ea.dds, road01sp.dds, and road01wh.dds, by attaching alternate textures in an esp file. TexGen deals fine with all the textures after I added a txt file to generate lod for the new textures as well. The problem is, any road using road01ealod.dds, road01sp.dds, or road01whlod.dds, DynDOLOD renders as using road01lod.dds.

Here's a screenshot. (And a higher quality version if needed). The lod, on the right, is using road01.dds, which has green in it. The actual road, on the left, is using road01wh.dds, which has... I guess it's more of a brown, in it. It seems to me like DynDOLOD is acting as if the road was never changed to another, all these roads were originally ones using road01.dds I think.

The coloured part being in the middle is because of the lod texture being the road texture tiled 4 times by default. Making it just the road texture once puts the colour to the side and makes the issue less noticeable, as the stone part of the textures are mostly the same (road01sp is a lighter colour though). So, I can live with it, but it would be nice to know how to make DynDOLOD acknowledge these road changes.

[sheson]

1 hour ago, Benna96 said:

The "sides" I'm talking about are included in the texture, no mesh changes, just textures. In vanilla, roads use road01.dds, road01fallforest01.dds, or road01reach01.dds. The mod adds in roads using road01ea.dds, road01sp.dds, and road01wh.dds, by attaching alternate textures in an esp file. TexGen deals fine with all the textures after I added a txt file to generate lod for the new textures as well. The problem is, any road using road01ealod.dds, road01sp.dds, or road01whlod.dds, DynDOLOD renders as using road01lod.dds.

Here's a screenshot. (And a higher quality version if needed). The lod, on the right, is using road01.dds, which has green in it. The actual road, on the left, is using road01wh.dds, which has... I guess it's more of a brown, in it. It seems to me like DynDOLOD is acting as if the road was never changed to another, all these roads were originally ones using road01.dds I think.

The coloured part being in the middle is because of the lod texture being the road texture tiled 4 times by default. Making it just the road texture once puts the colour to the side and makes the issue less noticeable, as the stone part of the textures are mostly the same (road01sp is a lighter colour though). So, I can live with it, but it would be nice to know how to make DynDOLOD acknowledge these road changes.

That mod would need customized or updated LOD models to use the custom LOD textures atm, because the way Skyrim engine works there is no automatic texture replacement for LOD textures as there is for full textures. LOD will simply use the LOD texture that is defined in the LOD model. There are some workarounds in DynDOLOD to address these things for vanilla texture replacements, but they required manually labor. This will be better addressed in future DynDOLOD versions where eventually this should be more automatic.

Use xLODGen to generate better terrain LOD meshes with protected cell borders.

[Benna96]

9 minutes ago, sheson said:

That mod would need customized or updated LOD models to use the custom LOD textures atm, because the way Skyrim engine works there is no automatic texture replacement for LOD textures as there is for full textures. LOD will simply use the LOD texture that is defined in the LOD model. There are some workarounds in DynDOLOD to address these things for vanilla texture replacements, but they required manually labor. This will be better addressed in future DynDOLOD versions where eventually this should be more automatic.

Use xLODGen to generate better terrain LOD meshes with protected cell borders.

So, the vanilla alternate textures work because they're hard-coded to, so to speak?

The way I'm reading this, I could make it work if I make them use their own models, and lod models, instead of the defaults, correct? I was thinking I might try that, but wanted to hear from you before I went ahead and tried.

Thank you.

[sheson]

13 minutes ago, Benna96 said:

So, the vanilla alternate textures work because they're hard-coded to, so to speak?

The way I'm reading this, I could make it work if I make them use their own models, and lod models, instead of the defaults, correct? I was thinking I might try that, but wanted to hear from you before I went ahead and tried.

Thank you.

Yes, vanilla textures are hardcoded via config files.

You can copy the existing LOD models to new unique file names. Then use a tool to mass update the textures on the BSShaderTextureSet to the new ones and then add the LOD models to the base records in xEdit or CK the old way.

In order for DynDOLOD to always use the defined LOD models from these base records (instead of the automatic filename matching which takes preference), add a file in Data\DynDOLOD\DynDOLOD_SSE_[pluginfilenameesp].INI (see DynDOLOD_Mod_Authors.html for the correct filename of the INI file) that contains
 [Skyrim Settings]
DefaultLOD=1

[Benna96]

Thanks Sheson, they're working now 🙂 I think I'll look into xLodGen too.

[Dreifels]

confusing ingame message v. 2.9.6

"DynDoLod cannot read file DynDoLod_none" ingame left up text line in window when I load save being in Vigilant/Coldharbour

can't find error log,

[sheson]

1 hour ago, Dreifels said:

confusing ingame message v. 2.9.6

"DynDoLod cannot read file DynDoLod_none" ingame left up text line in window when I load save being in Vigilant/Coldharbour

can't find error log,

FAQ: Game: DynDOLOD could not read DynDOLOD_Worlds / DynDOLOD can not read data for [worldspace name] from DynDOLOD_Worlds / DynDOLOD_Worlds does not belong to these DynDOLOD plugins / DynDOLOD can not read bunchofnumbers from DynDOLOD_[worldspace name] / DynDOLOD_[worldspace name] does not belong to these DynDOLOD plugins / DynDOLOD can not read index data from DynDOLOD_[worlspace name] / DynDOLOD can not find [worldspace name] in DynDOLOD_Worlds / DynDOLOD can not find master data in DynDOLOD_[worldspace name] 

A: Make sure SKSE and DynDOLOD DLL or PapyrusUtil are installed correctly, see DynDOLOD requires DynDOLOD.DLL/PapyrusUtil above. 

A: Make sure the *.[json|txt] data files in the SKSE subfolder of the DynDOLOD output and the DynDOLOD plugins are in sync from the same generation process. Check the DynDOLOD SkyUI MCM Information page in the game that all plugins and files have the same bunch of numbers. 

A: Make sure the *.[json|txt] data files in the SKSE subfolder of the DynDOLOD output are in the load order and can be read. In case DynDOLOD DLL is used, check the c:\Users\[username]\Documents\My Games\[Skyrim|Skyrim Special Edition|Skyrim VR]\SKSE\DynDOLOD.log for errors. 

The DynDOLOD generation log is saved to the ..\DynDOLOD\logs folder.

[Velezarius2]

Hello! I have been using DynDOLOD for a long time and everything has always been fine in the Skyrim SE game...
But when I started using 2.98, problems started.

 

DynDOLOD.log:

DynDOLOD Plugin 2.45.0 for Skyrim Script Extender 64 2.0.17 for Skyrim Special Edition 1.5.97.0
Reading file C:\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD_Data\DynDOLOD_worlds.txt
Reading file C:\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD_Data\DynDOLOD_Tamriel_objects.txt
Reading file C:\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD_Data\DynDOLOD_Tamriel.txt
GetIntArray: empty array for key 11612 in section index in file Tamriel

Edited December 23, 2021 by Velezarius2

[sheson]

8 hours ago, Velezarius2 said:

Hello! I have been using DynDOLOD for a long time and everything has always been fine in the Skyrim SE game...
But when I started using 2.98, problems started.

 

DynDOLOD.log:

DynDOLOD Plugin 2.45.0 for Skyrim Script Extender 64 2.0.17 for Skyrim Special Edition 1.5.97.0
Reading file C:\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD_Data\DynDOLOD_worlds.txt
Reading file C:\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD_Data\DynDOLOD_Tamriel_objects.txt
Reading file C:\Steam\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD_Data\DynDOLOD_Tamriel.txt
GetIntArray: empty array for key 11612 in section index in file Tamriel

This thread is for Skyrim/Enderal but it seems you you are using Skyrim Special Edition?

 

FAQ: DynDOLOD can not read data for [worldspace name] from DynDOLOD_Worlds 

A: Make sure SKSE and DynDOLOD DLL or PapyrusUtil are installed correctly, see DynDOLOD requires DynDOLOD.DLL/PapyrusUtil above. 

A: Make sure the *.[json|txt] data files in the SKSE subfolder of the DynDOLOD output and the DynDOLOD plugins are in sync from the same generation process. Check the DynDOLOD SkyUI MCM Information page in the game that all plugins and files have the same bunch of numbers. 

A: Make sure the *.[json|txt] data files in the SKSE subfolder of the DynDOLOD output are in the load order and can be read. In case DynDOLOD DLL is used, check the c:\Users\[username]\Documents\My Games\[Skyrim|Skyrim Special Edition|Skyrim VR]\SKSE\DynDOLOD.log for errors.

 

Make sure the DynDOLOD DLL scripts overwrite DynDOLOD Resources.

Does this happen with a new game?

[Velezarius2]

I apologize for not immediately answering your recommendations and questions. I have generated DynDOLOD many times for a new game, and for pure preservation, and with a library, and with just papyrus - there are always errors in  "DynDOLOD_Tamriel.json":

"Error: Parse error on line 2064:
...28017", "c28017"],    },    "intList": {        "
----------------------^
Expecting 'STRING', got '}' "

"Error: Parse error on line 1999:
...25457", "c25457"],    },    "intList": {        "
----------------------^
Expecting 'STRING', got '}' "

etc.

 

 

[sheson]

2 hours ago, Velezarius2 said:

I apologize for not immediately answering your recommendations and questions. I have generated DynDOLOD many times for a new game, and for pure preservation, and with a library, and with just papyrus - there are always errors in  "DynDOLOD_Tamriel.json":

"Error: Parse error on line 2064:
...28017", "c28017"],    },    "intList": {        "
----------------------^
Expecting 'STRING', got '}' "

"Error: Parse error on line 1999:
...25457", "c25457"],    },    "intList": {        "
----------------------^
Expecting 'STRING', got '}' "

etc.

 

 

Upload the complete json file that you believe has problems.

Upload the entire DynDOLOD log of the generation that you believe created the problematic json files.