aaaaaand it crashes.

[InfamousZombie]

Alrighty then, I've tried pretty much everything, from the .ini thread edit to d3d9 to windowed mode to driver updates and so on and so forth. The game won't even launch with d3d9.

Basically, the problem is that the game stops working as soon as I hit the projector loading screen, the one that says 'Please Stand By' with the Indian chief and whatnot. The one right before the Bethesda Softworks, and so on and so forth. I do not make it to the main menu, but the game does 'start'. I had it working before, a year or two ago on this computer (running windows 7 sp1), and I wanted to start a new playthrough, with new mods and stuff. Never tried MMM, FWE, DarNui, etc. before this (inorite?) and so I installed them. Stopped working. So I said, "Ok, let's make sure the game is working sans mods."

Nope.

Without any DLC.

Nope.

Here's the point where it crashes:http://i.imgur.com/LBc7T.jpg

So Nexus, can someone help me? :psyduck:

[Oubliette]

First thing's first: Never install a bunch of mods (especially large ones) all at once and then expect your game to work. It probably won't.

 

Second thing, if Fallout will not start with no mods loaded - your base game is probably broken. Please reinstall.

[michel92]

One thing to remember, as much as what I'm going to say now is irrelevant, ESMs run even deactivated. As long as they are in the Data folder, they will run.

 

Ok.

 

1. Know FNVEdit? Run it. If it opens without popup error messages, then it's not a problem in your load order. If it pops up an error message, check the log and see where the error is.

2. Your menu-whatever.xml might be broken. Try installing (via NMM or FOMM) the Unified HUD Project (search it on google/nexus). It can fix HUD errors.

3. Your ini may be corrupt. Go to my documents/my games/fallout 3, backup your ini if you want and delete it. Open the game. The launcher then is supposed to say: "Your video settings are now being detected" or something of the like. That means the game generated a new ini. Try open the game now.

 

If all of the above failed, is your game steam version? If it is, try verifying the integrity of the game cache. Else, see the post above mine.

Edited December 19, 2012 by michel92

[knovack1]

I am no expert at crash fixes, and Fallout 3 still crashes constantly now, More now then in the pass. I tried every single work around out there, and Fallout 3 is just stuborn like that. But I just have a few ideas you can try.(this is for the PC version of course)

 

Disclaimer: These are just ideas not work arounds. My game still crashes here and there, and asking Bethesda will never help. They will just tell you the game is not compatible to, etc, etc. So you are on your own.

 

1) Download the Fo3edit tool, and use it. Whenever you get rid of or install a new or old mod this tool will help your load orders, and it will also let you make a Merge Patch.(also make new merge patches when you install and delete mods)

Merge Patch-Is a tool you can create in the Fo3edit tool to help blend mods togeather that may conflict with other mods. Make a new merge patch when you install or delete mods. 1 merge patch is good enough, so if you install or delete mods be sure to also delete the old merge patch first before you run the Fo3edit tool again.

 

To make a merge patch in the Fo3edit tool is pretty simple:

once you load up the tool after it is installed it will give you two rows. One row(left) is the name of your mods that are installed in your game. The other row(right) is the plugin list that your mods need for your mods to run. To make the merge patch right click on ANY mod in the list of your mods that are displayed in the left row inside the Fo3edit tool. Click other in the drop down menu, then click Create Merge Patch. A seperate window pops up, and give it a name you want. I always name mine. Merge patch. What the Fo3edit tool then does it automaticly adds the merge patch in your list of mods, and plugin list. Close the Fo3edit tool and click save merge patch ok. When you reopen the Fo3edit tool you will see your merge patch in the list of your mods and plugins. Also be sure your merge patch IS AT THE BOTTOM OF EACH LIST. IE. The mod list and plug in list in both the Fo3edit tool and listed at the bottom of mods and plugins inside the NMM/FOMM list.

 

To remove your merge patch-This is based on the non steam version of Fallout 3.

C:/Program Files (x86)/Betheseda Softworks/Fallout 3/Data.

 

Program Files (x86) is for the Windows 7 64 bit users. And you have to click the Data folder to open it, then scroll down until you find the name of your merge patch, then just delete that folder. When you install and delete new and old mods besure to make a new merge patch when you do and do the things above again.

 

2)Get FOSE installed and working-FOSE is an acryonym for FallOut Script Extender. Most mods need a script extender for the mods to work in game. GECK I think does the same thing but I never once tried the GECK so I dunno. If you download and use FOSE, be sure to launch Fallout 3 through the FOSE.exe and NOT the Fallout.exe. This can be adjusted inside the NMM. Once you install FOSE open up the NMM and in the icons at the top on the left side, first option shows launch game with a little arrow pointing down. Click the little down arrow and pick the Launch FOSE option. So now everytime you want to play Fallout 3. Be sure to open the NMM and click on the Launch with FOSE. Your game will now start up.

 

I recommend the NMM-Nexus Mod Manager. You can use the FOMM-FallOut Mod Manager aswell. But to me I feel the FOMM is old school and most mods now are based on the NMM. But it doesn't really matter either or.

 

