Question and/or request for a new addition for aid to Mod Authors

[Logdas]

Currently they can specify that they want it to ignore world spaces, is that ignore that world space generally irrespective of plugin. However, if it isn't irrespective of plugin then great mod authors can use this to ignore world spaces for their plugins. However, if it is then that can be a problem as others that need or use it won't get it generated for them.

It can be corrected by enabling the specification options for something like the following: -

SkipPluginLODGen=<pluginfilename>.<extension>

or

SkipPluginLODGen=1 (with an alternate setting of 0)

Is this correct and/or does this exist currently please?

Edited November 21, 2022 by Logdas

[sheson]

21 minutes ago, Logdas said:

Currently they can specify that they want it to ignore world spaces, is that ignore that world space generally irrespective of plugin. However, if it isn't irrespective of plugin then great mod authors can use this to ignore world spaces for their plugins. However, if it is then that can be a problem as others that need or use it won't get it generated for them.

It can be corrected by enabling the specification options for something like the following: -

SkipPluginLODGen=<pluginfilename>.<extension>

or

SkipPluginLODGen=1 (with an alternate setting of 0)

Is this correct and/or does this exist currently please?

The setting to ignore entire worldspaces for LOD generation is set via a config file in the DynDOLOD installation only.

The plugin specific config setting to tell DynDOLOD to ignore references a plugin adds to a worldspace for that plugin and worldspace only and is generally intended for the city child worldspaces only. https://dyndolod.info/Mod-Authors#How-to-ignore-all-references-of-a-child-worldspace-for-copying-to-parent-worldspace-and-LOD

If there is an actual issue or problem, then it should be reported/discussed first, especially with DynDOLOD 3 Alpha.

https://dyndolod.info/Mod-Authors
Whenever coming across a problem and the initial reaction is to disable something - which is only a troubleshooting step - or to make elaborate workarounds to get something to work, it could mean the way LOD generation and DynDOLOD in particular works is not fully understood or that there is a bug or an unexpected situation that is not yet addressed - either in 3rd party mods or the tools or whatever else. Remember, DynDOLOD is a patcher to automatically generate a LOD patch. The LOD patch it generates is not supposed to require patching itself.