CTD from having dyndolod.esp enabled in new save and old

[pentapox]

After probably a good few years of no issues with Dyndolod I've come across pretty much the only error I can't troubleshoot by myself. I'm on 1.5.97 with the best of both downgrade but I'm not sure how relevant that is.

For reference, I did the following:

1) Pruned my load order prior to the error as I had a lot of city mods that I didn't want anymore and installed several mods (Below are screenshots of the recently installed/updated mods in order of installation date)


(Note that City Trees is ONLY the farm plugins and trees for Solitude, and it doesn't affect Corpselight Farm in particular. Mods that aren't updated are purposely left not updated as I don't tend to go through fixing versionin errors.)

2) Ran a new Dyndolod output but forgot to disable Master Occlusion.esm as per in the mod page (BOS Master Occlusion)

3) made a new save once I was sure everything was as it was supposed to be and loaded in. I noticed the CTD first in the various cells around WhiterunStables, notably cell 0000967B (1, -6) aka Wilderness, (see the crash logs attached ending in -42 and -11)

4) I disabled occlusion.esp and master occlusion.esm for the tim e being and tried to continue onwards. I came across the CTD again later on a couple of times outside of Bleak Falls Barrow and later near Falkreath (Crashlogs ending in -55 and -25)

5) After clearing my texgen and dyndolod outputs and running the process again from the top with the latest versions of Dyndolod 3 and Dyndolod DLL NG and Dyndolod Resources SE I have experienced the same CTDs again following. This time I even made sure to disable Master Occlusion.esm and I tried both loading again from a save in an interior cell and exiting to the exterior (Which caused CTDs upon loading into the worldspace, specifically the mountains south of Falkreath) and faced the CTD AGAIN when exiting that same interior cell to an exterior from a fresh save aka using COC to enter the cell from the main menu and leaving through the main door. 

If I disable dyndolod.esp it doesn't CTD whatsoever, however disabling occlusion.esp does nothing. I'm at my wit's end about what could be causing this so I'm currently looking through mods and my load order for anything out of the ordinary. I looked for errors with xedit in the dyndolod plugins and found nothing, and I've also been checking the wilderness cells referenced in the netscriptframework logs. If you want me to get back to you with logs from CrashLogger let me know and I'll reproduce the bug with it installed. I usually use netscript as I'm just used to the format for personal usage as I don't normally need tech support.

https://ufile.io/f/tr8ak Linked here are the dyndolod log and dyndolod debug log, and there is no bugreport.txt. For whatever reason the debug log is 300mb

Crash_2024_7_30_22-14-42.txt Crash_2024_7_30_21-30-11.txt Crash_2024_7_31_5-24-25.txt Crash_2024_7_31_1-15-55.txt

Edited August 3 by pentapox

[pentapox]

After a second look, several tree textures are appearing in the texgen output folder and according to Sniff they're not the power of 2. From what I've been told these should be atlased so it shouldn't be an issue, but the files are still present in Texgen Output.

Here's the log from Sniff, which just tests for errors and gave me these results.

SniffLog.txt

[sheson]

20 hours ago, pentapox said:

Okay I know I said I'd do a new run and all, but I went digging and found several texture files in texgen output that have resolutions that aren't to the power of two and I'm being told that this might be the problem, however the files go back to Dyndolod Resources SE and are several different trees that appear to be in the SBT folder. Is this possibly the problem? I don'/t even think I use Simply Bigger Trees.

Textures generated by TexGen are obviously not causing CTD. They are multiple of 4 and typically not used directly but for atlas texture generation.

If problematic textures are used by anything (potentially) LOD related, they are typically reported in the DynDOLOD log.

A texture causing a crash is usually very obvious in the crash log. Typically the textures filename is mentioned, at the least the BSLightingShaderProperty and BSShaderTextureSet NIF blocks. In case the NIF/tetxure is used by a reference, the form ID of the reference and base record.

[pentapox]

Having done some testing I've ruled out DynDOLOD as the culprit, it appears to have just been a lot of coincidences. I've got dozens of crashlogs now from the load order with no dyndolod or xlodgen files whatsoever enabled. Thank you so much for your patience in helping me nonetheleess, I've still got all the files cleaned and I think that'll make for better DynDOLOD outputs in the future.

Wish me luck figuring the rest of this out! Feel free to close the thread or what have you.