Your not supposed to add mods to F3?

[zfreakazoidz]

So I posted this on the official forums and basically got laughed at. I told them I installed Fallout 3 and the addons. Patched the game and installed about 10 mods (and mod mananger). Non of with I activated when I first played. Well either way the game kept crashing at the "dad" scene when you had to walk to him.

 

Anywho... they said for one I shouldn't install it in the programs folder and second I shouldn't install mods....ever.

 

Is this true? Why else would i rebuy this game for PC? Kind of defeats the purpose! How do people use mods then!

[Baelkin]

Don't listen to the people that say you shouldn't install mods because that is just their opinion and not fact. Most mods work fine and can add tons of content to your gamplay experience and, in my opinion, not modding your PC Fallout 3 is a bit of a waste. :)

 

As for installing in the programs folder, those comments do hold some merit as you can experience problems running mods using that install directory on Vista systems. Typically installing the game outside this folder will solve most file access problems caused by Vista, however my game is installed inside the program files folder and I have had no issues running mods yet. I haven't really changed a whole lot on my Vista system since install, however I do login as Admin and have turned off UAC which typically are the roots of the issue.

[WatersMoon110]

My not? (You are = You're) *grin*

 

I run on XP, have my game installed in the Program Files, and have tons of Mods, and I've never had a problem with a working mod (as opposed to one that I'm making).

 

Also, even without the loader, some mods can be added to the game. The GECK Tutorial, made by Bethsoft, says this:

Now that you've got a plugin with something to look at, let's test it in the game.

Start the Fallout 3 launcher and choose the "Data Files" option. You should see your .esp in the list of files that pops up. Check the box next to it and click OK.

[zfreakazoidz]

I don't get why mine doesn't work then. :( Maybe F3 just is glitched because of something on my computer then. I know some people had a problem with the Codec pack installed.

 

When you say you installed the mods outside fallout 3 folder where did you put them? And how does the game know where they are? Or am I misunderstanding. Also whats UAC? I know I've turned off a bunch of annoying features in Vista so far.

[VictoriaG]

My not? (You are = You're) *grin*

 

I run on XP, have my game installed in the Program Files, and have tons of Mods, and I've never had a problem with a working mod (as opposed to one that I'm making).

 

Well the previous poster is talking about Vista, since the UAC feature on it can cause issues with altering the contents of that folder.

[phoneyLogic]

Hey, do you want to reinstall?

If you "only" reinstall, it could lead to problems.

A "clean" reinstall would be recommended :)

Sorry for the long post, but this is kind of detailed ^^

 

Reinstalling Fallout 3, the "clean" way

1. Backup save games in: <Start Menu> \ Documents \ My Games \ Fallout3 \ Saves \
    
   
2. Uninstall Fallout3 in your System Control ( Programs )
    
   
3. There are two Folders left: Game Dir (with your Mods) & My Games folder
   -> delete or better rename the Folders to backup
   -> be careful with backed up data and avoid using old *.ini files
    
   
4. Clean Registry (e.g. by CCleaner)
    
   
5. Reboot your System, to get all Registry changes applied
    
   
6. Keep your System up to date. Perform a Windows Update including DirectX.
    
   
7. Install Fallout.
    
   On Windows7 or Vista, it is highly recommended to install the game to another location than "Program Files" ( for example C: \ Games \ Fallout 3 ) to avoid problems with the security feature UAC.
   Alternatively you could disable UAC, but this may lead to a less secure system, so be warned.
   http://www.loaditup.de/files/thum/395034.jpg
   ( click to enlarge )
    
   
