Game failing to launch

Post by **LZH14** » Sun Jan 01, 2017 5:18 am

System: Windows 10, Intel i7 4790k, 16 GB RAM

Mod Manager: FOMM 0.14.11.12

Install log: attached

Load order: attached

Fallout 3 Version: Steam download GOTY

What I expect it to do: ...work?

What it actually does: Gets to "Bethesda Softworks" title screen then gets stuck, unresponsive to task manager as well

What have I already tried: Fresh installs of both Fallout 3 and New Vegas (cleared everything possibly related to both games), adding NVAC

Notes: Fallout 3 and New Vegas are both installed on an external hard drive. The main hard drive is small and only contains the operating system.

Post by **RoyBatty** » Sun Jan 01, 2017 7:16 am

Try the things outlined here https://taleoftwowastelands.com/content/ttw-performance-guide

sometimes the multicore tweak is needed

Post by **LZH14** » Tue Jan 03, 2017 1:55 pm

So after implementing all the fixes in the performance thread, the game worked. Then, I began installing mods (and testing the game after each installation) and it still worked. Eventually, I got everything installed and began playing, then the game crashed during some random gunfight. No biggie, right? Except, now it's back to stage one, with freezing on "Bethesda Softworks". I disabled all plugins and kept disabling esms until it worked... which it did... after I disabled fallout3.esm... Was there possibly something in gameplay that could reset the file condition?

I've attached my load order for reference. With only the checked off boxes, it works, but obviously that's just FNV with no mods. Anything in there that I should change? Load order? Broken mods that are incompatible with TTW?

Post by **RoyBatty** » Wed Jan 04, 2017 1:38 am

If you run the default launcher your ini will be reset to default.

That's a pretty light load order and all of those mods are known working.

Post by **LZH14** » Sat Jan 07, 2017 6:39 pm

Update: Game worked for a few days, then was experiencing mouse stuttering and restarted computer. Game no longer works. All three INIs have the changes implemented, as well as the INI created for NVSE config.

To further elaborate, when launching from steam, clicking play on Fallout: New Vegas or launching from the desktop icon, the launcher will fail however many times before eventually deciding to work on its own. Then, it'll go into the sequence I've described previously. When launching from FOMM as FNV4GB, it'll just go straight into the failure sequence. What things should or shouldn't be set to read only?

Post by **RoyBatty** » Sat Jan 07, 2017 7:05 pm

Try the new 4GB patch luthien and I made. It's run and done 1 time application.

Post by **LZH14** » Sat Jan 07, 2017 8:18 pm

Patcher was implemented, game still stops working at the same phase. Had to install SuperF4 just to prevent from having to log out every time the game got stuck. Is there some process log lying around somewhere that I can post or something like that? To figure out exactly where in the startup everything goes to shit?

Post by **RoyBatty** » Sun Jan 08, 2017 4:22 am

See the NVSE LOG topic https://taleoftwowastelands.com/content/nvse-error-log-bug-hunting

NVAC keeps a log in the root folder of Fallout New Vegas.