anokii

Nicely done, clean interface and easy UI, looking forward to when we can take it for a drive.

Thanks Dark0ne, having been a member for quite awhile I as many do appreciate your efforts in getting things back to normal (if you can call all of this normal) :-) Also as one that tends to a server farm I can feel your pain. Hang in there mate..!!

Check out: http://www.tweakguid...Fallout3_1.html (long read but more than worth it) Always cover the basics (these are the most common causes of start up CTD's): - Do you have a legal copy? There are known issues with dodgy copies out there and we won't support those who pirate. - are you patched to 1.7? - upgrade / remove G4WL (Games for windows Live) - Personally I remove it - if you have a multi-core CPU have you modified your fallout.ini for multi-core CPU - have you done a default install (e.g. installed to C:\Program Files\.... ) and you run Win7 / Vista - if so uninstall and reinstall to a directory outside of C:\Program Files (e.g. C:\Games): Note that the this doesn't always fix start up CTD's but if you mod it's really a must do because of issues with UAC. - check your drivers and update where necessary. Note that some video driver versions can cause or introduce more problems than they fix - these are usually in game problems (e.g. stuttering, fpx, etc) - turn off all autosave features and either use CASM or manually save. (not suspected of causing of start up CTD's) Last but not least - always check FO3 for problems by running it prior to modding it. That way you know for sure that FO3 does launch / work before you start adding more complexities to the troubleshooting.

Check out: http://www.tweakguid...Fallout3_1.html (long read but more than worth it) Always cover the basics (these are the most common causes of start up CTD's): - Do you have a legal copy? There are known issues with dodgy copies out there and we won't support those who pirate. - are you patched to 1.7? - upgrade / remove G4WL (Games for windows Live) - Personally I remove it - if you have a multi-core CPU have you modified your fallout.ini for multi-core CPU - have you done a default install (e.g. installed to C:\Program Files\.... ) and you run Win7 / Vista - if so uninstall and reinstall to a directory outside of C:\Program Files (e.g. C:\Games): Note that the this doesn't always fix start up CTD's but if you mod it's really a must do because of issues with UAC. - check your drivers and update where necessary. Note that some video driver versions can cause or introduce more problems than they fix - these are usually in game problems (e.g. stuttering, fpx, etc) - turn off all autosave features and either use CASM or manually save. (not suspected of causing of start up CTD's) Last but not least - always check FO3 for problems by running it prior to modding it. That way you know for sure that FO3 does launch / work before you start adding more complexities to the troubleshooting. (Yes - this is my stock standard reply and I simply cut and paste it now)

How about some basics? - load order - hardware - OS - are you patched

Check out: http://www.tweakguid...Fallout3_1.html (long read but more than worth it) Always cover the basics (these are the most common causes of start up CTD's): - Do you have a legal copy? There are known issues with dodgy copies out there and we won't support those who pirate. - are you patched to 1.7? - upgrade / remove G4WL (Games for windows Live) - Personally I remove it - if you have a multi-core CPU have you modified your fallout.ini for multi-core CPU - have you done a default install (e.g. installed to C:\Program Files\.... ) and you run Win7 / Vista - if so uninstall and reinstall to a directory outside of C:\Program Files (e.g. C:\Games): Note that the this doesn't always fix start up CTD's but if you mod it's really a must do because of issues with UAC. - check your drivers and update where necessary. Note that some video driver versions can cause or introduce more problems than they fix - these are usually in game problems (e.g. stuttering, fpx, etc) - turn off all autosave features and either use CASM or manually save. (not suspected of causing start up CTD's) Last but not least - always check FO3 for problems by running it prior to modding it. That way you know for sure that FO3 does launch / work before you start adding more complexities to the troubleshooting.

Are you running a multi-core CPU - if so check out: http://www.tweakguides.com/Fallout3_10.html

If you haven't patched FOOK2 correctly then your going to have issues - make sure you follow the instructions to the letter.

Do you have a multi-core CPU? - if so have you changed the fallout.ini file to reflect this? Check out: http://www.tweakguides.com/Fallout3_1.html Long read but worth it - multi-core cpu fix is on page 10 (I think).

Suggestions: - definetly defrag - use a third party one - Windows utility is okay but you won't get the performance back like you would with a third party one - there are a number of free ones out there. Fragmentation is one of the killers for FO3 performance. - Stop all unecessary background processes - it sounds to me like something is running in the background and grabbing too many CPU cycles or memory which is dragging FO3 down. What your proably seeing is not losing control of you character but delayed key strokes finely getting processed. I'd suggest finding a good guide on what services you can disable. I know many on this forum will basically turn off everything they don't need (wireless, network, search, etc) to get maximum memory and performance. You can try a utility like "Game Booster" (free version available) which will basically shutdown all non-essential services for your gaming session. I've tried it and it's not bad.

