Fallout TTW was starting in New Vegas

Post by **BrotherofCats** » Fri Aug 12, 2016 5:30 am

Yep, started the game in FOMM through FNV4GB and again I was in Good Springs. I also tried to start a new game and it would let me. So FNV4GB is the culprit. Don't see how that's possible. I played almost two hundred hours of Fallout New Vegas with that program installed and never had this problem. And I played several starts in my last install of TTW without this problem. Something really screwy here.

Post by **RoyBatty** » Fri Aug 12, 2016 7:00 am

Yeah that doesn't make any sense at all, if NVSE isn't loaded the game should just crash.

I've had no reports of similar behavior on the tool, are you using the updated version?

What OS are you on? Is the FNV4GB exe and it's dll installed into the Fallout NV root directory?

Can you post the FNV4GB log on pastebin and link it here. The log is located in My Documents\My Games\FalloutNV

Post by **BrotherofCats** » Fri Aug 12, 2016 2:17 pm

OS is Windows 7, 32 gigs of ram. It seems to have loaded everything from the zip file into my NV directory. Looking at the log it looks like NVSE was failed in its load. Would that mean that since TTW didn't launch it went to a launch of Fallout New Vegas, and the save games came up in Good Springs since Washington was not available? One other thing. The game resides in a folder labled Fallout New Vegas TTW, to differentiate it from the Fallout New Vegas folder where I'm going to be modding that game. It didn't seem to make any kind of difference in the last install of TTW, but the FNV4G log seems to indicate that it was looking for Fallout New Vegas, so I'm wonder if the TTW in the name is throwing it off.

Fallout New Vegas 4GB

=====================

by MonochromeWench (the.wench@wenchy.net) Version 1.6.

Link to FNV4G log: http://pastebin.com/GqsgBtan

Post by **BrotherofCats** » Fri Aug 12, 2016 2:27 pm

OK, I think that was it. I renamed the folder Fallout New Vegas, getting rid of the TTW extension, and everything works. I can start a new game and it puts up the menu to pick the start in the Mojave or DC. Loading one of the saved games and I was outside of Vault 101. I was thinking that FNV4G was not loading NVSE extender last night before I went to bed, and that was the first thing on my mind when I woke up this morning. Thanks for pointing me to the FNV4G log, that made it easy to confirm my hypothesis. Still kind of weird that the game ran fine on the last install, except for a lot of crashes. Computers are strange, and not always predictable.

Post by **RoyBatty** » Fri Aug 12, 2016 7:53 pm

If you run the default launcher it will change the registry path entry to point to the current directory the game is being run from.

Post by **jlf65** » Sat Aug 13, 2016 8:33 pm

I ran into a problem getting FNVEdit/FO3Edit working when I switched from 32-bit Windows to 64-bit Windows. The game only makes one registry entry, but you need TWO slightly different entries for 64-bit. My FONV registry entries are like this:

[quote]Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Bethesda Softworks\FalloutNV]

"Installed Path"="C:\\GAMES\\Bethesda Softworks\\Fallout New Vegas\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bethesda Softworks\FalloutNV]

"Installed Path"="C:\\GAMES\\Bethesda Softworks\\Fallout New Vegas\\"

[/quote]