Difference between revisions of "Causes of CTDs"

358 bytes added ,  16:53, 18 March 2015
imported>Grigoriprime
(added exterior navmesh errors as potential cause of CTD (FO3 and NV))
imported>Grigoriprime
 
Line 115: Line 115:
==Worldspace Navmeshes==
==Worldspace Navmeshes==
Having uncaught errors in a navmesh that is in an exterior location can cause CTD on load of any save. This effect can be delayed by up to nearly a minute in some cases. It is also possible for this to happen if you manipulated an error free navmesh and forgot to finalize it.
Having uncaught errors in a navmesh that is in an exterior location can cause CTD on load of any save. This effect can be delayed by up to nearly a minute in some cases. It is also possible for this to happen if you manipulated an error free navmesh and forgot to finalize it.
This may be due to bad navmesh info and can sometimes be fixed by deleting the navmesh infos for your exteriors in FO3Edit and letting GECK re generate them. It is unknown if this creates other issues but it has been observed to resolve CTD on load without creating any additional GECK errors and does not require physically recreating your actual navmesh.
Anonymous user