3)Disable the save on rest, save on map travel, auto saves, and Quick saves. For some reason Fallout 3 bugs out when people add and remove mods, and use recent saves before/after the mod was installed. Each save game should be in its own slot. Yes it is a major annoyance that this happens in this stubborn game.

 

4)Also another thing you can do if you crash is make a new save before the game crashes, then load that new save again. Basicly it goes like this: Start game/Continue/game starts up/make a save point/ quit game/load that save point.

 

5)You also can go in an indoor cell-Meaning a place inside, like a building, Megaton House, etc. Wait for 3 days and leave the inside of the area to help remove corrupted recent saves before the crash.

 

So good luck and hope some of these things work for people. Again these are not fixes, just ideas that some may had not tried yet.

 

Here are the tools described as above:

FOSE - http://fallout3.nexusmods.com/mods/8606

Fo3edit tool - http://fallout3.nexusmods.com/mods/637

NMM - http://fallout3.nexusmods.com/news/952/

FOMM - http://fallout3.nexusmods.com/mods/640

Edited December 19, 2012 by knovack1

[blove]

Turn off Archive Invalidation Invalidated! and see if it will start. If it starts then you have an XML issue and will need to uninstall your User Interface changing mods then reinstall them or delete the "Menus" folder in your Fallout 3 "Data" folder.

[knovack1]

Turn off Archive Invalidation Invalidated! and see if it will start. If it starts then you have an XML issue and will need to uninstall your User Interface changing mods then reinstall them or delete the "Menus" folder in your Fallout 3 "Data" folder.

 

Intresting concept. My game did startup when I turned off my Archive Invalidation in the NMM. So I have an XML problem? Can you define exactly what you mean by your post, Uninstall my user interface, and changeing mods? I thought XML's where something to do with text and the only thing that comes to mind are mod read me's, and Launch.exe's. Also my mods still show they are working ingame with the Archive Invaladation off. IF the game runs more and crashes less with Archive Invaladation off and the mods still work, what will happen longterm? Do you mean deatctivate all my mods in the NMM, go into the DATA folder and delete every mod then reactivate the mods I have for them to reinstall? If so I am not sure what info in my Data Folder is for the vanilla game and what info is from mods. IE Texture folders, meshes etc. a lot of mod info shown is just self explanatory. You can see the name of the mod in the DATA folder that you are using. The texture, and meshes for the mods are hard to judge, whats what, since the textures and meshes use the vanilla folders. So more info would be helpful..

 

Please and Thank you.

Edited December 20, 2012 by knovack1

[blove]

Does your game crash at the exact same spot as the original poster's with Archive Invalidation Invalidated! on?

 

When the game crashes on start just like that, the most likely cause is a missing XML include in one of the menu files. My suggestion to turn off Archive Invalidation is only meant for troubleshooting since doing so ignores any override files that you may have added like meshes, textures, and XML menu files. Of those override files, only XML menu files can cause a crash like the OP's. Uninstalling and reinstalling all of your user interface changing mods should fix the issue. If that does not fix it, delete your "Menus" folder in your Fallout 3 "Data" folder. Vanilla FO3 does not have a "Menus" folder.

 

Missing master should crash before the first slide. Missing XML includes should crash at the first slide. Orphaned records should freeze with no main menu.

[knovack1]

Does your game crash at the exact same spot as the original poster's with Archive Invalidation Invalidated! on?

 

When the game crashes on start just like that, the most likely cause is a missing XML include in one of the menu files. My suggestion to turn off Archive Invalidation is only meant for troubleshooting since doing so ignores any override files that you may have added like meshes, textures, and XML menu files. Of those override files, only XML menu files can cause a crash like the OP's. Uninstalling and reinstalling all of your user interface changing mods should fix the issue. If that does not fix it, delete your "Menus" folder in your Fallout 3 "Data" folder. Vanilla FO3 does not have a "Menus" folder.

 

Missing master should crash before the first slide. Missing XML includes should crash at the first slide. Orphaned records should freeze with no main menu.

Well my game loads up, with Archive Invalidation off or on, and I can continue from my last save, and play the game, until I get to a certain door in the metro system, and when I enter this one door it always C'sTD, with Archive Invalidation off or on. What I don't get is how can my game even run with mods, and Archive Invalidation is off? With the feature being off, I think I should crash instantly, but I only crash when I try to go through a certain door. I had not left the metro station, to test if other places I will CTD. I just know no matter what I try I will crash entering this one load door.

[blove]

CTD when entering a door can be caused be quite a few things. It would be best to start a new thread with your issue.

[InfamousZombie]

First of all, thanks to everyone who chipped in advice or whatnot.

 

Second, I figured out part of the problem. Turns out NMM had archive invalidation on at the same time as the original archiveinvalidate invalidated that I had running.

I can get to the main menu, but for some reason windowed mode has a window (I'm running fake fullscreen).

Haven't tried to start a new game or anything yet.

 

Once again, thanks a ton, and have a happy day-before-the-world-ends-or-we'll-be-fine-according-to-eyewitness-reports-from-Australia. :nuke: