Fallout freezing with mods (what's new?)

[ChuckFinly]

I'm having some trouble with game freezing.

 

I'm running Fallout 3 Reborn.

 

Iron Sights

 

All the DLCs,

 

and Fellout, as well as various texture packs.

 

I would be running the game and it would freeze when exiting the program, leveling up, or loading another profile. It's a serious pain in the neck!

 

I'm running the latest patch as well.

 

If you need me to be more specific on my information just ask.

 

Thank you for your time and have a nice day.

[ElderMalaclypse]

We really need your exact load order to help with this sort of issue because it could be dependant on what order the mods are in.

So post your load order and someone should be able to help you out.

[ChuckFinly]

Thank you for your time.

 

I actually didn't know that the load order mattered!

 

As best as I can remember, I think the order was as follows:

 

The DLC's

 

Iron Sights (unknown version at this time)

 

Reborn including the DLC addons

 

*

 

Fellout

 

All of Fellout's DLC addons

 

*Texture addon packs, most of which were done by a guy known as Niel_MC I think.

They include his Megaton, Rivet City, Rock, and General HD textures

Other textures include Night Sky by CptJoker

 

Note: I forgot to download the other mods that Fellout was designed to work with (that may be the problem, now that I think about it).

 

 

I have to load FOSE to get some of the features from the mod to run properly, such as sprinting, and Iron Sights blur. Otherwise they will neither one of these will not work at all.

Edited November 21, 2011 by ChuckFinly

[Jeoshua]

Get FOMM, and ignore NMM for the time being. Make a proper load order. This could be half your problem right here.

[ChuckFinly]

Thanks for your reply.

 

That is the actual load order in FOMM; I apologize for not mentioning that.

 

My EXACT load order in FOMM is the following:

 

Fallout3.esm

Anchorage.esm

BrokenSteel.esm

ThePitt.esm

PointLookout.esm

Zeta.esm

RH_IRONSIGHTS.esm

RH_IronSights_Basic_VanillaPlugin.esp

RH_IronSights_RemoveRecticule.esp

RH_IronSights_Basic_AnchoragePlugin.esp

RH_IronSights_BasicBrokenSteelPlugin.esp

RH_IronSights_Basic_PittPlugin.esp

RH_IronSights_Pitt_NewRifleSights.esp

RH_IronSights_Basic_PointLookoutPlugin.esp

RH_IronSights_PL_NewItems.esp

RH_IronSights_Basic_ZetaPlugin.esp

fallout3_reborn_v9.esp

Fellout-Full.esp

Fellout-Anchorage.esp

Fellout-BrokenSteel.esp

Fellout-pipboylight.esp

Fellout-PointLookout.esp

Fellout-Zeta.esp

XRealistic Weaponry V5.espX (currently not selected).

 

 

I hope that answered some questions.

 

What is a "proper load order" and what is "NMM?"

 

Thank you for your time in dealing with my ignorance!

Edited November 22, 2011 by ChuckFinly

[Jeoshua]

There is a program on the main page of the Nexus, in Open Beta, called "Nexus Mod Manager"

 

Ignore it. It's still in testing, doesn't have half the features of FOMM, and in general is a piss poor but very global version of the mod managers out there for the different games that Nexus houses mods for. It's supposed to be a one-stop-shop for all your mod installation needs, but as of this moment it's pretty much just a hack and doesn't do the job as well as a more proper load ordering tool, like OBMM or FOMM.

 

You mention the game freezing when loading a "profile"? Is this a Steam or GFWL thing?

[Werne]

@Jeoshua He probably meant saves.

 

@ChuckFinly Do you have a quad-core processor? if you do, here's how to fix the freezing (at least some of it):

 

Open up the fallout.ini file in: My Documents\My Games\Fallout3

Find the line:

bUseThreadedAI=0

change it to:

bUseThreadedAI=1

Add another line after it and insert:

iNumHWThreads=2

This will limit the game to 2 cores and prevent the engine bug from causing the game to freeze.

 

And I don't recognise these plugins

 

RH_IronSights_PL_NewItems.esp

RH_IronSights_Pitt_NewRifleSights.esp

 

Try disabling them and see if it helps.

Edited November 22, 2011 by Werne

[ChuckFinly]

Thanks you are right, "saves" is a better term and I should have used that.

 

Those files you talked about came with the main download, actually the one I downloaded was V0.9A...donno how that happened.

 

Lol, I actually have (by today's standards) an ancient system!

 

Intel Pentium 4 650 3.4GHZ single-core with Hyper-Threading enabled.

 

Dell Optiplex GX280 mobo (SMT)

 

3GB 533MHZ RAM

 

MSI Nvidia Geforce 9600GT 512MB version.

 

Believe it or not, Fallout runs fairly well on these specs.

 

 

Though I must ask, why would have 3 or more cores run the game cause any issues?

The next system I'll build myself (tired of brand PC's), and it will likely have a quad or hex core.

 

 

 

This is the Game of the Year Edition on the disk. I don't like Steam.

Edited November 22, 2011 by ChuckFinly

[BlackRampage]

Though I must ask, why would have 3 or more cores run the game cause any issues?

Fallout 3 wasn't designed to run on more then 2 cores. It's the same story as that it doesn't use over 2 gigs of RAM even if you have more then 2 gigs in your PC. (though the latter can be easily fixed.)

 

The next system I'll build myself (tired of brand PC's)

A wise choice. I think you will find that building one yourself can get you a rig with far better components and thus better performance for the same price.

 

On to the troubleshooting part:

 

Even though you have a single core processor, you may want to give the .ini fix Werne posted a try anyway. Not sure how it goes with a single core, but your processor does have hyper-threading so it might just work for you.

Just don't forget to backup your .ini first.

 

Your load order's just fine btw.

[Werne]

Yeah, Fallout runs pretty well on old comps, but it has a serious freezing issue with quad-core processors, don't know why. The .ini fix I wrote limits the game to two cores and it stops freezing but sice you have pentium 4 you don't have that kind of issue. Actually, do what BlackRampage said.

 

The plugins I suggested you to remove are not the problem, I checked them and they are only depending on the DLC's.

 

Also, usually the best way to solve your issues with modded game problems is to uncheck all mods and activate them one by one. Each time you activate one start the game and see if the problem appears. When it does just remove the last mod you activated and don't use it. It's trial and error.

Edited November 22, 2011 by Werne