Jump to content


Photo

Concerning the cleaning of DLC and their deleted navmeshes


  • Please log in to reply
3 replies to this topic

#1 Kappaccino

Kappaccino

    Watcher

  • Citizen
  • 8 posts

Posted 25 May 2019 - 02:57 PM

Removing the deleted navmeshes and cleaning the DLC ESMs is listed early on in the guide, and links to GamerPoet's playlist on YouTube. I noticed recently that his "Introduction" video has a pinned comment from him advising people to not follow these steps until after all the modding in the guide has been done, since mods that touch the deleted navmeshes could cause a CTD if they're cleaned prior to install. I'd like some advice on the matter, since I respect both Kelmych's and GamerPoet's opinions.


  • 0

#2 Kelmych

Kelmych

    Emperor

  • VIP-Supporter
  • PipPipPipPipPipPipPipPipPipPipPip
  • 3,903 posts

Posted 25 May 2019 - 09:57 PM

I hadn't heard this before; it could be correct. GamerPoet got his information about the deleted navmeshes from Roy Batty who is the expert on this aspect of Fallout 3.


  • 0

#3 Kappaccino

Kappaccino

    Watcher

  • Citizen
  • 8 posts

Posted 25 May 2019 - 10:27 PM

I hadn't heard this before; it could be correct. GamerPoet got his information about the deleted navmeshes from Roy Batty who is the expert on this aspect of Fallout 3.

I love Roy. If you could talk with him about the topic at hand, I would like to hear what he thinks. 


  • 0

#4 sattyre

sattyre

    Citizen

  • Citizen
  • 22 posts

Posted 01 May 2020 - 07:58 PM

is there any new info on this.  I am having a really difficult time pinning down the cause of ctds and freezing.  For the record, a friend sent me the two esms with the navmesh fixed, but uncleaned, from his own game, and I then cleaned all the DLC in sequence and then did the rest of the modlist.  I also unfortunately used Xedit version 4.0.3 to clean them and apparently that version of xedit created some kind of rendering issue with the FO3 DLCs.  That last info, i got directly from the XEdit discord.  I have upgraded to the still experimental 4.0.3b which doesn't have the issue.  This issue didn't exist in Xedit 4.0.2


  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users