lucid

I could use some help figuring out where I've gone wrong with this one. To start, I had an old version of DnyDOLOD installed, and intially was just going to update it to the more current version. My save at the time was pretty new so I decided to just uninstall the old DynDOLOD and start fresh all around. This is probably where I done goofed. I have been at this for hours and I give up T3T. I uninstalled and deleted everything as per the instructions from the Official Forum. I have all of the offsite requirements for DynDOLOD. I downloaded the standalone zip file and created a folder for it in my modding folder for Skyrim--not in a program file (x) or anything like that, it's in a separate gaming folder on my (C:) drive. I have the resources mod, and the dll NG and scripts mod. I made my executables for TexGen and DynDOLOD through MO2. After running TexGen I made sure the filepath for the textures for DynDOLOD were pulling from the .ini output file for TexGen--I saw this in another forum somewhere where someone had a similar issue to me and figured it was worth checking. The TexGen output was made into a mod, and enabled. Trying to run DynDOLOD is where the issues happen. It's just a wall of error messages, and it gets stuck at different intervals and not the same instance. I don't know if it's either DynDOLOD directly, or something I'm missing regarding it. It's like it isn't able to find the textures/meshes I've gathered with running TexGen. I have the pastebins for what I think is needed below. If I'm missing something I'm so sorry! I've never posted to a troubleshooting forum before, so I hope I'm being thorough. Please tell me what I've done wrong? Thank you for any help! dynDOLOD bugreport.txt: https://pastebin.com/5xnNWVvs dynDOLOD most recent session log: https://pastebin.com/E9BCSjKp - I know that this isn't the preferred way to link this file, but the actual .txt is too big for pastebin, and all of the alternatives I tried don't seem to be working for various reasons. This is just a copy and paste of the session logs from the executable window.