[SOLVED] Can you explain this weird CTD?

[WhatRules]

When approaching Rorikstead from the south I'm getting a CTD everytime, but when I come from the north I don't. What could cause a CTD like this?

[Just Don't]

Do you use mods to remove certain effects (smoke, fog, dust) and DynDOLOD? Recently I was having very specific crashes when going into interior spaces and it was due to a mod removing some glow effects which DynDOLOD was flagging with "has distant LOD".

 

If that's not your case I'd try to brute force my way to isolate the issue (disabling mods and trying to replicate the crash until you can pinpoint the exact mod causing it).

[Tlam99]

It is the last mistcloud up to neck of world.

Very old bug. With dyndolod you spread it over whole tamriel.

Very bad, it is in the savegames.

 

 

 

 

[Grey Cloud]

11 hours ago, saltshade said:

When approaching Rorikstead from the south I'm getting a CTD everytime, but when I come from the north I don't. What could cause a CTD like this?

When you approach from the north can you walk past the spot where it crashes when you come the other way?

[WhatRules]

23 hours ago, dontknowdontcaredontask said:

Do you use mods to remove certain effects (smoke, fog, dust) and DynDOLOD? Recently I was having very specific crashes when going into interior spaces and it was due to a mod removing some glow effects which DynDOLOD was flagging with "has distant LOD".

 

If that's not your case I'd try to brute force my way to isolate the issue (disabling mods and trying to replicate the crash until you can pinpoint the exact mod causing it).

Yes I have DynDOLOD but the CTD remains even if I disable it. Might still be in the savegame as the person below you were suggesting.

[Just Don't]

22 minutes ago, saltshade said:

Yes I have DynDOLOD but the CTD remains even if I disable it. Might still be in the savegame as the person below you were suggesting.

I'm not aware of that mistcloud + DynDOLOD interaction. My crashes where at very specific locations and disabling the DynDOLOD esp stopped the crash entirely. In my case I had to pinpoint the mod providing the incompatible nif files and replace it. Seems like your issue is different. It could be a corrupted nif file, not sure if Crash Fixes has a crash log detailing the potential culprits. I used the crash log from Net Script Framework to spot the nif files in question (but that's a SE mod).

[Tlam99]

I could spot the cloud with Netscript, the I checked the net and found some posts with exactly the same issue.

Downloaded all files new from se, bug still there.

then I checked some clouds, and behind this hidden shag where dark brotherhood starts with a lake behind and some clouds, ctd.

Dyndolod off, then this ctd was gone, but the cloud southeast neck world still caused ctd.

strange thing, you need to look west on the path to ctd.

walking down and looking on the floor and not looking west allowed me to walk down.

But, I could not save at this postion, ctd on save.

there is a solution to proceed with the quest with tcl and porting to a specific position, I will ceck this and post a link.

 

So here the link.

just read complete, there is a solution to finish the quest

https://forums.uesp.net/viewtopic.php?f=40&t=39153

 

 

[WhatRules]

17 hours ago, Grey Cloud said:

When you approach from the north can you walk past the spot where it crashes when you come the other way?

Yep, but now all of a sudden I can enter from the south as well (without entering from the north first). The bug is gone. All I did before that was to change some settings in SL Aroused. I had boosted some values to max because I wanted more aroused actors, but realized it was too much. I don't know if that could have caused the CTD, but I'm also using TDF aroused rape and SL Survival and that could have made a lot of actors target the player at the same time, which could have become to much for poor little papyrus.

 

Or maybe there was a randomly generated NPC from Travellers of Skyrim or Populated towns that had a bad mesh and this time it wasn't spawned. Either way, I don't feel the need to try to replicate a bug that I have solved.

[WhatRules]

4 hours ago, dontknowdontcaredontask said:

I'm not aware of that mistcloud + DynDOLOD interaction. My crashes where at very specific locations and disabling the DynDOLOD esp stopped the crash entirely. In my case I had to pinpoint the mod providing the incompatible nif files and replace it. Seems like your issue is different. It could be a corrupted nif file, not sure if Crash Fixes has a crash log detailing the potential culprits. I used the crash log from Net Script Framework to spot the nif files in question (but that's a SE mod).

I'm actually playing SE, but posted here by mistake, and after so many replies I can't say I'm sorry about it. I'm using Bug Fixes SEE, which has a folder called NetScriptFramework, but there is no log in it.

[Just Don't]

10 hours ago, saltshade said:

I'm actually playing SE, but posted here by mistake, and after so many replies I can't say I'm sorry about it. I'm using Bug Fixes SEE, which has a folder called NetScriptFramework, but there is no log in it.

Net Script Framework is a different mod. I have both Bug Fixes SSE and Net Script, the files for the later are:

Spoiler

 

And you need to enable logging in order to get the crash logs. To do so you need to edit the NetScriptFramework.config.txt file in the following lines:

Debug.CrashLog.Enabled = 1                                                      <- 1 for enabled, I think it comes disabled by default.

Debug.CrashLog.Path = "Data\NetScriptFramework\Crash"      <-  the default file path for the crash logs, that's where the files will go (if you're using MO these will be in "Overwrite\NetScriptFramework\Crash" instead)

 

 

I see the crash is gone, but I'd still be on the look for other possible instances and perhaps getting a proper crash log might help to solve things for good in the future.