Have you installed FO3 to the default directory? (e.g. C:\Program Files (x86).........)..?? Sounds like it's a UAC problem - highly suggest if you have to uninstall and reinstall someplace like C:\Games or something like it (another words custom install and put it in a different directory. Basics; - If your running Vista / Win7 the game will default install to C:\Program Files....... This is a problem as UAC can interfere with the setup of mods in the future. If you haven't got a game running right suggest you uninstall and reinstall to a different directory (something like C:\Games). Uninstalling has it's own issues and you should search the forum here as there are already a couple of good guides for that. (I think someone posted a 'utility' on nexus that does it in one hit but can't find it at the moment) - Make sure you patch the game to 1.7 (latest FO3 patch) - Update your drivers - however be aware that some versions of drivers can introduce problems as well (e.g. NVidia - there a couple of versions that caused more problems than fixed). - Update or remove G4WL (Games for Windows Live) - Personally I remove it and you don't really need it, see this: http://fallout3nexus...ile.php?id=1086 - Check out this guide for great tips: http://www.tweakguid...Fallout3_1.html in there you can find the 'multi-core CPU' fix which is a must if your running a multi-core CPU - make sure to use FOMM to help manage your mods and you may need FOSE as well for some mods, if they need it they should state in the readme file. That should get you started for the moment. Let us know if you still can't start after you work your way through some of that. PS: Your Fallout.ini file should be in C:\Users\%username%\My Games\Fallout3 folder if your running Win7 - sorry can't remember where for the other OS's at the moment but I know it's in that tweak guide.

Sounds like a mod that is specific to Megaton then - perhaps your loading Lings Pretty Things or similar (Project Beauty) would be another. If so it sounds like you haven't installed the mod correctly, try reinstalling. Last but not least posting your current load order is always best when asking for help - otherwise we're just all guessing what the problem is / could be.

That'll teach me - I failed to go to the end of the thread - so apologies this should have been posted eariler. To answer your question about save games - yes they can cause problems especially when you make major changes in the background and sometimes FOOK2 qualifies for that. The best thing to do if you want to use a previous save is the old "hide out for 3 days" trick. This is where you go to a empty cell (someplace like the toliets at Megaton - i.e. a small room where NPC's won't venture) and then kick the clock up so that time passes faster (or use the Wait function) and stay there for 3 days. The game resets all cells every 72 hours. This does not always work though and the only true method is to start a new game. Below was my orginal reply to yours on the previous page. Whoa there big fella...!!! Hmm not sure where your seeing that load order at, but first a quick history lesson (PS: I'm not an historian so this may not be 100% accurate but you'll get the gist of it); - FOOK2 was originally started and released by a group of modders (V1.0) which is the stand alone .exe you have already seen and installed. Unfortunately it wasn't as polished as first thought and had quite a few show stopping bugs in it. Most (if not all) of the original group gave up or moved on and it laid there until another like-minded bunch picked it up and decided to fix it all and add even more to the original. It was decided to drop the original .exe concept but since a lot of the 'core' files were already there it's being used as a 'base' install and hence the reason for the hugely convoluted install process. Once the final realease has been finished the plans are to merge it into a more cohesive package (and hopefully shorten the current install / upgrade process). So this is why you have to remove all of the original esm's and esp filles, they have been redone and for the most part fixed. Thus endith the lesson. LOAD ORDER: Here's what I see on their web site; 1.1 Standard Load Order Official esms must be in the same order as here, and FOOK esps should always be last, again in the same order as here. Use any other mod at your own risks. Almost all Compatibility Patches were made for FOOK 1.0 and are now way outdated, and will kill your game. * Fallout3.esm * Anchorage.esm * Pitt.esm * BrokenSteel.esm * PointLookout.esm * Zeta.esm * Calibr.esm <other mods> * FOOK2 - Main.esm * FOOK2 - [DIK] DLC Improvement Kit.esm <other mods> * FOOK2 - Main.esp * FOOK2 - [DIK] DLC Improvement Kit.esp * FOOK2 Main [Hotfix].esp * FOOK2 DIK [Hotfix].esp If you dont own the DLCs, just remove anything DLC-related: * Fallout3.esm * Calibr.esm <other mods> * FOOK2 - Main.esm <other mods> * FOOK2 - Main.esp * FOOK2 Main [Hotfix].esp So as you can see there is no mention of the older files. Please take this the right way - try not to make it harder than it already is..... ;-) The reference to moving the DLC files is that when you install the DLC pack (Zeta, Anchorage, etc), depending on where they came from (Steam, separate disks, etc) they would be installed in a completely different directory than the original install directory, this was not a problem with the GOTY edition - so as you have already found out you can safely skip that step (e.g. check to see if they are there - yep their there - move on to next step). My fingers are crossed for you. And yes there is a mind controlling substance that is absorbed through the fingertips once you handle either the install media or the original game packaging. To end on a lighter note (actually sad note for me and it gives you an idea how bad that addiction can get). I too after playing through it all on XBox decided to try the PC version. In my early install / playing / modding days, I can safely say that I uninstalled and reinstalled so many times that I know the entire process and on-screen dialouges by heart, created so many characters that I could populate half of the lower east side of Manhatten, and crashed and burned so many times I turned to self-mutilation (not really but I wanted to). I'm a fan of FOOK2 and I can now run for hours continously without a CTD and it's not unusal to go weeks or months without a CTD. I've learned to have separate installs so I can do mod testing and one for actually playing and I'm a happy camper - I'm now eagerly waiting for my FONV to arrive and start the whole process all over again.

