Modslave

Okay well this is all far more arcane than I've ever had to deal with with this system, I didn't just download a collection yesterday and have no idea what I'm doing I've been using Dyndolod with these resources now for several years. While I appreciate you taking the time to answer me you're not really telling me anything you're just telling me something that used to work doesn't work like it did literally 2 days ago and to RTFM. So I guess I'll just uninstall everything and start over cause this is getting me no where. EDIT to add: I just tried a Dyndolod session backing down Vedogoit Trees from 10.1 to 7.5 and got similar long period LODGen and high file sizes under Alpha 169. I have now backed down Dyndolod itself to Alpha 167 which was the last working version I had that generated outputs in about 20 minutes and am trying a new output now, will report back once I see what the results are.

Hrrrm well this is all very curious because the tree and grass models I'm using are the same ones I've been using since 2022. There was an update for them recently which I did update to, but they've never done this before....the passthru lods there seem to be being generated as a reference object from nifs but with much larger file sizes because Veydogolt is no where near that size for the passthru lods's in its own files. The only level32 considerations are for ACMOS. Billboard 6 for Tree and Level0 for /

Apologies for the delay. I'd already started a fresh texgen/dyndolod output after trying to eliminate potential issues and even downgrading the Dyndolod script package to the last version and noticed the log requirements after that. I just had to sit through a 2 hour Dyndolod output to ensure I have the logs required. One hour and 44 minutes of that literally being generating the Tamriel LODGen. Here are the relevant logs I believe. https://drive.google.com/file/d/1j2puHpv6JfE2sszQkgj_TQQXpOqbWeRj/view?usp=drive_link The debug log alone is 185mb something is very not right here. The largest asset folder in the output is the \DynDOLOD_Output\Meshes\Terrain\Tamriel\Objects folder, which is coming in at a whopping 27.6 GB uncompressed. Here is the Tamriel ModelsUsed. https://pastebin.com/Sa5REP8n The strange part of this is I haven't added anything that should be doing this, I've actually been removing things that add objects. And its not helping. My Texgen output.....by comparison, is literally less than 130 MB.

So, sorry to bring this here but I'm kind of not clear on what's happened here and its very concerning. I recently updated Dyndolod and its resources to 3.0 Alpha 169 and over the last two days had some very concerning lodgen sessions with it. Prior Dyndolod sessions would take me around 13 to 20 minutes generating a file on the average of about 2.5gb in total compressed size. But yesterdays session generated a compressed Dyndolod Output of 11.2 GB in size and it took about an hour and a half. It was mostly fine in the general Tamriel worldspace and then I got near Whiterun and the giant fight at the farm and it was such a simulation slide show that even Aela was saying her lines well after they appeared on my screen. I have an insanely high spec PC running a 3080 Ti, 64GB of RAM on a 4.5ghz clocked I7-9700 running at 1440p on a Nvidia G-Sync monitor and surprisingly it all held together and eventually settled down enough for me to be able to walk again but it was really awful so something was obviously wrong cause normally I can run Skyrim with another game or app in the background without a problem. So I dug into my modlist and removed a few texture and mesh addon mods, specifically Traverse the Uvenwald and Wigfrids Trees (both mods I've had in my load order in the previous 2.5 GB outputs and have been in my mod list for months) and cut some base object swapper mods for farmhouses as well. Leaving my prior install shorter on details. And I just ran Dyndolod again and it took another hour and a half and this time the compressed Output file is literally 19.2 GB compressed and 39.4 GB uncompressed which is quite literally 3 times the size of the entire game unmodded. Something is dreadfully wrong here and I can't figure out what. The only changes I've made should have reduced the total mesh and texture load, not increased it, and the only custom rules I'm setting in the expert level config are the ACMOS default billboard setttings for tree and /, everything else is just default run on High as I've always done.