The official DynDOLOD support forum is the primary address to turn to for any question regarding issues or compatibility with any mods or other plugins. It should be preferred over any other resource where only second hand knowledge is available at best.
Use the Latest Versions
Always use the latest DynDOLOD Standalone and DynDOLOD Resources version. Bugs and other problems may already be fixed or addressed.
The official DynDOLOD support forum contains many years worth of information and discussion. Chances are high that a question or a problem has been discussed before.
For example, search for the mod or plugin name to find discussion about a particular mod.
For example, use parts of the log messages or error message to search for posts containing the same messages. Remove the individual information, for example in case the message contains a path to a file, only keep the filename.
Copy and Paste Text
Copy and paste text instead of making screenshots of text. Text can be indexed and searched so posts can be found more easily.
If the option Copy this message to clipboard is available on a message prompt, use it to copy and paste the text.
- ..\DynDOLOD\bugreport.txt - if it exists
- ..\DynDOLOD\Logs\[DynDOLOD|TexGen]_[GAME MODE]_log.txt - truncate large log files to the entire last meaningful generation, starting with the line [DynDOLOD|TexGen] ... starting session
- ..\DynDOLOD\Logs\[DynDOLOD|TexGen]_[GAME MODE]_Debug_log.txt
If the issue involves LODGen upload or paste:
If there is no LODGen log or it does not contain a useful error message, start DynDOLOD in expert mode, select the desired worldspace and click Execute LODGen. Bring the LODGen command prompt window to the front to see if it prints more details to the console. Copy and paste that text. If that does not give more detail, check the Windows Event Viewer for additional messages from the .NET Runtime.
Simply zipping the entire log folder and uploading it is fine, too.
A screenshot alone does not substitute describing the issue with text. "This" is not a problem description.
If the form ID points to a DynDOLOD plugin, load the plugin into xEdit and look up the reference. Take note of the Editor ID, which is typically of the format plugniname_formID for the source plugin and reference.
Note that tree LOD or object LOD does not have a form ID. To determine if something is LOD, toggle LOD on/off with tll in console. In that case, also walk close to an object, so its reference with the full model is loaded in order to gets its form ID.
Use the DynDOLOD SkyUI MCM You Are Here page to determine the cell coordinates.