stein03

Your suggestion on Terrain LOD Redone worked. I disabled it, and DynDOLOD launched. Oddly, I have had it in my LO for at least a year and still generated LOD several times without conflict. For some reason, the Alpha 111 didnn't like it, or more likely, I managed to change my LO without understanding how. I certainly did not change any priority rules involving it. Thank you again for your help.

Yes, I believe you 100%, but that doesn't help troubleshoot. At least not for me. By the way, I am greatly appreciative of your work on this tool and tireless support of the community.

Indeed, they are generated for all worldspaces and are loading after all conflicts (just Beyond Reach and Wyrmstooth, presumeably pre-generated terrain textures. I do not have a bugreport.txt. Here are the other logs. DynDOLOD_SSE_log.txt DynDOLOD_SSE_Debug_log.txt

DynDOLOD_SSE_Debug_log.txt Does this work for the log? I'm sorry for being such a noob on this forum and its functions. The reason I mentioned xLODGen and terrain is because that is what the error message specifically mentions as a solution.

Francis - did this error go away after you ran xLODGen?

I am having this same issue. I have already re-run xLOD gen for terrain meshes and textures. Is there a way to troubleshoot exactly which mesh file is supposedly broken? I'm sorry, I think this was attached to the wrong thread. I have this same issue; newly updated to alpha 111 from alpha 73. I have already generated terrain meshes/textures with xLODgen as well as billboards with TexGen. Is there a way to debug the supposedly broken mesh?

I am having this same issue. What was your "misstep"?