Can't Start New Game - TTW 2.4a

Post by **morlund69** » Sat Dec 28, 2013 7:34 am

Win7 x64, Intel i3 2.1GHz, 4GB RAM (a toaster, yes, but a toaster that could run TTW 2.2)

Load Order:

FalloutNV.esm=1

DeadMoney.esm=1

HonestHearts.esm=1

OldWorldBlues.esm=1

LonesomeRoad.esm=1

GunRunnersArsenal.esm=1

CaravanPack.esm=0

ClassicPack.esm=0

MercenaryPack.esm=0

TribalPack.esm=0

Fallout3.esm=1

Anchorage.esm=1

ThePitt.esm=1

BrokenSteel.esm=1

PointLookout.esm=1

Zeta.esm=1

TaleOfTwoWastelands.esm=1

TTW_AnchorageCustomization.esp=0

TTW_XPReduction.esp=0

TTW_SuperMutantRebalance.esp=0

TTW_StashPackOptions.esp=0

TTW_OutcastTrading.esp=0

TTW_NoKarmaDCFollowers.esp=0

TTW_MoreCookingItems.esp=0

TTW_Bobbleheads.esp=0

Steam versions of both Fallout 3 GOTY and New Vegas Ultimate Ed.

I have reinstalled and fixed my issues with the main menu not appearing, but I can't start a new game. When I click New Game, the popup asking to overwrite the current Autosave appears. Selecting "yes" does nothing and closes the popup, as does selecting "no", so I am stuck at the main menu. I am on a clean install with no old saves to attempt to load.

Possibly of note, I can not toggle archive invalidation (it is currently on, I just wanted to reset it to make sure) because I apparently do not have permission to access fallout.ini

Also, no matter which .exe I select to start the game (FalloutNV.exe, FalloutNVLauncher.exe, NVSE_loader.exe, fnv4gb.exe), the default New Vegas launcher pops up.

I have no idea wtf.

Post by **morlund69** » Sat Dec 28, 2013 7:37 am

And on a whim, running the game as an administrator makes no difference.

Post by **Thatchor** » Sat Dec 28, 2013 8:12 am

Open up the console from the main menu and type:

COC Springvale

See if it'll actually load you into the game.

Post by **morlund69** » Sat Dec 28, 2013 8:23 am

Ok I have just tried that and it did work. I am in game.

Post by **Thatchor** » Sat Dec 28, 2013 8:27 am

I don't know why I told you to do that. I just wanted to see if the game actually worked. :P

Uhm, okay shooting in the dark here:

In your fallout_default.ini, which is in the game directory (steam folder), and in your Fallout.ini which is in your mygames/new vegas folder, look for the lines:

SCharGenQuest

sIntroMovie

bLoadFaceGenHeadEGTFiles

What are they set to?

Post by **morlund69** » Sat Dec 28, 2013 8:30 am

SCharGenQuest=001FFFFB

sIntroMovie=

bLoadFaceGenHeadEGTFiles=1

for both fallout.ini and fallout_default.ini

EDIT: sonuva... I see the problem, will test. (I have it as a B when it should be an 8)

Post by **Thatchor** » Sat Dec 28, 2013 8:39 am

Good catch. Let me know if it works. :)

Post by **morlund69** » Sat Dec 28, 2013 8:44 am

Okay so fixing that error in both ini's fixed the new game problem and I feel like a dumbass. Also, fallout.ini was set as read only which is why ArchiveInvalidation failed. That doesn't make sense to me because the mod manager explicitly said it changed it to not be read only. Whatever, its fixed now.

On the other hand, I still have the "any .exe opens the launcher" thing. While that doesn't strike me as harmful, it never happened before and I don't think it should be happening now. Thoughts?

And thanks for all your help Thatchor, I wouldn't have caught that error without you.

Post by **Thatchor** » Sat Dec 28, 2013 9:00 am

Yeah, it'll change to read only sometimes. Usually because of Steam in my experience at least. The only time that the game opens the launcher when it shouldn't is when I have Steam turned off and I try to start the game through my NVSE shortcut. NVSE doesn't load the launcher, but it'll turn Steam on first and Steam loads it. If Steam is already open, nvse_loader.exe boots straight into game. As for your situation, no clue. If you're using NVSE, type getnvseversion into the console and make sure it doesn't return an error.

Post by **morlund69** » Sat Dec 28, 2013 9:11 am

getnvseversion returns "NVSE Version: 2"

My Steam is open while I'm doing all of this so I suppose the launcher isn't supposed to be popping up, though it appears to be totally harmless and simply a minor inconvenience.

EDIT: Soooo it turns out the launcher problem doesn't happen if I boot fnv4gb through steam as opposed to double clicking the .exe, and I have feeling I should have known that and I'm just stupid today. Anyway, TTW 2.4 is good to go on my toaster now, so imma go punch Butch right in the tunnel snake.