Skip to main content
Home
DynDOLOD - Dynamic Distant Objects LOD
Finally I can see my house from here!
Support me on Ko-fi

Exceptions

Read the error message and check the log above the exception for additional hints. Check the list below for additional explanations for some exception messages.

Always use the the latest version of DynDOLOD/TexGen.

Follow the installation instructions and do not install tools or game into special Windows folders like Program Files, Game, Data or mod manager folders to avoid issues with files access etc.

Finalize the load order. Install mods, sort and resolve conflicts. Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean - ignore misinformation that cleaning any plugins is not needed or causes problems. The Batch Plugin Cleaner for Mod Organizer or the xEdit Cleaning Extension for Vortex help to automate some of that. Check the load order for errors with xEdit before generating LOD. Fix all errors. See this video for help (ignore the old cleaning instructions as that was already done).

If there are any kind of memory errors, make sure to use the x64 versions of the tools. Check FAQ answers for High memory usage.

Search the official DynDOLOD support forum for the message to find discussions about the same topic.

If the problem persists, post an error report with the log, debug log and bugreport.txt as explained to the official DynDOLOD support forum.

Access violation at address

Always use the latest version of DynDOLOD/TexGen as explained above.

This could be caused by invalid or corrupt assets.

This could be caused by invalid or corrupt plugins. Clean and error check the load order with xEdit.

This could be low or out of memory problems. Use the x64 version of the tools. Check memory usage in Windows Task Manager. Check FAQ answers for High memory usage.

This could be caused by the OS or antivir interfering with file access.

This can be a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

Assertion failure

Always use the latest version of DynDOLOD/TexGen as explained above.

If the assertion failure is a 100% repeatable, it might be cause by a broken plugin.

Clean and error check the load order with xEdit before generating LOD. Fix all errors. See this video for help.

If the assertion failure is not 100% repeatable or no error can be found in plugins, it could be a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

Duplicates not allowed

Always use the latest version of DynDOLOD/TexGen as explained above.

This is a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

Error reading grass [worldspace] [x,y]

There is a problem reading a grass cache *.CGID/*.GID file. It is probably corrupted.

Find the file in the ..\Data\Grass\ folder and delete it.

The filename is of the form [worldspace]X[x]Y[y].CGID with leading zeros to pad up to 3 digits.

Start the game, open console with ~ and type cow [worldspace] [x] [y] to load into the worldspace and cell so that No Grass In Objects generates the *.CGID file on-demand.

Start DynDOLOD to generate LOD, hopefully without errors this time.

Integer overflow

Always use the latest version of DynDOLOD/TexGen as explained above.

This is a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

Item not found

Always use the latest version of DynDOLOD/TexGen as explained above.

This is a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

List Index Out Of Bounds

Always use the latest version of DynDOLOD/TexGen as explained above.

This is a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

OpenGL: invalid operation

Always use the latest version of DynDOLOD/TexGen as explained above.

If this happens while using optional AMD drivers, try installing the latest recommended drivers instead of optional drivers. Do not install crapware shipping with drivers.

This can be also a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

Range check error

Always use the latest version of DynDOLOD/TexGen as explained above.

This is a bug with the tools encountering unexpected situations. Make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

The system cannot find the path specified

The OS, UAC, antivir or some other 3rd party crap ware is blocking write access to the mentioned destination path. Add an exception to whatever it is that is blocking access.

It is also possible another process or program is accessing the same folder or file and this is preventing write access. In case the closing of other programs does not help, a reboot typically clears such issues.

Remove old files from the destination/output path, which might prevent creating the new files because they are blocked by other programs.

Unknown grass data file format

There is a problem reading a grass cache *.CGID/*.GID file. It is most likely in the vanilla Skyrim LE format (Skyrim SE vanilla BSA ship with the Skyrim LE format, hence the vanilla grass cache files do not work).

Find the file in the ..\Data\Grass\ folder and delete it, or in case it is a vanilla *.GID file make sure it is being overwritten with a valid file.

The filename is of the form [worldspace]X[x]Y[y].CGID with leading zeros to pad up to 3 digits.

The mod Grass Cache Fixes comes with a BSA that overwrites the vanilla grass *.GID files which are typically not generated by grass cache generation, since they are in areas that have been removed from Skyrim.esm.