Glanzer

Thank you! For now I just created a new JSON file with the updated formids and that worked. If you do create a dynamic JSON file be sure to give each of the 3 bounds in it a value of at least 300 due to the size of the firelog mesh. I'm using 400 but I like to get burnt early since it's such a big fire.

I noticed that the giant campfires no longer burn my character when using Fire Hurts NG. I traced the problem to the fact that the base object ID of the campfire was changed and replaced by an object that is now in the DynDOLOD.esm plugin (see attached screenshot). I then found the following rule in the DynDOLOD_SSE_embersxdesp.ini (yes I do use EmbersXD): [Skyrim LODGen] LODGen1=giantcampfire01,,,,Far Full,Replace,0 If I'm reading that correctly, it looks like the LOD is being used for the closeup model. I'm getting that from here where it says "Replace" means that when the cell is attached (when the character enters the cell?) the original reference is disabled and the LOD continues to be used. Am I reading that correctly? If so, why was that done? It breaks the giant campfires for the Fire Hurts mod.

I wanted to add a couple things to this discussion. If you use Engarde you can roll to put out the fire. Also I published some patches for Fire Hurts NG here.

Discussion topic: Markarth Murder Prevention by Glanzer Wiki Link Moves the attacker's spawn point further away from the victim, giving you more time to prevent a murder. No cells or worldspace records touched, just a single value change to one small record. Rationale for inclusion in STEP: Dyndolod users have less time to react due to the delayed screen load. Also, SSE seems to delay the reaction time compared to LE. Users of long modlists can have additional delays that prevent the PC from getting there in time.

I removed the dyndolod plugins and the problem persists. Looks like it's not a dyndolod problem, sorry for not doing more troubleshooting first.

Just upgraded to Dyndolod ver. 136 and the latest version of Dyndolod resources, and switched from Dyndolod DLL SE to Dyndolod DLL NG. Cleared out all previous files and reran everything using the same procedures I've used with no problems. Started a new game but I now see this around all campfires. I checked all the files linked off the Dyndolod summary and nothing appears unusual. Point me in the right direction, or I can upload the logs per your bug reporting procedures if need be. As always great thanks to you for your great support Sheson. https://i.imgur.com/K8RxZGl.png

YES the LODGen is now successful for the aaChanterelle2 worldspace. HAPPY DANCE!

I create the bashed patch first, then run xlodgen/dyndolod/occlusion, then run synthesis. I find that there are a few records that dyndolod uses from the bashed patch, so the plugin order ends up being bashed patch, dyndolod.esp, synthesis.esp, occlusion.esp, followed by map mod plugins. Your mileage may vary! Here's the remind I wrote for myself, but keep in mind this is based on the mods I have installed: PATCHING ORDER: 1. Disable map mods 2. Remove all dynamic patches (bashed patch, zpatch, synthesis, dyndolod) 3. Run blacksmith forge water xedit patcher, enable it 4. Run bashed patch, enable it 5. Run the "No Grass in Objects" grass generator from within MO2. Move the output file to the NGIO mod. 6. Then run SSELODGEN/Dyndolod/Occlusion, enable them. 7. Run zedit patches, enable them 8. Run synthesis patcher, enable it. 9. Run the standalone Experience Synthesis patcher 10. Rerun Nemesis and execute the vbs file for Engarde 11. Re-enable map mods

See https://dyndolod.info/Messages

Well it works fine when I uncheck grass. Why would it do that if it's something about trees? Anyway, I'm sure you'll find it.

fwiw I ran that nif through CAO with full optimization, but LODGen still crashed with the same error.

As I recall the memory usage was 8 GB max. I have 32 GB. I'll try it with the standard tree settings and see what happens.

Here you go: aaChanterelle2.zip

Running without the loose files and with the BSAs only didn't help, the same error happened. But after some more experimentation I narrowed the problem to the precached grass. Unchecking the Grass option in Dyndolod let's it complete without errors. (Yes I did run all NGIO precaching before starting the texgen/dyndolod process.) I notice that Vactrol (mod author) put a note about generating the grass for two of his worldspaces separately, so I'm going to start over and see if that makes a difference. Another user said he didn't do that and had no problems. In any case, let's consider this problem 'solved' for now because I'm taking this issue back to the mod and continuing the discussion/debugging there. If I find out anything of general interest that might help other users beyond that mod, I'll come back and post it here. Thanks so much for your help Sheson!

Ran the LODGen using LODGenx64.exe instead of LODGenx64Win.exe and it failed again. The logs all look the same, but the event log entry is slightly different: