Ashok0

Hi, Thanks for the quick reply! I fixed the most serious errors in xEdit and tried re-running TexGen and DynDOLOD 3.0 Alpha-88. Because I'm modding Skyrim VR for Enderal, I also removed all Worldspace and Cell data from my plugins to avoid getting Tamriel worldspace inside of Enderal. I permanently deleted Embers XD.esp as I wish to just use the mod's textures and meshes without the plugin. When I initially load up a campsite in Enderal VR with the Embers XD textures and meshes installed (no plugin used), Embers XD appears to be working just fine and More Informative Console shows "Model: Campfire01Burning.nif", "Base defined in: Skyrim.esm". https://ibb.co/cCBXGZH But after running DynDOLOD, the fires change and Embers XD no longer works. More Informative Console shows "Model: Campfire01Burning.nif", "Base defined in: DynDOLOD.esm". https://ibb.co/BTsqNmW From what I can tell, my problem seems to be that after running DynDOLOD, the campfires are using meshes from: \DynDOLOD Resources SE\Meshes\DynDOLOD\lod\clutter\campfire01burning_dyndolod_lod.nif instead of the desired... \Embers XD\meshes\clutter\woodfires\campfire01burning.nif In my MO2 load order, Embers XD has a higher priority than DynDOLOD Resources so I'm a bit confused why the Embers XD textures and meshes don't appear in game after running DynDOLOD? See logs here: https://ufile.io/f/8tk4b Kind regards, Ashok

Hi, I have a small issue when using DynDOLOD 3.0 Alpha 88 + DynDOLOD Resources 3.0 Alpha-24 with Enderal VR. Everything mostly works but I use Embers XD, and DynDOLOD seems to add logs to my Embers campfires. The standard campfires show up when I first load into a campsite and then once DynDOLOD is initialized, large logs seemingly load in as LODs. The problem goes away if I revert way back to Alpha 65. Is this normal behavior in Alpha 88? And if so, is there a way to force DynDOLOD to not alter the Embers XD campfires? I have attached my log files (DynDOLOD_ENDERALSE_log.txt & DynDOLOD_ENDERALSE_Debug_log.txt) below. Thanks! Campfires before DynDOLOD loads: https://ibb.co/GJs2Yxs Campfires after DynDOLOD loads: https://ibb.co/F4vqN0P https://ufile.io/f/wjsuj

Hi Sheson, I am having problems using the latest versions of DynDOLOD 3.0 with Enderal VR. I just updated to Alpha-49 and DynDOLOD 3.0 halts with the following error: "Record [REFR:00012FB4] in file SkyrimVR.esm is being overridden by record [NAVI:00012FB4] in file SkyrimVR.esm. These errors cause CTD and other serious issues and need to be fixed. Ignore wrong advice to temporarily disable plugins." I am assuming this happens because Enderal VR is repurposing the Tamriel worldspace record with MQP01Home, "Home, Sweet Home". If I downgrade to DynDOLOD 3.0 Alpha-44, DynDOLOD 3.0 works perfectly fine. Is there any solution to using Alpha-49 with Enderal VR? I have also attached logs below, thank you! DynDOLOD_TES5VR_Debug_log.txt: https://ufile.io/bmvlrob4 DynDOLOD_TES5VR_log.txt: https://ufile.io/vk0ly96l

Hi, I am using xLODGen Beta 84 and TexGen/DynDOLOD 3.0 with Enderal VR. I have always gone thru the following process without issue: 1. Run xLODGen with Perfect Terrain LOD (as temporary textures for xLODGen generation only) 2. Run TexGen 3. Run DynDOLOD 3.0 These steps have always worked flawlessly for me and I've had no issues with terrain/object/tree LOD. After updating to DynDOLOD Alpha 42, I receive the following error when running DynDOLOD 3.0: Incorrect terrain LOD for MQP01Home. See below for log files: DynDOLOD_ENDERALSE_log.txt: https://ufile.io/vpzxe8pr DynDOLOD_ENDERALSE_Debug_log.txt: https://ufile.io/1c0klc7l I was actually able fix this issue by simply re-running xLODGen and unticking the worldspace for MQP01Home "Home, Sweet Home" [WRLD:0000003C]. DynDOLOD runs fine now and terrain LODs look great! I believe I'm actually all set but was just wondering if the above fix is considered an optimal solution for using xLODGen + Perfect Terrain LOD with Enderal VR? Thanks!