Jump to content


Photo

CTD issue with DynDOLOD active


  • Please log in to reply
4 replies to this topic

#1 TheOnceler

TheOnceler

    Prisoner

  • Members
  • 14 posts

Posted 07 August 2018 - 05:50 PM

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.


  • 0

#2 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,311 posts

Posted 08 August 2018 - 01:38 AM

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.


But why stop when you are so close? Only a few potential records left to eliminate. I don't get what you expect anyone else to do or suggest if you are that close to finish the trouble shooting?

Make sure that removing base records does not result in "can not resolve errors".

No log was posted. So I assume generation is free of messages about Root NiNodes, deleted references and missing models.

Edited by sheson, 08 August 2018 - 01:44 AM.

  • 0

#3 TheOnceler

TheOnceler

    Prisoner

  • Members
  • 14 posts

Posted 08 August 2018 - 01:52 PM

I think I've solved the problem. It's in my Farmhouse Chimneys Merge. I forgot I removed two of the towns required for the full merged patch available with the mod, so I merged them myself. Obviously something didn't work quite right. I'll test it out tonight and let you know.


  • 0

#4 TheOnceler

TheOnceler

    Prisoner

  • Members
  • 14 posts

Posted 09 August 2018 - 02:08 AM

Yes, that fixed it. Looks like I'm all set. Thanks!


  • 0

#5 sheson

sheson

    Dragon King

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,311 posts

Posted 09 August 2018 - 05:17 AM

Great that you found out the problem and thanks for letting us know.


  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users