anokii

Some suggestions: - are you running a multi-core CPU? If so you need to modify your fallout.ini file. Apolgies but I can't remember the exact change but if you look at this: http://www.tweakguides.com/Fallout3_10.html - under the heading "Update" in bold you'll see the change you need to make. (BTW: the guide is quite good and has heaps of other ideas as well) - I've found weather mods to sometimes cause issues especially when exiting or entering a building but that's usually a crash. - exiting CTD's are common and usually related to the autosave feature - turn it off and use someting like CASM and you might find that clears the problem.

You'll need the FOIP patch for MMM & FOOK2 Sounds like you may have a corrupted save file - try to restore an older save (as sad as that is) - also turn off autosave complely as this typically causes more issues. You can access the autosave features from the main menu. May want to check out CASM for saving as it lets you have multiple profiles. As silly as it sounds (and yes this does work and yes I've tried it myself): If you have a save that is constantly crashing after loading it have your character commit suicide - the game will restore back to where the save was but creates a new save file. Believe it or not this will get rid of these issues. I know it's strange but I use FOOK2 often and have experienced identical problems with saves. Last but least check: http://www.fookunity.com/forum/showthread.php?t=4307 for the latest patches for FOOK2 - there was a documented fast travel bug in v1.0 and it has reappeared from time to time with the new devlopement that is going on.

Another thing to check - compatibility of some of those smaller mods you have with something like FO3. FO3 has lots bundled into it and you may be duplicating some of that which can cause CTD's. I've also heard that MMM RC 6.0 has some issues at the moment but you may want to check that.

Try reinstalling 1.7 patch. Download it from Bethedsa and install it. 1.7 patch is included on disk 2 of the GOTY edition and is supposed to install automatically. I found with my copy that it would but for some reason stuff it. Reinstalling the patch manually fixed it. PS: if that doesn't work try patching or removing G4WL (Games for Windows Live). I seem to recall that this has been reported as a problem with disk 2 as well.

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 CTD's): - are you patched to 1.7? - upgrade / remove G4WL (Games for windows Live) - 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 UAC. See how you go with those and let me know.

Things to try: - Check out http://www.tweakguides.com/Fallout3_1.html long read but worth it, heaps of info about tuning - in there you will also find the ini fix for multi-core CPU's (you need to add a line which I can't remember right now - multi-core CPU's can CTD the game) - your patched to 1.7 yeah? - you don't say much about your video card? If it's on-board and not a dedicated graphics GPU you'll never get decent performance without dropping everything to low in graphics. FO3 is pretty graphic intensive and will be crippled with anything less than a good medium class graphics card. - if you do have a dedicated graphics card (NVida or ATI) - check your drivers, I've personally experienced issues with drivers.

Means your missing meshs/textures - are you absolutely sure you installed the mods correctly...? (typically people forget to copy all of the files across from a mod) You may also have gotten a corrupted mod. Try installing the mod again and following the instructions carefully.

FOOK2 (v1.1) has the Phalanx mod which is a companion mod, it can conflict with other companion mods so care should be taken and personally I wouldn't use any other follower mods with FOOK2. Hmm, load order looks okay - have you checked FOOK2 for the latest patch/hotfix? http://www.fookunity.com/forum/showthread.php?t=4307 If your good to go as far as FOOK2 is concerned I'd try a merge patch - can sometimes fix these little issues. Oh yeah - you could always talk to Gary (avatar for the Phalanx companions - outside Megaton ) - in his dialog you can find some troubleshooting topics and some reset topics. There's also some advanced scripting you can run from the dialog and run some checks on the mod.

Wow - methinks you have too many mods there - yes the limit is 255 but the more you add the more problems your likely to encounter. I would seriously consider chopping your list back. There are known issues with [ahem] Animy_prostitution.esm and user dialogs sometimes screwing up, considering some of your other mods I think you've got a conflict there and will have unless you scale back. You could always try a merge patch which sometimes works, but with all those masters (esm's) I wouldn't count on it. Actually looking at your load order again and I'm almost sure you have some conflicts there. Good luck.

Yeah the 'flickering' problem I've seen and still occassioningly experience as well. Never have figoured out the cause except I reckon that it's got something to do with how the mesh was made. Sounds like it may be a bug with Zeta Crew or one of the mods for Zeta. Perhaps check with the author?

