Possible to get a separate script for all plugins that have one or more unacceptable errors?

[fractalbase]

Hi Sheson,

Many including me have run into the issue where a plugin in a load order has at least one unacceptable error according to DynDOLOD, where DynDOLOD only gives you the option to exit.  If you get rid of the mod and try generating DynDOLOD again, DynDOLOD might run into yet another plugin with at least one unacceptable error, and the process continues.

Finding these errors with DynDOLOD is a pain because the user is notified of only the first such error, and that all involves the DynDOLOD LOD generation process.

I'm wondering if it is possible to write an xEdit script that looks for all such errors in a person's load order without the LOD generation overhead and allowing processing of all plugins so if there are multiple plugins with unacceptable errors, those all can be displayed from one running of the script?

[sheson]

On 7/27/2023 at 8:22 PM, fractalbase said:

Hi Sheson,

Many including me have run into the issue where a plugin in a load order has at least one unacceptable error according to DynDOLOD, where DynDOLOD only gives you the option to exit.  If you get rid of the mod and try generating DynDOLOD again, DynDOLOD might run into yet another plugin with at least one unacceptable error, and the process continues.

Finding these errors with DynDOLOD is a pain because the user is notified of only the first such error, and that all involves the DynDOLOD LOD generation process.

I'm wondering if it is possible to write an xEdit script that looks for all such errors in a person's load order without the LOD generation overhead and allowing processing of all plugins so if there are multiple plugins with unacceptable errors, those all can be displayed from one running of the script?

https://dyndolod.info/Generation-Instructions#Prerequisites
Finalize the load order. Install mods and their requirements. Sort and resolve conflicts. Clean and error check the load order with xEdit.

Usually errors that prevent successful LOD generation are errors reported by xEdit. The background loader of xEdit reports the duplicate, overriden or invalid object IDs etc. The xEdit error check reports the unresolved form ID errors. Having a stable/working load order or creating a patch plugin is pretty much impossible with these errors in the load order.

Most of the stop errors should have been discovered and fixed long before running DynDOLOD when following proper modding practice.
One would expect mods or plugins that have errors are fixed by mod authors or in case the mods are older/unmaintained and nobody made a fix yet they have newer alternatives.

You can "try/dry run" most of the checks quicker by selecting dynamic LOD only and not selecting anything else, in particular object LOD.

[fractalbase]

Hi sheson, I have a request.  I understand that plugins that dyndolod finds problems with shouldn't be used period.

however, finding those mods does take a long time, as DynDOLOD stops at the first found problematic plugin.

removing that mod and restarting DynDOLOD takes time.

my request: am xEdit script that processes an entire load order without stopping at each problematic plugin, so that a list of all problematic plugins can be acquired quickly and simply for the purpose of reporting such errors to mod authors, etc.

[sheson]

9 hours ago, fractalbase said:

Hi sheson, I have a request.  I understand that plugins that dyndolod finds problems with shouldn't be used period.

however, finding those mods does take a long time, as DynDOLOD stops at the first found problematic plugin.

removing that mod and restarting DynDOLOD takes time.

my request: am xEdit script that processes an entire load order without stopping at each problematic plugin, so that a list of all problematic plugins can be acquired quickly and simply for the purpose of reporting such errors to mod authors, etc.

https://dyndolod.info/Generation-Instructions#Prerequisites
Clean and error check the load order with xEdit.

https://dyndolod.info/Generation-Instructions#1-Generate-The-Required-LOD-Assets-with-TexGen
Make sure all mods, plugins and patches (that affect affect trees, grasses or any textures) are enabled and their overwrite order is sorted. ... In case of issues, solve the cause .. . Disabling plugins, mods, meshes or textures is a troubleshooting step and not a fix.

https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD
Finalize the load order as explained in the prerequisites above. Clean and error check the load order with xEdit. Make sure all mods, plugins and patches (that affect exterior cells and worldspaces and base records used by references in exterior cells) are enabled and their overwrite order is sorted. Ignore wrong 3rd party advice to temporarily disable plugins, mods, meshes or textures. .. In case of issues, solve the cause or use appropriate mesh mask rules or settings for desired results. Disabling plugins, mods, meshes or textures is a troubleshooting step and not a fix.

https://dyndolod.info/Messages#Warning-and-Error-Messages
Some errors stop the process with a dedicated pop-up window with further details and a "Click on this link for additional explanations and help for this message" link which directly opens a listed message below. Problems that stop the process are because of errors in the setup, mods, load order, unknown situations, bugs with the tools or third party issues (like OS, antivir, drivers, crapware, hardware etc.) that prevent a successful or safe LOD patch generation. As explained in the Generation Instructions, finalize the load order, install mods, sort and resolve conflicts. Clean and error check the load order with xEdit before generating LOD. Error checking the load order with xEdit will report many of the stop errors like unresolved Form ID in a single run. It also is possible to dry run most things a bit quicker by checking dynamic LOD only in the advanced mode.

Problems in plugins should be fixed or the mod should not ne used at all. Not fixing a problem that stopped the process pretty much guarantees there will be an issue in the game. If the problem is properly investigated to find out its severeness it can also be fixed in the process.

DynDOLOD is based on xEdit. Most of the errors that stop the process are from the xEdit background loader and the xEdit error check.