Robaa

I agree, that's why I was so confused But I finally found the issue, and - as expected - it was my own fault. The ENB preset I used required an older version of ENBhost than I was using. Changing that solved everything... It's probably a miracle that it worked before... Sheson, thanks for replying to my ramblings anyway, and keep up the great work!

Compatibility between an ENB preset and the result from the use of DynDOLOD. I did some more testing with other ENB presets, and I think I found the main cause of the CTD. My two test cases (VandB ENB Nature and Natural Lighting and Atmospherics) both use _mist_anchors.xml, which provides a list of worldspace coordinates, probably to place some special effects there (honestly I can only guess). Could it be thinkable that this conflicts with generated LODs? Edit1: To be precise, my testcase: having ENB but no *.xml with DynDOLOD and related mods enabled = no CTD, having ENB with *.xml and DynDOLOD enabled = CTD. And as I explained before, the curious case: if I have a working load order, with an ENB that uses the *.xml, and then run DynDOLOD, it CTDs afterwards. If I then remove all DynDOLOD content in MO, it still CTDs, unless I remove the *.xml - as I just found out. Edit2: For Natural Lighting and Atmospherics there are two *.xml files (_mist_anchors.xml and volumetric_mist_anchors.xml) but only the presence of _mist_anchors.xml causes a CTD. Not sure how that helps, but it's an observation :-)

Thank you Sheson for the quick reply! The Memory Blocks log is a nice addition for problem analysis :-) There was no memory problem, nor a conflicting nif. Safety-load was not in use, and ExpandSystemMemoryX64 was already false. The problem only disappears when I completely remove the ENB preset I use (VandB ENB Nature). If I only set UsePatchSpeedhackWithoutGraphics=true while keeping the files in enbseries intact still gives CTDs. Very curious... Switching to a different ENB (e.g. TAZ Visual Overhaul) gives no problems whatsover. So in the end... a compatibility issue with an ENB? Have you heard that before?

I'm very confused about my current attempts to use DynDOLOD, and I hope anybody has a clue of what is going on. First of all, I think I have a pretty good understanding of how to use MO, TES5Edit and so on, and I have all the latest versions of all mods and tools. So here's the thing. I've wanted to add Enhanced Landscapes + DynDOLOD to my current load order, for a new playthrough. I start up a game (Alternate Start) prior to installing the new stuff and everything seems to work fine. Then I follow the installation instructions for EL+DynDOLOD - or at least I think I do. After some time I get roughly 1,8 GB of DynDOLOD output, which I load into MO. I fire up the game and the starting dungeon still works perfectly. DynDOLOD gets loaded and appears in the MCM, but when I start to load an exterior location the game always CTDs after a few seconds of loading screen (I've tried different starting options and some COC's). Now initially I thought, okay, I have probably done something wrong with the LOD generation. So I uncheck all new mods (the billboards, Papyrus Utils, DynDOLOD, Enhanced Landscapes and the DynDOLOD output) to re-check that my initial load order was working correctly. But to my surprise, now even without any DynDOLOD stuff loaded (according to MO at least), I get CTDs as soon as I want to load an exterior location... What is going on? What changed? Isn't the whole purpose of MO to be able to quickly revert to a previous/different load order without anything left behind? And why doesn't that work in this case? ... any clues?