Can't Start In Vault 101

[SnapDragon1916]

So I am running on Windows 8.1

I have Mod Organizer 1.2.14

My install log is an attachment

My load order is very simple. It is just all of the required esms in the order that is stated on here, I've checked that many times, and then the 4 Project Nevada esms and then the Project Nevada TTW patch that is on here. That's it.

Now what is happening is that I go to start a new game and it goes to the NV intro movie. Then I hit escape and it goes to that normal NV loading screen, the one with the spinning roulette thing. Then it starts the FO3 intro movie and so I hit escape again and I start in Doc Mitchell's house. I have also tried going through both intros and not hitting escape. Same result. I did the three ini changes to both of the NV inis, the ones stated on the FAQ page, to deal with the starting in the wrong place problem and it didn't change anything.

[paragonskeep]

Step 2

You need to make an edit to your .INI files so that you start the game properly.  This is normally done by the .fomod when it is installed but sometimes for some reason a manual edit is necessary:

• 
  The files you're looking for are C:\Users\YourName\Documents\My Games\FalloutNV\Fallout.iniand C:\Users\YourName\Documents\My Games\FalloutNV\FalloutPrefs.ini


• 
  You may also want to make the changes in FalloutDefault.ini in the game folder as well, if you use the normal game launcher for some reason.  Using that launcher overwrites Fallout.ini with the values in FalloutDefault.ini every time it's run. 


• 
  Make these changes:
  
  
  
  • 
    SCharGenQuest = 001FFFF8
  
  
  • 
    sIntroMovie = (yes this one is blank on purpose, it needs to be blank)
  
  
  • 
    bLoadFaceGenHeadEGTFiles = 1
  
  
  • 
     
  
  
  
  

[SnapDragon1916]

Se that's the thing, I've already done those fixes to all three of the NV .INI files. Still getting both movies and Doc Mitchell's house.

[RoyBatty]

I have Mod Organizer 1.2.14

use at least 1.2.18

Turn off BSA management too.

[SnapDragon1916]

Wow so apparently it's pretty clear I haven't played new vegas in quite a while. I didn't realize my MO was so outdated for it. But that solved it. I must have checked those .INI files 15 times and I just didn't understand what was wrong. Thanks man

[RoyBatty]

You're welcome.