I've been struggling with a CTD issue for a few weeks now and I've exhausted all the troubleshooting advice I could find without a solution.
I have a large load order based loosely on Lexy's LOTD SSE build. The problem is, everytime I try to activate DynDOLOD, I get CTDs in Riverwood and multiple other locations (I've mostly been testing Riverwood).
Without DynDOLOD active, I was able to exit the caves at Helgen in the ASLAL vanilla start, travel to Riverwood and Whiterun and go in and out of locations there without issue. But with DynDOLOD active, I hit a consistent CTD just past the guardian stones (and along the road before the Riverwood bridge coming from the other direction). I also tried saving inside Gerdur's house and activating DynDOLOD there, but every time I exited I got the CTD.
Then I started testing. Without DynDOLOD, I could coc from the main menu to Whiterun, let all my mods load, then coc to Windhelm, Morthal, Nightgate, Blackreach, Dawnstar, Karthwasten, Markarth, Ivarstead, Darkwater, Falkreath, Helgen, RavenRock, and Winterhold without any CTDs. Then I tried the same thing with DynDOLOD active. I could get to Whiterun, but after that the first 5 locations I tried resulted in a CTD.
Also, without DynDOLOD I was able to enter godmode and flew over many of those trouble spots without incident. But with DynDOLOD, I could not get far in any direction before a CTD stopped me.
Following the troubleshooting advice in Docs, I turned on the logging but there were no nif references at all in my papyrus log and nothing obvious in my DynDOLOD logs either. My TexGen and DynDOLOD installs complete successfully every time (I've now tried versions 2.37, 2.41 and 2.43). I tried hiding the textures and meshes in the DynDOLOD output. Then I started slowly cutting out content from the esp and then the esm with xedit, but no amount of cutting made a difference. Eventually I eliminated all the worldspace cells entirely, leaving only the persistent lines with Minions, Firstborn, etc. Then I eliminated the Trees and Static sections. Still got the CTD. And that's where I decided I'd had enough and called it quits.
I have no idea why DynDOLOD is no longer working for me. It has worked fine in the past with previous builds. I simply can't discover where the problem lies, even after stripping out half my load order and then reducing the esp and esm to practically nothing. At this point, I'm resigned to using SSELODgen for object and tree lods, too, but I'm hoping someone here might have a suggestion. Has anyone seen a solution for an issue like this? I'm using Windows 10, MO2, and a 1080 Ti with 8gb vram.
Question
TheOnceler
I've been struggling with a CTD issue for a few weeks now and I've exhausted all the troubleshooting advice I could find without a solution.
I have a large load order based loosely on Lexy's LOTD SSE build. The problem is, everytime I try to activate DynDOLOD, I get CTDs in Riverwood and multiple other locations (I've mostly been testing Riverwood).
Without DynDOLOD active, I was able to exit the caves at Helgen in the ASLAL vanilla start, travel to Riverwood and Whiterun and go in and out of locations there without issue. But with DynDOLOD active, I hit a consistent CTD just past the guardian stones (and along the road before the Riverwood bridge coming from the other direction). I also tried saving inside Gerdur's house and activating DynDOLOD there, but every time I exited I got the CTD.
Then I started testing. Without DynDOLOD, I could coc from the main menu to Whiterun, let all my mods load, then coc to Windhelm, Morthal, Nightgate, Blackreach, Dawnstar, Karthwasten, Markarth, Ivarstead, Darkwater, Falkreath, Helgen, RavenRock, and Winterhold without any CTDs. Then I tried the same thing with DynDOLOD active. I could get to Whiterun, but after that the first 5 locations I tried resulted in a CTD.
Also, without DynDOLOD I was able to enter godmode and flew over many of those trouble spots without incident. But with DynDOLOD, I could not get far in any direction before a CTD stopped me.
Following the troubleshooting advice in Docs, I turned on the logging but there were no nif references at all in my papyrus log and nothing obvious in my DynDOLOD logs either. My TexGen and DynDOLOD installs complete successfully every time (I've now tried versions 2.37, 2.41 and 2.43). I tried hiding the textures and meshes in the DynDOLOD output. Then I started slowly cutting out content from the esp and then the esm with xedit, but no amount of cutting made a difference. Eventually I eliminated all the worldspace cells entirely, leaving only the persistent lines with Minions, Firstborn, etc. Then I eliminated the Trees and Static sections. Still got the CTD. And that's where I decided I'd had enough and called it quits.
I have no idea why DynDOLOD is no longer working for me. It has worked fine in the past with previous builds. I simply can't discover where the problem lies, even after stripping out half my load order and then reducing the esp and esm to practically nothing. At this point, I'm resigned to using SSELODgen for object and tree lods, too, but I'm hoping someone here might have a suggestion. Has anyone seen a solution for an issue like this? I'm using Windows 10, MO2, and a 1080 Ti with 8gb vram.
4 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now