[LE] How likely would a Navmesh conflict cause a crash?

[Russia2012]

I am trying to think of what is causing crashes for me when i enter certain cells. I know in that in Skyrim navmesh basically tells npcs where they can go and what they can do there. I figure if there is a navmesh conflict it would more likely result in NPCS acting weird than crashing to desktop. I am also guessing that if there was a navmesh error that was causing crashes i would likely know about it quickly. Either the game would crash before I was able to load the game or i would always crash when I entered the cell that had the navmesh error.

So far the game loads fine and I am able to load saves. Perhaps my CTD problem is not with navmeshes.

[niston]

Can confirm, borked Navmesh can lead to CTD.

 

I've just fixed such issue in a mod I downloaded; There were places on the map that would insta-CTD when I went there with a companion or followed a provisioner there. Turns out the navmesh was corrupted. No CTD anymore in the area after I fix it.

 

Also, if Fo4 doesn't shut down on quit, but keeps lingering as a background process, I've found that most of the times, the cause is a cell w/ unfinalized navmesh.

 

I suspect it is the same situtation for Skyrim.

[RoyBatterian]

100% if a door link is removed.

[ciathyza]

If there are undeleted navmeshes that have been forgotten they will very likely (in my experience 100%) lead to a crash. Creating such navmeshes unintentionally is unfortunately very easy with the CK and fixing that issue is a bit tedious but after some practice it can be done rather easily.

[YouDoNotKnowMyName]

Yes, screwed up navmesh can and will lead to CTDs!

A while ago I started working on a little personal project, a small castle thing in the plains of Whiterun, and after working a few hours on it I wanted to go in the game to see how it looked.

I did a bit of the navmeshing already .... the game didn't like that!