Admiral30

I have decided to generate entire LOD (object/terrain/tree) using LODGEN and something went wrong. Screenshot of the issue (purple meshes): Log: https://pastebin.com/DAGuS7a3 Log reports missing meshes. The issue is those meshes do exist and are enabled in the mod manager. Is there something obvious that I'm missing? The ice mod that I'm using is Icy Mesh Remaster, but I don't know if it's related.

Even occlusion? That thing takes ages, I can do it, but I would want to avoid it.

Oh dear, of course I didn't look at the first page. Here are the logs and some screenshots: https://ufile.io/f/gp6k5

I have a problem with DynDOLOD refusing to start. I'm using up to date DynDOLOD with DynDOLOD Resources enabled (both during generation and for gameplay), DynDOLOD DLL Scripts 2.82.4 and DynDOLOD DLL 2.45 for Skyrim SE 1.5.97. I've did the same thing that I always do and it always works. Run texgen, throw output into MO2, enable it, run dyndolod, throw output into MO2, enable it, order plugins, and done, it works. But not this time. LOD is screwed up and DynDOLOD toggle is greyed out in MCM. Unfortunately I have no clue what it can be.

I will try to make some reasonable comparison, but I have to admit if it works for the 2nd time I will certainly have no strength for another run, so I will assume problem is solved for now. But I have a feeling it will crash.

Red - RAM Green - CPU Threads = 1, memory argument for dyndolod exe. Funny thing is no OOM exceptions this time, but it took way too many attempts to achieve this, so I wouldn't call this a win yet.

CPU is almost constantly 100%, memory 30-70%. I have 16GB, I was thinking about getting another 16, but not because of DynDOLOD.

I have only one output atm and it's 3.46 GB. I also have a backup of older output (the one with glitched waterfalls) and it's also 3.46 GB. There is also possibility that arguments are incorrectly set

I require explanation.

Keeping dyndolod output enabled again triggers out of memory errors. Unfortunately I'm forced to rollback to previous version for the time being.

I see. I have disabled it because DynDOLOD showed warning that output will be overriden (which technically I don't want, I just need separate occlusion.esp).

I have generated LOD with occlusion disabled, moved it to MO2 but didn't enable it, then used DynDOLOD again with only occlusion enabled (according to manual), and it works fine. No idea why it happens, it isn't even reaching more than 70% of RAM usage, and I had WAY heavier load order before and it worked fine on earlier versions. But in the end it works again, just one more step instead. Thanks for help, hopefully it will be accidentally fixed in alpha 74+.

I already did set occlusion threads and it changed nothing. Adding -memory command doesn't fix it either. I will try generating it in two steps, I have no idea how but I will figure it out. As I said before it worked fine before (alpha 70 or 71), so something is clearly wrong with alpha 73.

DynDOLOD semi-randomly fails to generate meshes with out of memory error (even though RAM usage is around 50%), and uses 100% of CPU (had to forcefully disable 4 cores for dyndolod process). I'm using newest alpha 73, it wasn't a thing on previous versions. I will upload logs as soon as DynDOLOD completes generating LOD that doesn't throws out of memory exception. https://ufile.io/f/9tasc At least a few meshes failed making output unusable. 2nd attempt with changed ini threads settings failed again

All waterfalls are flickering, so I imagine all references are "broken", but here is the example from video: Ok incorrect load order might be the problem here. For me resources are on the very top, I will move them a little lower to overwrite patches. You see I contacted water for enb because I suspected that his meshes are the reason why dyndolod generates incorrect lod. But at the same time I guess someone else would notice it too. I will try to update the lod now. If I won't reply again it means its fixed. Thanks for help again.