FOOK2 v1.0 is buggy as and incomplete - if you want to run FOOK2 your going to have to do some work (but well worth it IMO). Go here; http://www.yourfook.com/downloads/ and here (AND FOLLOW THE INSTRUCTIONS): http://www.fookunity.com/forum/showthread.php?t=4212 and then the latest hot fixes from here: http://www.fookunity.com/forum/showthread.php?t=4307 and no - don't install mods that are already included with a mod - it will stuff it.

Do you know which version of MMM your running? I remember seeing some discussions here where v6.0 (I think) was buggy and people were being told to wait for 6.1 (again only going from memory so please check). Custom race mods have been mentioned several times in regards to causing issues - try disabling and starting the game again.

I would suggest the following; - check drivers and update where necessary (Windows update may have updated or tried to your existing drivers - which were corrupted or even a version that is causing the problem). Check the update logs, etc - defrag your HDD - and use a good third party one not the in-built Windows one. - what if anything have you changed to your complete setup - e.g. new hardware, new HDD, etc. if possible reverse the change and try again. - run an extended RAM (memory) test - problems like you have described can quite often be hardware related and when really weird things happen RAM is a good place to start looking.

It could be as simple as: - load order out of whack - posting your load order would be a good start so we can see what you are trying to do. - if your running 150+ mods you're probably going to run into issues, although the limit is 255 the more you run the higher chance you have of these kinds of problems, you may want to consider culling it down a bit more. - are you running any 'large scale' mods (e.g. FOOK2, FWE, MMM, etc), these will often clash with smaller mods since they are trying to change the same thing. Also if you run something like FOOK2 and FWE together it won't work, another item you need if course is FOIP's for some mods to work together. So post your load order and then maybe we can help.

A copy of your load order would help.

