Yet Another Crashing Thread - Startup

[VAULTEER]

All right, so I'm new to modding, although I've been reading threads on here for quite some time, and so I decided to go for it. I downloaded Fallout 3 via Steam, and had to apply the d3dl.dll file and the # of processors trick, and got it to work. I then downloaded the Unofficial Patch and Fallout Mod Manager, and it still worked, I could play forever.

 

I then decided to go for something a bit more. So I got the Fallout Script Extender (FOSE) and the Fallout Wasteland Edition (FOWE), put the FOSE .dll files as well as the launcher into the area it was supposed to go (The folder with the fallout.exe, not the one where I had to go to put the processor trick in), and then got FOMM to go to town on unpacking, installing, and finally activating the FOWE Pack 1, Pack 2, 6.03 patch, and the HUD update (I can't remember its exact name). Everything was ready to go, from the installation, to the order of loading, to making sure to use the FOSE loader. And yet it crashed. In less than 10 seconds after clicking the launcher, it crashed back to the desktop. For hours I tried reinstalling, triple-checking, refreshing, using different Zip software, everything, but it still is crashing. If anyone has any ideas at all why it may be doing this, it would be greatly appreciated if you could help me out.

 

General information and specifications below:

-Windows 7 (x64)

-Dual-Core G640 @ 2.8GHz Intel Pentium Processor (2 Cores, 2 Logical Processors)

-Intel HD Graphics Family (Tells no more information)

-6GB of RAM

-Yes, I have run the game unmodded, as well as modded before.

-Yes, I have all the Master applications, like Fallout3, Broken Steel, The Pitt, etc.

-Yes, they are in the right order, I have tried getting 4 different people to make comparisons with the guides. If you are looking for the exact order, I no longer have it due to uninstalling, but I assure you, I used the EXACT order defined by the author MULTIPLE times.

-I have done multiple Restores from Restore Points to insure that there is absolutely nothing left over from previous installations.

-I did a factory reset less that 48 Hours ago on my computer, so it couldn't be anything left over from anything else.

-The only ModI had prior to downloading FOWE was the Unofficial Patch.

-No, I have no idea what I'm doing, so I'm just leaving all info that might be of use to get this fixed.

 

Any help would be greatly appreciated, once again.

 

Edit: Thought I might include that I'm running the Steam version of F3:GOTY.

Edited April 13, 2014 by VAULTEER

[Purr4me]

Delete the My Documents\My games\fallout3\falloutini files, any others sitting in there and run the games launcher, have IT reset the game files, reset the graphics VIA game launcher and do not open the graphics settings in fomm. this will cause the bug again. so don't

EDITED: See spoiler:

 

F.O.W.E - Fallout Winter Edition

A Game Modification for Fallout 3

~~Compatabillity Test~~
!!Rating Meanings!!
Pass = No Conflicts Known
Stable = Stable, with possible Unknown Conflicts
Minor = Known Conflicts But Will Still Work, possbile Crashes
Fatal = Your Game Will Definately Crash at some point


Tested on and created on Fallout Official Patch 1.1.0.35- *STABLE*
Tested on Fallout Official Patch 1.4.0.6 *STABLE*
Tested on Fallout Official Patch 1.5 * FATAL*
Tested with Unofficial Fallout 3 Patch version 1.5.022 and Unofficial Expansion Patches Anchorage and The Pitt- *STABLE*
Tested with Fallout Fake Patch 1.5.022-* STABLE*
Tested Conflicts between Major Mods and FOWE such as Fook,MMMRC2,CALIBR,XFO,FWE,EnhancedWeather-Rain, Fellout, WeaponModKits- *MINOR*
Modded with G.E.C.K. version 1.5.0.19........*FATAL* :)

~~Mod Requirements~~
Fallout 3
Fallout 3 DLC Operation Anchorage, installed and Anchorage.esm checked
Fallout 3 Official Patched Version 1.1.015 to 1.4.0.6
1.5 Gigabytes of Free Hardrive Space for F.O.W.E. Lite , 2 Gigabytes for F.O.W.E.
The minumum Requirements to play Fallout 3 as indicated by Bethesda
**DO NOT USE OFFICIAL PATCH 1.5 With This MOD~~

 

Based on the read me file, It clearly states in it , there was an issue dealing with the early patches for this mod (FOWE) There fore I have extracted and recompiling the data for use and inspection in Mod Organizer so I can see what needs to be updated in it to conform to 1.7 and the last version of the GECK.

 

NOTE: I hold no promises here, it is just to inspect and possible find a solution. This very well can be the reason for your issues.

kitty

Edited April 13, 2014 by Purr4me

[VAULTEER]

Ok, call me an idiot if you like, but how would I reset the Game files and the Graphics settings? And you mean FOMM for the launcher right? Not FOSE?

[Purr4me]

C:'Falout3\falout3launcher.exe

Leave Fomm alone, "Do Not touch it."

C:\user\username\My Documents\My games or just games\fallout\fallout.ini

 

FOWE winter edition breaks my game too. well it broke so much I uninstalled all data here. Some of the *.dds files that came with it are not from fallout 3 ,and the code is not for this game, though the names are the same. I can't prove anything, I just wiped it all out.

So, I can only suggest you use Oleander to compress the loose data from the data folder , it a tool used here for some things, IF the data from that mod gets compressed, chances are the foot print the files cause will be so small not to interfere any more.

Not a fan of FWE any Edition. Not a fan of Fose Either. can't track invisible bugs when that is used, those bugs are Fose related scripts that do all sorts of crazy things, because of that, there is no way to track your game flow. call it a wild card.

But, Buggy graphics set ups here on the nexus is abundant and usually is the problem.

 

 

-Intel HD Graphics Family (Tells no more information)

http://fallout3.nexusmods.com/mods/17209/?

 

kitty

[VAULTEER]

Alright, I attempted what you said in your first post, deleting the .ini files, revalidating the game via steam, and then launching FO3 via its own launcher. It then reset all the graphics options and files, and I installed FOWE, only to have it crash again, like before, before I even get to the main menu.

Now to recap, I've done the d3d9.dll download to bypass the single-core settings that FO3 has by default, and it ran. It ran with FOMM installed along with the Unofficial Patch. It just doesn't run when I have FOWE even in the FOMM. (To get the game to run again I need to not only deactivate FOWE but also delete it from the MM itself. It doesn't matter if I have it in Downloads, but just the fact that it is in FOMM seems to make it crash.

 

I have no idea what to do.

[Purr4me]

Convert ( FOWE)into an esp using FNVutility.jar then rename the last letter of the esm to esp.

extract the packages of (FOWE) to a folder from the down load with 7z, and if the extraction shows an error, the nthe download is corrupted, if not, continue.

 

inspect the contents, verify if all contents are real data for fallout 3. What may be taking place is cross data corruption from the servers. my copy contained data from several mods, only these mods are from different points, and not complete, just bit's an pieces, most of the dds files were not view-able, so, if a simple dds viewer can not render them, then the game sure will crash. I am currently cruising the Japanese web sites in another browser looking for a replacement source. I need to compare the data contents against. also looking on other well known websites for an equivilent. some place on one of 40 old hard drives in storage I have an original from here that is not updated nor corrupted. it works, I worked with EnRoger with the intervention riffle used in Earach42's mod and MUW so we need to be on the same page. that was a while ago. this one here is just no good. does not work for me either. site might need to switch it to a different server but as it is, not gonna work. I too have removed all data from this mod. a shame too, I had Beautiful pines all over the place, a real winter wonder land. I like scenery, not dead things. you mat need to do the same.

kitty