Right, this (random CTD) is one of the reasons I stopped using FWE and went back to FOOK2 (also didn't like all that realism garbage - yes I know you can turn it off... ;-) What your describing seems to be isolated to the save game, so then you can try what I'm calling the "Twlight Zone fix" - I have used it and it does work, sounds strange as hell but it does. - load up your last save - go somewhere quiet (e.g. hill above Megaton, etc) - suicide your character - easiest way is to drop a couple of frag grenades at your feet (careful if your on a hill they will roll away) - your game will reload from the exact same area of your last save - now go and try the locations where you CTD - you won't lose anything (including frags since your restored back to before you blew up) Again very strange fix I know but apparently it has something to do with items loaded into memory from the save file, your character dying wipes this clear. I've tried to figure out the techical details but I'm a hardware tech not a programmer. One last item - have you turned off Autosave? This is known to be an issue with some setups and again it's recommended that you disable autosave features and use something like CASM or manual saves only.

You've got some load order problems as well. Golden Rule: Always load esm's before esp's, you've got your Project Beauty esp files loading too soon, move them down and double check the rest. - your running FWE and FOOK2 together - ain't gonna work. These two mods are not compatible as they both try to do similar things (e.g. major game play changes), Suggest you pick one and stick with it or you will have problems in the future. Some people will tell you they will but not really and more importantly not reliably. - Looks like your FOOK2 install is hosed as well - your runing a mixture of v1.0 and v1.1 files - suggest you follow the instructions here: http://www.fookunity.com/forum/showthread.php?t=4212 or again you'll have problems later on. I'd almost bet your 'missing textures' are a result of the motched FOOK2 installation. Good luck.

Here are my personal experiences; - If your running one of the real large mods (FWE, FOOK2, etc) you will find that there are 'bugs' in areas where you will be prone to crashes (CTD's). In particular I found once in a certain area I would continually crash - through continous trying I finally found that there was a Mr Gutsy in the area and when he fired his plasma weapon I would crash - this was related to EVE and FOOK2, to get past it I grabbed a previous save and entered the area from another direction - problem solved (and I nuked the Mr Gutsy). - FOOK2 as an example had serious problems in v1.0, fast travel, certain areas, Rivet City, and even leveling up would cause a CTD. The latest version has cleared them all. - One I can't prove is weather changes - I swear that when you use some of the weather mods you will CTD more, seems to happen when the weather changes, whether it's a script problem or what I couldn't say but it seemed to me to be an issue. - Last but not least you could be experiencing issues as a result of a corrupted save, multi-core bug or other issues. Take a look at this; http://www.tweakguides.com/Fallout3_1.html it's a long read but well worth it - has a good troubleshooting section and lists the multi-core CPU fix. See how you go and if you need more let me know.

Autosave crashes are pretty common mate - now stand by for an absolute strange possible fix. - as silly as it sounds kill your character - yse that's right suicide your character. Best way is to just drop some frags at your feet, I know your thinking "this guy is nuts". However it is a proven method to get past a corrupted save game profile which is what's happening to you. I didn't believe it the first time someone told me but it does work and worked for me with an indentical problem. PS: You may want to turn autosave off as this is a known problem - I personally use CASM and only quicksave. Do some searches and you'll see that it is a known problem.

What your asking for is equivalent to piracy which isn't tolerated here. Suggest you drop this real quick.

Yo guys - your running an older version of FOOK2 (v1.0) and this was a documented bug "crash on Rivet City Entry", I would suggest upgrading to the latest build which gets rid of a lot of other bugs as well (level up freeze, etc). Check out: - http://www.yourfook.com/downloads/ - http://www.fookunity.com/forum/showthread.php?t=4212 - http://www.fookunity.com/forum/showthread.php?t=4307 Install instructions (link 2) are painful but make sure to follow them exactly or you will have even more issues (key point being to remove all of the original esm's and esp's) PS: You'll need a FOIP for MMM to work properly with FOOK2: http://fallout3nexus.com/downloads/file.php?id=4968

Just remembered - FWE has all that guff about essentials (food rest, water, etc) - could it be you that feature enabled and your character is simply passing out from lack of something? (I know it sounds silly but when I thought of it, it sounded better).

I seem to recall this was an issue with NVidia based cards but I thought it was fixed. You running a NVidia card by any chance? Opps one more thing; you running any NPC mods (e.g. Project Beauty, Lings Pretty Things, etc)?

Had similar problems and definitely was the NVidia driver at the time - ended up going all the way back to 186.16, although I am running 258.96 and its stable. Always cover the basics (these are the most common causes of start CTD's): - are you patched to 1.7? - upgrade / remove G4WL (Games for windows Live) - 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 UAC. and Check out: http://www.tweakguid...Fallout3_1.html Long read but well worth it

Check out: http://www.tweakguides.com/Fallout3_1.html (long read but more than worth it) I think he mentions SLI in there - I'm sure I saw somewhere that it is a pain to get up and running and from memory drivers were the big issue. Always cover the basics (these are the most common causes of start CTD's): - are you patched to 1.7? - upgrade / remove G4WL (Games for windows Live) - 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 UAC.

Yep - man you have some problems there; - Your running FOOK2 and FWE which will cause you problems - two major overhauls like those just don't work together. You'll need to decide which one to use, once you do stick with it and clean your load order accordingly, also both of these add heaps of changes and as such incorporate other mods, I think you've got some individual mods which are already included with either FWE or FOOK2 already and that as well will cause you problems (e.g. streetlights). You've got others as well; slower degradation, explosive entry, etc, etc FWE and FOOK2 has an extensive configuration menu in game to modify game aspects such as these - suggest you check their readme's and websites as well. I think you'll find you can drop over half your load order and get a smoother / better experience. - Your FOOK2 install is hosed. Suggest you fix that if you plan on staying with it (latest info: http://www.yourfook.com/downloads/ and http://www.fookunity.com/forum/showthread.php?t=4212 and http://www.fookunity.com/forum/showthread.php?t=4307 ) Basically you've got esm's and esp's from v1.0 still referenced and active which should have been deleted when you upgraded - follow the installl instructions. - I'm pretty sure you load order is less than optimal as well but to tell the truth I'm not 100% familar with some of them. Your biggest problem is the larger mods (FWE, FOOK2, XFO). - I don't see many FOIP patches - you'll need them to get some of those to work together nicely. As for your base problem with missing texture I'd suggest that when you were installing your mods you overwrote one of the texture files that were needed - as an example both FWE and FOOK2 add heaps of new weapons and textures to which you have Hi-Res Weapons installed as well - this may have overridden a texture that's now needed. Note: Arwen's mods are not compatible with FOOK2 at the moment unless she's just fixed them. Personally - scrub and start again as painful as that might be - sorry.

Umm - Archive Invalidation shouldn't cause any CTD's, it's simply changing the ini file for you. And all this is just telling the game engine to ignore the precompiled files and load them direct from the Meshes / Textures folders. If this isn't done or setup properly the game doens't know about the new textures and meshes and throws up the exclamation point. So usually this is caused by; - mod not properly installed - e.g. meshes and textures folders were not copied to the data directory from the mod - Archive Invalidation not done properly and the game doesn't load the new files - side note: if your running Win7 / Vista and you've installed to the default directory (C:\Program Files), UAC will cause problems and mods may not install properly - highly recommend you uninstall and reinstall to a new directory like C:\Games or something. You can always check out: http://www.tweakguid...Fallout3_1.html Long read but well worth it

Always cover the basics (these are the most common causes of start CTD's): - are you patched to 1.7? - upgrade / remove G4WL (Games for windows Live) - 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 UAC. and Check out: http://www.tweakguid...Fallout3_1.html Long read but well worth it

Yep - you got problems; - Your load order is out of whack - golden rule = ESM's should always be loaded before ESP's, and you need to sort it out, you can try: http://fallout3nexus.com/downloads/file.php?id=10193 (does a decent job but the install is just a tad tricky for newcomers). Basically your load order is all over the shop and your going to run into huge problems if you don't fix it up. - Your running an older version of FOOK2 (v1.0), this release was well known to be buggy and cause CTD's. Suggest if your going to keep it to go to: http://www.yourfook.com/downloads/ and: http://www.fookunity.com/forum/showthread.php?t=4212 (read the install very carefully and follow the steps as is - failure to do so will cause you more grief), and then go to: http://www.fookunity.com/forum/showthread.php?t=4307 and get the latest patches. - Check compatibility of your mods - some of the ones you have listed are already in FOOK2 (EVE as an example) so your doubling up which will cause problems. - I don't seen any FOIP patches for the large mods either like MMM and FOOK2 - Personally I would drop the Unofficial Patch - Broken Steel this is has been known to cause some issues. - Personally I would consider using a merge patch with that large of a load order. That should get you started.

Sorry should have posted this earlier in the piece; Always cover the basics (these are the most common causes of start CTD's): - are you patched to 1.7? - upgrade / remove G4WL (Games for windows Live) - 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 UAC. and Check out: http://www.tweakguid...Fallout3_1.html Long read but well worth it