Jump to content

Problem with Game Breaking (Modded).


starkeysuper64

Recommended Posts

Alright; I've reinstalled Fallout 3 in my Games folder (on my first install, I had it in Program Files x86, which caused all sorts of admin problems, so I reinstalled...), and I digress--

 

Previously, I was using NMM, but I encountered a problem wherein after installing MMM, my game appeared to be broken; no matter how I changed load order, the game would freeze and Task Manager would force quit it at the opening slide ("Please Stand By").

 

Thinking NMM was causing the problems, after I reinstalled the game I switched to using FOMM, which worked fine... to be sure it was working correctly, I only installed FWE at first, and it worked correctly on first startup. Confident that the game would work properly this time, I reinstalled MMM (with the FOIP patch), making sure to only use the "with DLC" master file. However, the same game-breaking problem occurred wherein no matter how I change which mods are installed and the load order, I cannot get past the "Please Stand By" screen.

 

My load order is as such:

 

Fallout3.esm
Anchorage.esm
ThePitt.esm
BrokenSteel.esm
PointLookout.esm
Zeta.esm
CRAFT.esm
CALIBR.esm
FO3 Wanderers Edition - Main File.esm
FO3 Wanderers Edition - Alternate Travel.esp
Mart's Mutant Mod.esm
DarNifiedUIF3.esp
DUIF3Extras.esp
FO3 Wanderers Edition - Main File.esp
FO3 Wanderers Edition - DLC Anchorage.esp
FO3 Wanderers Edition - DLC The Pitt.esp
FO3 Wanderers Edition - DLC Broken Steel.esp
FO3 Wanderers Edition - DLC Point Lookout.esp
FO3 Wanderers Edition - DLC Mothership Zeta.esp
FO3 Wanderers Edition - Followers Enhanced (BrokenSteel).esp
FO3 Wanderers Edition - Optional Restore Tracers.esp
Blackened FWE + MMM.esp
Mart's Mutant Mod.esp
Mart's Mutant Mod - DLC Anchorage.esp
Mart's Mutant Mod - DLC The Pitt.esp
Mart's Mutant Mod - DLC Broken Steel.esp
Mart's Mutant Mod - DLC Point Lookout.esp
Mart's Mutant Mod - DLC Zeta.esp
Mart's Mutant Mod - Master Menu Module.esp
Total active plugins: 29
Total plugins: 30
(Please note that I later switched to the Blackened patch, which is slightly newer; I believed that it would help resolve the problem.)
OS: Windows 8
Proc.: AMD APU A8-4500 Quad Core @ 1.9GHz
Graphics: Integrated discreet-grade AMD Radeon HD 7650
RAM: 4GB (3.5GB) DDR3
Sound: integrated Realtek HD
HDD: standard 400GB SATA
Fallout 3 is patched to 1.7x and I have all the DLC installed properly; on my previous install the game worked fine before I attempted to install FWE and MMM; all I had been using at the time was Project Reality FO3.
I've also used ArchiveInvalidated Invalidated and the 3GB Limit Remover on my executable; the Stutter Remover didn't seem to initialize properly, but my FOSE is properly updated as well.
Any ideas as to what is causing this serious conflict?
Link to comment
Share on other sites

Run the game on the lowest graphics possible. Move the Blackened patch to after the last MMM plugin. Disable and uninstall FWE - Alternate Travel. Do the quad core fix to limit your CPU to two cores. I hope this helps, since your equipment does not meet the system requirements.

Link to comment
Share on other sites

It actually more than meets the minimum system requirements, which are:

A 2.4 GHz Pentium 4

A GeForce 6800 GT

1 GB of RAM

 

When the game is auto-configured, it defaults to High settings, and runs fairly well on them, but I usually turn them down. My system specs hardly play into this.

 

That, and I've already done the .ini fix (I thought this was implied; otherwise the game wouldn't have run at all. I'm not a complete fool, after all.)

Link to comment
Share on other sites

It's a North American DVD copy, version 1.06, or whatever. I manually patched it to 1.7, added the DLC to the data folder, and I have LIVE disabled. I don't believe it's the game, because it works fine until I decide to stack MMM and FWE.

Link to comment
Share on other sites

it might be the OS, Windows 8 is more for Tablets and Devices like that, so its not the best for Gaming on a PC or Laptop

It's really not a problem in this case, though, since the problem would derive from 8's root being Windows 7... and since I've used the .ini fix, I don't believe my OS is the problem, especially since other users have confirmed that Windows 8 works fine with Fallout 3.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...