matashina

Thank you. I know it might seem obvious, but I just wanted to confirm for my smooth brain that there wasn't currently a path for grass LOD that didn't involve downgrading. So much gratitude for this set of tools.

Hi, it looks like the .NET Script Framework, which is a requirement for DynDOLOD grass LOD via No Grass in Objects, will not be receiving an update for AE. Is the right thing to do now as an end user who isn't interested in downgrading to continue to use DynDOLOD without grass? Thank you.

Hey, apologies, I know these smooth-brained questions are super annoying but I couldn't find an answer to this reading the docs. I have file conflicts between the latest version of DynDOLOD resources and a bunch of LOD meshes provided by other mods like Drengin's Blue Palace Terrace or the Spice of Life orc strongholds. The right thing to do is to let these mods win, right? The authors went to the trouble to provide LOD meshes so I should just use them? I know that but that applies just to textures, correct? Again, sorry, I know it's a stupid question, I just get pretty confused by all the moving parts. So grateful for these tools and the support in using them.

Yes, with 8. This is good to know, thank you. I'll try it out the next time I run DynDOLOD.

Yeah, I was unable to complete a run with a SuperDenseGrass-enabled grass cache. I made a new grass cache with that setting turned off and reran DynDOLOD. It completed in a normal amount of time and none of those "pos x outside cell y center z" messages showed up in the logs.

You know what, I've had it running for like 3 hours now, I'm going to see if this ever finishes for the sake of argument, and then if it ever finishes I'm going to see if the game even runs. In the very likely event that my PC literally melts first ima turn off SuperDenseGrass and see if that fixes it. Skyrim. It's a journey, not a destination. Also, sorry, one more question. I see that having a root node of a NIF that's a NiNode can be a problem, and from the docs, that seems to be the case when generating Dynamic LOD, which the docs defines as "an optional type of LOD by DynDOLOD for objects that change state based on quests like military tents, ships, animated objects like waterfalls or fires or glow LOD windows that react to weather/sunlight." Would grass count as Dynamic LOD then?

Yeah, I think the file thing was just windows defender not like believing that I actually wanted the rules I'd set to work until I'd restarted my computer or something. Sorry to make you reiterate. You're on to something with my grass cache files. I tried out SuperDenseGrass and really like the results in-game before running my LOD stuff, but now that I think about it, uh, yeah, that could do it with ballooning my DynDOLOD times. Is that setting not compatible? I just grepped through the DynDOLOD docs and searched this forum thread and I don't think anyone has mentioned SuperDenseGrass before, but I could be wrong...?

Hello, I'm trying to get LOD'd up again after wiping the entire hard drive I had SSE installed on. I have two questions: 1. The first time I ran TexGenx64, I was getting Can not copy resource textures\clutter\stockade\stockadewood01_n.dds to C:\Modding\DynDOLOD\TexGen_Output\DynDOLOD-temp\textures\clutter\stockade\stockadewood01snow_n.dds The system cannot find the path specified. The file in question was right there in my data folder, naturally, not even in a BSA. Yes, I know that this is because of firewall/antivirus stuff for most users! For me, though, turning off Windows Defender didn't seem to help like it did for others. What allowed me to finish the program was deactivating DynDOLOD Resources 3.0 from my load order before I ran TexGen. Here are logs for the successful run: TexGen_SSE_Debug_log TexGen_SSE_log. I can also try rerunning with the resources activated if that output would be helpful. Was I supposed to be running TexGen without the resources activated this whole time? If not, does the fact that I had to deactivate the resources to get the program to work evidence of something wrong that I should fix? 2. Having (maybe) run TexGenx64 to completion, I moved on to run DynDOLOD for the first time on this machine, and it's taking way way way longer than I'm used to, at least 4 or 5 hours where it used to complete in like 45 minutes. I went to bed last night with it running and when I got up this morning it was still running. I exited th eprogram because I was worried it was taking so long (probably shouldn't have done that). Here are all the DynDOLOD/Lodgen log from that run, hope it's okay I zipped them. Is it normal for it to take this long? The only thing I think I had different in my settings from my old setup on the same hardware is changing my tree rules to the ones recommended in the new Aspens Ablaze DynDOLOD add-on. Thank you as always and I hope to god I didn't miss any necessary logs. There currently is no bugreport.txt.