Jump to content
  • 0
Sign in to follow this  
wellden

Fixing deleted navmeshes from Pitt & BS

Question

Hi Kelmych - Just a note fwiw that I just had a discussion with @RoyBatty on discord (#troubleshooting TTW) last night and today about any procedures he recommended and this was his take :

1. deleting the navs can potentially break some mods, but he still recommends doing it as described only waiting until full modlist is in place so xEdit should update any ID's in the list

2. since he says xEdit can possibly flag the changed ID's as ITM's, he recommended NO autoclean to be used

 

Just wanted to share this info and hope it helps. Some folks were asking Michael (GP) and don't know if he got around to asking him or not...so I did

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

Since Roy is the expert on deleted navmeshes (and lots of other things), this will be put in the guide when it's updated. Thanks for the information.

Share this post


Link to post
Share on other sites
  • 0

Glad to help. I just fixed mine (been busy with other things) and the only mod updated from the list was DCInteriors_ComboEdition.esm that I saw. Also of note, since Sreetlights.esm is above BrokenSteel.esm, the "ID to replace w/original" in Michael's instruction list you linked will be "0400.*" instead of "0300.*" I just bet we could still clean the remaining DLC with the exception of Pitt and BS...but your call there ;)

Thank you for a wonderful guide all these years and for continued work on it.

Share this post


Link to post
Share on other sites
  • 0

I'm glad you find the guide useful. I periodically search through all the new and modified FO3 mods on Nexus, but there aren't usually very many that seem appropriate for inclusion in the guide so the the guide isn't updated often.

 

I have one question on your original comment about Roy's recommendations. Did you mean that Roy recommended not using Quick Autoclean? The current version of xEdit 4.00+ (e.g., 4.02)does Autoclean or Quick Autoclean; it no longer works the same as xEdit version 3 when cleaning.

Share this post


Link to post
Share on other sites
  • 0

Yes I should have clarified...sorry about that. He was referring to autoclean and I suppose cleaning those 2 DLC in general as xEdit could "possibly", he said, interpret the changed FormID's as ITM's (which the older cleaning method would too I imagine)...therefore he advised against cleaning at all. I know he doesn't recommend cleaning DLC in FNV either...although like you...I always have. I did not this time per his advice ...as you said, he knows a thing or two ;) When I cleaned the navs from the Pitt and BS, LOOT reported them as clean...go figure!

Oh and speaking of newer mods...this one by StewieAl of FNV fame adds the falloutcustom.ini (which combines fallout.ini and prefs.ini) into one ini that is read first at runtime...making ini edits so much easier to copy/paste among a slew of other useful commands if it is to your liking. You might have seen it already but thought I would share if you don't mind.


Edit...Yes "Quick Autoclean"!! Hate not being able to edit posts!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By se7enex
      Lucas Simms himself is missing his arms. I can see his gloves but his actual arms are invisible. I can't even begin to imagine what the fluff could be causing that. I did have issues with .32 and Mausers having big red exclamation marks but that's because it REQUIRES (listed in mod guide as optional) the individual weapon remakes. 

      Springvale Sewers, a AWOP location crashes consistently when I try to enter it. 

       
    • By Dennai
      Is there a way to make GaryBash work with MO in Fallout 3? I tried to use it as executable, but MO wouldn't recognized the Wrye launcher as such. It surprised me, because MO had no problem recognizing the Wrye Bash launcher for Oblivion, but I don't have the same luck with Wrye Flash. When I browse the Moppy folder to try to find the Binary, Wrye Bash Debug is the only application the MO can see.
    • By wolverine2710
      Originally BrainFever posted this in the Nexus MO forum. So that this discussion will not get buried on the nexus forums I created the question here and will respond to it here.
      MO works with Fallout3 and FONV (Fallout New Vegas). I have used it successfully with FONV. There are however a few mods which are bit more difficult to install. Mods like darnified UI, MCM, Unified Hud. These mods need to see the XXX_menu.xml files installed by other mods to work properly. The fundamental concept of MO (Mod Organizer) is mod isolation. In the current situation with MO when installing those kind of mods can't find those xml files. There are however workarounds for this. Those are described in the Nexus forum (search for fake or XML). It is also discussed here in this forum. An explanation how to use FOMM can be found here.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.