8. Install the latest Patch which fits to your game version.
   ( If you get the xlive.dll error at start, then you'll need to install the lates GfWL-Client too. )
    
   
9. Backup your "clean" Data folder before installing Mods.
   It saves time if something went wrong - especially if you installed Fallout via steam.
   http://www.loaditup.de/files/thum/395035.jpg
   (a clean data folder)
    
   
10. and Defragment your Hard Drives...
    

[mechine]

LMAO!

 

 

 

 

 

 

*edit*

 

 

Wait I kind of see what's going on.

 

 

Do the clean install thing above.

 

 

Then focus on testing a vanilla version of fallout 3.

 

 

Use the 1.7 patch

 

 

Then run around in vanilla fallout trying to make it crash

 

follow the tweek guide at this point

 

after you get your base fallout 3 working well, then start modding it an learning how to mod it

 

it's not easy an takes tons of work an reading

 

totally worth it though.

[zfreakazoidz]

Well I figured most of that. Although I didn't know I had to clean install it (removing reg portions and all). Now it works just as vanilla.

 

So I read this guide:

http://www.fallout3nexus.com/articles/article.php?id=43

 

I guess I am kinda confused though. So if I just have a ESP file then I only need to run the FMOD thing and load that mod and thats it right.

 

HOWEVER if I have a mod that has other things with it like textures...etc I need to first run the Archive tool, THEN the FMOD tool then start F3? Or do I start the FMOD tool, THEN run the Archive tool, then start F3?

 

Sorry I just am kind lost.

[mechine]

Uh Archive invalidation invalidated is built into FOMM, which you toggle on or off as you wish

but to my knowlege you really only have to turn it on one time, when you first run FOMM.

 

You can also ignore any mention of adding lines to archive invalidation

 

Archive invalidation invalidated (get it? no more archive invalidation adding lines in)

We used to have to add in lines of text telling which textures to make invalid

You don't have to mess with that part of the fallout.ini either

just toggle it on in fomm an select yes to apply it, an then forget about it

 

 

 

LOL

 

 

How did you get so screwed up?

 

 

 

For one I wouldn't use that "guide" idk it says 2008 for one thing

 

 

then the pinned topic here on the forum "installing mods with DLC's is much better anyway

 

http://thenexusforums.com/index.php?showtopic=120735

 

Idk I've never even seen that guide you linked, not that it looked like it held enough information anyway.

 

 

 

There's a old guide called ultimate load order, which is listed in the downloads on nexus.

 

It's pretty old now though.

 

 

But It does teach you how to install mods among other things. So it's still valid, but

 

it's all pre 1.7 patch infomation, which things really didn't change much, anyway.

 

The pinned topic would be your best bet for updated information on how to install.

 

 

 

 

 

I don't use FOMOD, idk I don't like auto installers either

 

I drag an drop stuff in, but you know checking what is going to replace something first.

 

 

 

Pretty much I get a good install of fallout 3, then run the tweek guide http://www.tweakguides.com/Fallout3_1.html

 

Then test the poop out of it, try to make it stutter an crash or whatever

 

Then I add the DLC's an test it again.

 

 

I try to fix any problems inherent in fallout 3, or minimize them like stutter for one example.

 

 

Then I get a clean game start, and go run to one of the megaton bathrooms or a small room with no npc's

or really anything in it. Which is where My clean save game is, also where I'll activate the mods in the load order

either one at a time or all at once depending on how many scripts are running. The clean save game is helpful later on

if you run into problems from a diagnosis standpoint.

 

Then I start installing mods when I know I have a good working fallout 3

 

 

Then come up with a load order of those mods

 

 

Then run a merge patch with FO3edit (load up all mods an Ctrl A to select all, right click, create merge patch, save)

Then you fix all the conflicts an errors in the merge patch you saved

 

 

Then I'll start at the top an work my way down the load order with the whole load order loaded in FO3edit

fixing all the conflicting entrys or maybe even deleting stuff, or removing mods from what I've seen in them

Also small mods that only change a thing or two get added into other existing mods, to save space.

 

 

Then I'll have to create a OverRide or ten (a .esp plug in which uses one or multiple esm/esp as masters)

 

In a mulitple conflict entry inside FO3edit the one the furthest to the right gets used

 

You can't fix everything in the whole load order the normal way, so sometimes you have to add a override

 

like one that uses Primary needs and inebriation as masters, to allow you to create a override inside it

 

which can use the scripts from both mods in order to produce a whiskey which will get you drunk but also

 

effect primary needs thirst, there's a long first draft on how to do overrides in mod trouble shooting.

 

 

 

 

At the very least I view an fix what I can in the load order with it all loaded in FO3edit, then also use the merge patch.

All that work just to avoid a few more crashes.

 

 

 

It doesn't ever get easy, you always have to read stuff, an you always mess up stuff.

 

 

So go out there an start messing up stuff so you can learn.

 

 

 

 

 

Idk it might help you out later on, if you turn off fallout 3's AA an AF (performance)

 

Then force whatever AA an AF you want via the grapics card control panel

 

which is kind of opposite from all other games, but hey it works great

 

you can even pick higher or max settings without any performance loss

 

 

wierd huh, try it out...

 

 

 

Then much later on remember when you're playing fallout to reboot the system every so often

as the system cache sometimes gets corupt which will corupt your save games, also ending that game.

 

Which is why we never Auto save, or Quick save.

 

Press Esc, then create a new save each time.

 

And either keep all of them an never delete any, or keep 20 or more.

 

 

 

 

Running 250 mods is fun, no doubt

 

 

Getting 250 mods to work together though isn't very fun at all, it's just like really hard work that never ends.

So sometimes running a simple load order with only like 50 mods is what you need, just to get some game time in.

 

 

It's a learning process, from nooby noob noob, to using mods, to creating mods, to fixing mods, then trolling here

an telling everybody the wrong thing to do like me.

[zfreakazoidz]

Thanks! I got some work to do! lol