HELP

Post by **Discord.Whooves** » Sat Jun 07, 2014 10:09 pm

excuse me i am using nexus mod manager beta 0.49.8 my install log system specs and current load order is attached and the fallout 3 version i'm using is steam downloaded game of the year edition and what it's doing is anytime i have all the fallout 3 esm files checked it crashes and i have no start menu however when the fallout 3 esm files are unchecked it works perfectly as for what i have tried so far i have tried everything the faq says to do except for manual setup if any one can help me it'd be most appreciated i should also add that even when i uncheck all the dlc for fallout 3 and keep just fallout 3 and TTW esms' it still doesn't work

Post by **thermador** » Sat Jun 07, 2014 10:23 pm

You can't have TaleOfTwoWastelands.esm checked if you don't have ALL of the fallout 3 .esm files checked (Fallout3.esm and all of the expansions). Note the highlighted text below, from the FAQ.

http://taleoftwowastelands.com/content/faq#crashes

If your menu worked before you installed TTW, and now it doesn't, and you haven't done anything else, it is most likely caused by TTW. A third-party program used by the installer, BSAOpt, tends to create corrupt .bsa files on some computers, for some unlucky users, and there's not much we can do about it. Fixing it is pretty easy though.

Check your load order and make sure it matches what is shown on the Download Page.

Disable TaleOfTwoWastelands.esm in your mod manager. Run the game. See if you get a menu.

If not, leave that ESM file disabled, and work your way up the load order (that is, disable Zeta.esm in your mod manager as well). Run the game. See if you get a menu.

Repeat this process until you get a menu. (example: you get a menu after you disabled ThePitt.esm)

Then you need to re-run the TTW installer, using the same directories as before, and the installer will ask you if you want to rebuild the .bsa files. Say no to each box, until you get to the .bsa files for the mod that was causing a problem (example: ThePitt - Main.bsa and ThePitt - Sounds.bsa). These are the ones that you want to rebuild.

Once the installer rebuilds the .bsa files that you need, copy them to your FNV data folder, overwriting the old ones (if you didn't choose your FNV folder as the install location already).

Run the game and see if you get a menu. If not, go back to step one and run through this process again.

Post by **JaxFirehart** » Sat Jun 07, 2014 11:36 pm

We released a new version recently, make sure you are using the newest version 2.6.3. Your installer didn't finish, so download and run 2.6.3 and upload the new install log and we can go from there.

Post by **Discord.Whooves** » Sun Jun 08, 2014 1:03 am

my updated install log is attached

Post by **JaxFirehart** » Sun Jun 08, 2014 1:06 am

OK your install log is clean. Install the newly generated FOMOD into FNV like you normally would. Try again and we will see what we can do.

Post by **Discord.Whooves** » Sun Jun 08, 2014 2:01 am

still no dice

Post by **JaxFirehart** » Sun Jun 08, 2014 2:06 am

OK. Do what Thermador said near the top of the thread. Let us know when you narrow it down to a certain ESM that is causing the no menu crash.

Post by **Discord.Whooves** » Sun Jun 08, 2014 2:11 am

only time it works is when i disable all fallout 3 esms'

Post by **Discord.Whooves** » Sun Jun 08, 2014 2:18 am

plus ttw