Your FOOK2 installation is still hosed up my friend. Methinks you failed to follow their instructions (I admit their not great), here's a snippet; STEP BY STEP: * Install Fallout 3, patch it with the official Patch 1.7, and if you own the DLCs, move them from \Documents and Settings\Your User Name\Local Settings\Application Data\Microsoft\Xlive\DLC (Windows XP) or \Users\Your User Name\AppData\Local\Microsoft\XLive\DLC (Windows Vista & Windows 7) to your Fallout 3\Data folder. * Download ArchiveInvalidation Invalidated! (AII!) ( http://www.fallout3nexus.com/downloads/file.php?id=944 ) and install it. * Download Fallout Mod Manager (FOMM) ( http://www.fallout3nexus.com/downloads/file.php?id=640 ) and install it. * Download Fallout Script Extender (FOSE) - Strongly recommended - ( http://fose.silverlock.org ) and install it. * Download and install FOOK2 1.0. * Delete EVERY SINGLE 1.0 plugins. *censored*, EVE, Mothership Zeta plugins, the main esms, remove them ALL. * It is advised that you use a clean install and a new game, rather than continuing a save from previous versions - otherwise many of the fixes may not work. * Download and install the new 1.1 Beta 2. * Use Fallout Mod Manager to arrange your load order (see Standard Load Order below) and to launch the game with FOSE. And RECOMMENDATIONS: * Be careful to remove *censored*, EVE and all the other FOOK2 plugins / fixes. They are now integrated into FOOK2 - Main.esm. * DIK now require Mothership Zeta to launch itself. * Be careful of outdated Compatibility Patches and plugins. WMK-FOOK2 plugin was already too old for FOOK2 1.0, and wasn't compatible with the EVE Plugin (which has now been merged). Outdated plugins may crash your game. * Major mods added to FOOK2 1.1 are EVE, Phalanx, DLC Refurbished, AMPUTATE, Selected Containers Respawn, Melee Lock-On, Fellout, Streetlights mod. You must remove those mods from your load order before using 1.1. * Be careful if you are using the Unofficial Fallout 3 Patch to load it before FOOK esps. Note that the UF3P Broken Steel patch may be crashing your game, with or without FOOK. * Be careful with the Destruction mod, as some of its plugins require *censored* as a master - master that don't exist anymore in 1.1. The best solution is probably to remove Destruction until a proper update is made to the mod. * It is highly advised to remove FOOK2 & DIK 1.0 from your load order, to wait with your savegame in an empty cell for four days, and then to activate FOOK2 1.1 if you dont want to create a new character. Check the credits for other incompatiblies that may happen with 1.1. * Be careful to have your game updated to official patch 1.7, and your FOSE to at least v1.2b. * Remove anything of value from the Amata, Brianna, Lucy West and Colonel Autumn followers before to install FOOK 1.1. They are removed from the mod. The Brianna and Lucy West should be generally usable by loading the original mod. Amata and Colonel Autumn will break the other followers dialogue if they are loaded, however. * Follower overhaul mods are not likely to play nice with FOOK. * Mods which make modifications to vanilla followers may make the follower not obey commands. If this happens, the author making a FOOK-specific version of the mod (when FOOK it is out of beta) should rectify this. * Some mods which add followers will break Malcolm, Deisha, and K-9, and mess up the dialogue for the other followers. This indicates a design problem with the other mod, if this happens. What you still have are all of the original FOOK2 esm / esp's loading (e.g. World and Neighborhood Kit, MyFook, on and on). And of course this is why your having problems. Now you can find all the information here: http://www.yourfook.com/downloads/ And here: http://www.fookunity.com/forum/showthread.php?t=4212 And here: http://www.fookunity.com/forum/showthread.php?t=4307 I personally use FOOK2 and it does work - sure there are bugs at times but it's a large mod and the guys are trying to fix it all - with that said I haven't had any issues for ages with it. Sorry to hear about all the drama's - I can sympathise since I had similar issues after deciding to try FO3 on the PC ages ago - several hardware failures and other upgrades later......

Do you have it installed to your C:\Program Files? If so UAC may be stopping it - can't test at the moment but if you right-click on the exe and select properties you may see that the file has been blocked by UAC. If you are in C:\Program Files I would suggest a uninstall and fresh install to another directory - UAC can ruin your day when you start adding mods.

No worries, Aha - from memory that's a laptop with integrated graphics (simply means you don't have a dedicated graphics chipset). Sorry to tell you but it won't run on that particular hardware. FO3 is pretty graphic intensive and although a huge beefy video card isn't required you do need a decent one to start and continue running it. Most laptops don't have a dedicated GPU and you can usually easily tell as there will be a sticker (AMD or NVidia) on the laptop - there also a bit more in price. Again sorry mate but your outta luck on this one.

Your also running FWE and FOOK2 together which won't work either - their not compatible and you'll find heaps of others on here who have tried. Pick one or the other and go with it or your going to be seeing a lot more problems as you progress through the game.

And no - Win7 wasn't officially out yet when the game was released - with that said I run it on Win7 x64 without any problems.

Which version of FOOK2 are you running? There are known issues / bugs with some of the older versions especially with leveling up - check here: http://www.yourfook.com/downloads/ - and here: http://www.fookunity.com/forum/showthread.php?t=4212 - and here: http://www.fookunity.com/forum/showthread.php?t=4307 make sure you follow the instructions.

I would suggest you patch to 1.7 not 1.5 - still heaps of issues in 1.5. Your FOOK2 installation is hosed - you've got a mixture of v1.0 and v1.2 - go to: http://www.fookunity.com/forum/showthread.php?t=4212 make sure read the instructions carefully (yeah their not great). Basically you need to remove all of the old esm's and esp's that were part of 1.0. Also make sure to get the latest hotfixes here; http://www.fookunity.com/forum/showthread.php?t=4307 The version of FOOK your basically running was bug ridden and well known to be - hence the reason the team over there is trying to fix it all up. Good luck.