Sack

Just tried it out - DynDOLOD started properly and everything worked smoothly in-game afterwards. Thanks for the fix!

Sorry, here is the right log file, DynDOLOD.log: https://pastebin.com/19PsUGFx Here is a screenshot of the MO2 folder structure as you requested. Everything seems to match what you're describing. As far as I can tell, all the folders are configured correctly. As mentioned earlier, using DynDOLOD DLL SE with the exact same setup works fine, as you can see here. The only difference between these two attempts is I swapped DynDOLOD DLL NG with DynDOLOD DLL SE, everything else is using the same settings across all applications. Thank you for your patience.

Apologies for posting in the wrong section. DynDOLOD DLL SE is not installed when this error happens. Nothing is overwriting DynDOLOD DLL NG according to MO2. To make sure, I just tried again on a clean MO2 profile with nothing installed other than DynDOLOD, and the result is still the same. You can see what that looks like here. Here are all the logs for this new, clean, install showing the same error: DynDOLOD_ENderalSE_log.txt https://pastebin.com/1BQ5wHnB DynDOLOD_EnderalSE_Debug_log.txt https://pastebin.com/cBf6v0ED Papyrus.0.log: https://pastebin.com/r30dkJcR

I am trying to generate LODs for modded Enderal SE from GOG. This is the standalone version of the game, based on older versions of Skyrim SE and SKSE. I installed the latest versions of DynDOLOD 3.0, DynDOLOD Resources SE 3 and DynDOLOD DLL NG for 1.5.x/1.6.x using MO2. When trying to launch DynDOLODx64 the tool fails to start with the following error. Error: DynDOLOD.DLL from DynDOLOD.DLL and Scripts not found! Dynamic LOD can not be generated. Verify correct installation of the DynDOLOD.DLL from DynDOLOD.DLL and Scripts. Here is the full log: https://pastebin.com/TTPNfERC Some other notes: I tried running the older PapyrusUtil + DynDOLOD DLL SE version and that works fine. The issue only happens with DynDOLOD DLL NG. DynDOLOD DLL NG works fine with the game itself (SKSE loads it correctly), only the LOD generation tool says it can't find the files. xLODGen and TexGen have no issues with the same setup and the same launch arguments in MO2.