SSE - CTD for Falskaar and Solstheim with Open Cities

[OregonPete]

Hi!

 

I use Open Cities in SSE so I'm creating the LODs using the two-step procedure described in the manual and the GamerPoets video. I'm getting CTDs for both Falskaar and Solstheim. To be more exact, as soon as I try to travel to Solstheim via the Northern Maiden, I get a CTD. Same thing with Falskaar: the instant I try to enter the Falskaar world, CTD. If I completely deactivate and remove DynDOLOD, both Solstheim and Falskaar work fine. Interestingly, I'm getting no issues with anything else. Even Beyond Skyrim - Bruma is working just fine with DynDOLOD. 

 

Do you need me to post the logs for both steps of the process, or is this already a known issue with Open Cities?

 

Thanks!

 

OregonPete

 

 

[sheson]

Why do you believe this has something to do with Open Cities?

 

Does it work when you generate completely without Open Cities ever?

[OregonPete]

Thanks, Sheson, for the timely response. And sorry, I didn't mean to imply that Open Cities is the culprit. I just wanted to let you know that the process is a bit different since I have OCS installed. So what's the best way to narrow this issue down?

[sheson]

First I would generate LOD in one session, just to verify that the two pass generation is not introducing any problems. For that test, it should be enough just to to select the two worldspaces that have problems to save time, as LOD and data in other worldspaces should to be the problem.

 

Then check this recent discussion I had with uncleseano how to narrow down such problems.

[OregonPete]

Hey Sheson!

 

I know it's been a while, but I finally found the time to look into this issue some more...and solved it! Long story short, it had nothing to do with Open Cities, but more with RTFM, or in this case R-AU-TFM (read - and UNDERSTAND - the f***ing manual)! LOL The problem was that I didn't realize DynDoLOD required the results from TexGen, so I didn't add the TexGen archive to MO until after I had run both tools. Kind of embarrassing, to be honest. Anyway, now that I have the steps and order of installation correct, everything is working just fine, and my Skyrim looks absolutely amazing. Thanks!

 

OregonPete

[sheson]

The likely scenario is that the TexGen output replaces a non vanilla texture that causes CTD.

 

The TexGen output updates existing LOD textures from current full textures. If the TexGen output it is not installed vanilla or textures from other mods are used. Typically that is a visual problem only.