totengraeber

Hey, i was not asking something specific, just wanted to post my experience and of course i got your point with the different presets. But i have a question now. :) I had 6 mods (no one has anything to do with lod or something like that) merged within the batched patch. I checked them via TES5Edit and no errors were found in them. Picture. Wrye Bash is the last version i could download. So i guess it's up to date. As i mentioned above running Dyndolod (advanced settings) with the bashed patch with merged mods was not working and running it with the bashed patch without the merged mods was also not working. Both times i got the same error message. Only with a deactivated bashed patch it worked. The message contained "from Skyrim.esm into DynDOLOD.esp Assertion failure" but the problem seemed to be the activated bashed patch somehow. The faq hints that a bashed patch could be a problem but it's not stating that a bashed patch should be always disabled. So should it be always disabled when running Dyndolod or doesn't it matter and if it's the last then i don't understand why in my case the bashed patch caused the problem.

Hi. First time dyndolod (wannabe) user here. I had a similar message. The end of the message was Well, when i used the normal settings of dyndolod the process was starting without any error messages. I had a bashed patch with merged .esps and that was not a problem. When i changed to the advanced settings the above error msg occured right after the start and what i didn't understand was the "from Skyrim.esm into DynDOLOD.esp Assertion failure" and how can a bashed patch or merged esps be the problem. The Problem still occured after recreating a bashed patch without merged .esps. Only unchecking the bashed patch resolved the issue. So i had the experience if i used the normal settings all was working even with a bashed patch and merged .esps but the advanced version was only working with a deactivated bashed patch.