Fallout 3 Won't Run with Mods Installed

[phantomgamerz]

When I install a mod (any mod it seems) Fallout 3 will start up once to the Menu Intro, then it will crash to desktop with no error.

Every launch after that it will start up to a black screen and immediately close.

 

It works FINE without modifications installed.

 

At first I tried the 10 essential mods as posted on PCGamer, which gave me this issue.

I assumed it was a Mod Incompatibility Issue so I reinstalled my game.

I then installed FOMM and Fook2, I used the Archive Invalidation Option in FOMM.

The problem occurred again, so I do not think it is a Mod issue but possibly Game/OS issue.

 

I have Windows 7 Ultimate x64 and am using the latest Steam version of the game.

I have no DLC installed.

 

I have my Video Drivers fully updated and have the KLITE Codec Pack.

Anyone have any suggestions?

 

The problem is nearly identical to the one in the following thread, but I didn't want to bump it since it was so old.

http://www.thenexusforums.com/index.php?/topic/169260-fallout-3-wont-start-with-mods/

[anokii]

Have you installed FO3 to the default directory? (e.g. C:\Program Files (x86).........)..??

 

Sounds like it's a UAC problem - highly suggest if you have to uninstall and reinstall someplace like C:\Games or something like it (another words custom install and put it in a different directory.

 

Basics;

 

- If your running Vista / Win7 the game will default install to C:\Program Files....... This is a problem as UAC can interfere with the setup of mods in the future. If you haven't got a game running right suggest you uninstall and reinstall to a different directory (something like C:\Games). Uninstalling has it's own issues and you should search the forum here as there are already a couple of good guides for that. (I think someone posted a 'utility' on nexus that does it in one hit but can't find it at the moment)

 

- Make sure you patch the game to 1.7 (latest FO3 patch)

 

- Update your drivers - however be aware that some versions of drivers can introduce problems as well (e.g. NVidia - there a couple of versions that caused more problems than fixed).

 

- Update or remove G4WL (Games for Windows Live) - Personally I remove it and you don't really need it, see this: http://fallout3nexus...ile.php?id=1086

 

- Check out this guide for great tips: http://www.tweakguid...Fallout3_1.html in there you can find the 'multi-core CPU' fix which is a must if your running a multi-core CPU

 

- make sure to use FOMM to help manage your mods and you may need FOSE as well for some mods, if they need it they should state in the readme file.

 

That should get you started for the moment. Let us know if you still can't start after you work your way through some of that.

 

PS: Your Fallout.ini file should be in C:\Users\%username%\My Games\Fallout3 folder if your running Win7 - sorry can't remember where for the other OS's at the moment but I know it's in that tweak guide.

[phantomgamerz]

Have you installed FO3 to the default directory? (e.g. C:\Program Files (x86).........)..??

 

Sounds like it's a UAC problem - highly suggest if you have to uninstall and reinstall someplace like C:\Games or something like it (another words custom install and put it in a different directory.

 

Basics;

 

- If your running Vista / Win7 the game will default install to C:\Program Files....... This is a problem as UAC can interfere with the setup of mods in the future. If you haven't got a game running right suggest you uninstall and reinstall to a different directory (something like C:\Games). Uninstalling has it's own issues and you should search the forum here as there are already a couple of good guides for that. (I think someone posted a 'utility' on nexus that does it in one hit but can't find it at the moment)

 

- Make sure you patch the game to 1.7 (latest FO3 patch)

As I stated, I am running the latest Steam version.

That means it updates to 1.7 and installs to Program Files x86/Steam/Steamapps/common.

 

I just fixed my issue though, sort of.

It was the FOOK2 Beta Files and the FWE Hotfix that were causing the game to not launch, I installed everything without those two and it launched fine.

But now I have another few issues.

 

One, the FWE Alternate Start option freezes up my game.

Two, after entering Megaton my screen got blurry. It would clear up every 5 minutes or so but would go back to being blurry shortly after that.

The blurriness doesn't affect the actual PIP Boy Menu, but it affects the Pip Boy Model. It also doesn't affect the Pause Menu.

 

Thirdly, the game will sometimes just freeze up and go not responding until I kill it with task manager. This also somehow binds my mouse to the Fallout 3 screen, so I can't alt tab and click off or anything.

I need to Alt Tab Del, open task manager, and use my arrow keys to scroll to Fallout3.exe and press Delete -> Enter.

 

The 3rd option is semi rare, so it doesn't matter that much.

I suspect all of these issues are related to each overhaul interfering with each other.

 

I heard of Compatibility Patches such as FOIP, but I don't quite understand how I can install it.

I suspect the issue is from the overhauls replacing each others textures and not the ESPs themselves.

If anyone could tell me step by step on how to make MMM EVE FWE and FOOK2 play nicely together I would very much appreciate it.

[ICERAY2000]

My personal experience with STEAM left me steaming. I will not run any game that requires it again. I didn't read the other responses, so my only advice would be to make sure you are upgraded to 1.7 patch, and the latest Fallout Mod Manager - use the suggested load order function --and FOSE.

You may need to totally uninstall everything, check to make sure it is ACTUALLY gone, then reboot and try it all over again.

Welcome to the wonderful world of modding...

[devilpengui]

Run in windows xp compatiblity, it might help.

[Anilium]

I just got windows 7 64 myself and tried installing a few mods. The issue I have with 99% of them is that my "game of the year" edition has no actual data file. Well, the file is there but nothing exists in it. So any mod that tells.asks for my to copy data in fallout3/data/whatever......all the nif files to be replaced simply aren't there. When I run the game with the fallout3 app as opposed to the launcher some core mods will run. When using fose it tries to load old game files that I thought were deleted after the patch. My system is run as administrator and I have hide files options turned off. It might just be the version of fallout that people have that determines how easy mods are to use.

[Fonger]

I just got windows 7 64 myself and tried installing a few mods. The issue I have with 99% of them is that my "game of the year" edition has no actual data file

what steps have you taken to insure that this is not simply a UAC issue

[IDKVignette1]

I also have the same problem, So i took ICERAY's advice of deleteing eveything and then reloading it. And it worked, and then I tried the DLC's they then worked also, but then I put on FOMM first, then I started to put my mods on maybe only 12 of them. Then it started to freakout and cry at me, and it only got to the green screen before the Native American Stand-by screen, and now it reseted back to where it was before...at the begining..Not sure what's wrong, but it all started not working after I downloaded FOSE, It worked the first time I used FOSE but then, the next day it stopped working. I then tried the Patch, the newest one for FO3. And now I have no idea what to do...

[Purr4me]

pick out only the mods that do NOT require fose, install them , test them, then make a new folder on the desktop to sore all they installed, Move the data for them only out of the games data directory. use fomm to uninstall the hard coded hidden data it is keeping online. once that data is removed, you can simple copy back your non fose mods into the data directory, and have a backup to counter overwrites.

 

Now, you do this very same thing with all fose required mods too. but, you make a separate folder for their stuff and again, test them alone, by them selves. if there is issue, you move that data now out to the new folder and use fomm to uninstall that hidden data as well.

 

At this point you should only have the original game, and all things should run properly. if this procedure does not work, you have OS issues, steam issues, missing operating system data, incompatible software's installed, antivirus programs and firewalls security issues with steam that have not been set yet.

 

windows 64bit is not a nice os to play with. Steam is not nice to play with o0n that system.

 

Windows 32bit blows all that out the window, shortens the list of problems and is a natural environment for the game.

 

give a shot, you have nothing to lose but time anyway.

 

kitty.