prensa

adouglas4312 - Hello! "I re-installed it and it worked." Glad you got it working! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ LordWushin - Hello! "When I click the download link all I get is a jumble of odd symbols and no download or anything." Try right clicking on the link & select "Save Link As" (Firefox) Or "Save Target As...." (IE) Or if that still does not work just copy & paste the download link into your browser's address bar press enter: http://fose.silverlock.org/download/fose_v1_2_beta2.7z Hope this helps! Prensa

burnoutspartan - Hello! I've never had a freeze in Arlington Library. Does the game freeze only in Arlington Library? Or does it happen elsewhere, in small interiors, locking up & then CTDing? Are you running Fallout 3 on a multi core? If so, it could be the Fallout 3 multi core bug. Fallout 3 has trouble with multi core computers, mainly with ones that have more than two cores & use hyperthreading. You need to edit your .ini, the one you want to change is in: For XP: My Documents\My Games\Fallout3\ For Win7: Documents\My Games\Fallout3 & change this line: bUseThreadedAI=0 to: bUseThreadedAI=1 & insert this line under it: iNumHWThreads=2 Save & close your ini. Hope this Helps! Prensa

adouglas4312 - Hello! Has your mouse got a configuration menu? Many mice have one, usually down at the bottom of the taskbar in "Hidden Icons". Or maybe a desktop icon? If you're running Win7, typing: mouse In the Start Menu's Search Box should bring it up. If you can find it, it may have a "Game Setting" section. In my Setpoint Menu it's a chess piece. Within that you can enable game detection & can tell the mouse to enable/disable certain functions of the mouse buttons when you're playing games. This may help fix your problem. Hope this helps! Prensa

Killzone51 - Hello! Some people do have trouble with quicksaves. Glad you got it sorted! :) Prensa

Killzone51 - Hello! Is it just your mouse that slows down, or the whole game? If it's just the mouse that slows, have you increased this setting in your graphics card control center (like ATI Tray Tools or CCC etc): For Nvidia cards - Maximum Pre-rendered frames or For ATI cards - Flip Queue From their defaults of 3 or Undefined? If you have altered them by raising them, return them to the default of either 3 or Undefined. If you haven't touched them before, try a lower number than 3. If this does nothing then return those settings to default (3 or Undefined). It could also simply be caused by playing at too high settings for your system. A high screen resolution can be taxing & Anti aliasing eats FPS for breakfast. Pushing either of those can cause mouse lag during busy moments. Have you got the mouse Acceleration fix in your .ini? It's more of a sluggish mouse than a slow down but worth checking. Directly under [Controls] add these lines if they are not there to fix it: fForegroundMouseAccelBase=0 fForegroundMouseAccelTop=0 fForegroundMouseBase=0 fForegroundMouseMult=0 (If you don't know where your .ini is, skip down below for directions). If it's the whole game slowing down, have you done any .ini tweaks? Specifically have you altered the default setting of: iFPSClamp=0 For example, did you change it to: iFPSClamp=60 As, although it can fix stuttering, it will cause slow downs when you get busy moments in the game like combat. ensure that .ini setting is set to 0. The one you want to change is: For XP: My Documents\My Games\Fallout3\ For Vista & Win7: Documents\My Games\Fallout3 The file you want will be called: FALLOUT.ini Check the .ini with Notepad. Hope this helps! Prensa

RavveN - Hello! Do the CTDs happen when you just run Fallout 3 & the DLCs with no mods? If you haven't tried without mods do so. If you don't get the CTD problem with your mods turned off it points to one of them being the cause or at least clashing with another. If that's the case turn your mods back on one at a time, checking between easch to see if the game still runs fine. As soon as you hit the CTDs again you'll know which mod is the culprit. I'm pretty sure an Athlon 64 3700+ is a single core processor so I'd be surprised if it was the Fallout 3 multi core bug. Does the game freeze mainly in small interiors, locking up & then CTDing? Fallout 3 has trouble with multi core computers, mainly with ones that have more than two cores & use hyperthreading. But like I say, I'm pretty sure the Athlon 64 3700+ is a single core. You could try the fix, you need to edit your Fallout 3 .ini file. The one you want to change is: For XP: My Documents\My Games\Fallout3\ For Vista & Win7: Documents\My Games\Fallout3 The file you want will be called: FALLOUT.ini Open the .ini with Notepad & change this line: bUseThreadedAI=0 to: bUseThreadedAI=1 & insert this line under it: iNumHWThreads=2 Save & close your ini. Hope this helps! Prensa

Commander19 - Hello! Sorry, I'm not an expert on the GECK but there was a bit of discussion about a bug in Orthographic Mode here: http://www.thenexusforums.com/index.php?/topic/123163-sigh-yet-more-geck-stupidity/ I don't know if it's the problem you're having.... Hope it helps! Prensa

Yes, the Microsoft official line is that Fallout 3 is not compatible with Windows 7, to be fair, this is the same line that Bethesda takes: http://fallout.bethsoft.com/eng/info/faq.html Does Fallout 3 Support Windows 7? Fallout 3 is not an officially supported title of Windows 7. It should not be taken seriously though, what it really means is - we can't be held responsible if it does not work! After all Fallout 3 was made prior to Win7. Like I said & others on here too, it works very well on my Win7 64 bit. & that's both before the service pack & after. I even run it with the highest settings. The thing Fallout 3 really seems to have trouble with are hyperthreaded multi cores especially those above two cores. Fortunately there's an .ini work around for that. :) Prensa

Glad it helped! :) The freeze CTD bug can be surprising as it actually affects more powerful computers (multi core). My older dual core was fine, I only had trouble when I got a quad core. Fortunately the .ini tweak works. :) Prensa

ianwienpien - Hello! "How do I update the maserlist.bat?" To update your BOSS master list just double clicked on: BOSS - Update Masterlist.bat It should be in your Fallout 3 Data folder alongside the BOSS.exe. The actual list will be stored in a folder that BOSS creates in the Fallout Data folder called: BOSS Once you've run "BOSS - Update Masterlist.bat" you then run the "BOSS.exe" & that will sort your mods. Hope this helps! Prensa

Flopsies - Hello! I've not heard of any vanilla bugs related to Rockland Car Tunnel. The only thing I can suggest is some basic troubleshooting. Make sure it's not your save, try a slightly older save & see if that works at Rockland Car Tunnel. Try turning off autosave on travel in the Fallout 3 Settings menu, it might just be the save that's made upon exiting doors that's causing the CTD. Maybe it's related to the mods you are using. Try & exit with only Fallout 3 & the DLCs running & see if you get a CTD. If you can exit Rockland Car Tunnel fine with just Fallout 3 & the DLCs in you'll know it's caused by one of your mods. Turn 'em back on one at a time, checking in between to see if the CTD on exiting Rockland Car Tunnel returns. That way you can identify the culprit. Hope this helps! Prensa

tayler44 - Hello! That's an Oblivion Mod that you've linked too. I think you will have more luck in the Oblivion Tech Support section here: http://www.thenexusforums.com/index.php?/forum/179-oblivion-technical-support/ Hope this helps! Prensa

ianwienpien - Hello! Have you double clicked on BOSS - Update Masterlist.bat? You have to do that before running BOSS.exe for the first time or else it will have no list to read. Also ensure BOSS is in your Data folder. Click on the BOSS - Update Masterlist.bat from time to time to get the very latest list from the web. Hope this helps! Prensa

daninthemix - Hello! Did you try this from my first post: "You'll have to try a bit of troubleshooting. Try running Fallout 3 with all your other mods unticked. If it works fine with the other mods turned off, you'll know one of the them is the culprit. Turn them back on one at a time, checking in between in game to see if the problem returns. That way you can track down the mod causing the problem." Because if the CTD problem goes away when you just run Fallout 3 you'll know it's a mod causing it & turning them back on one at a time will allow you to determine which one. Also a question, are you using some kind of extended .ini? There's a of a lot of stuff there I've never seen before. Particularly under [Pathfinding], [HAVOK] & [MAIN] plus others. I recognise DARNUI edits in [Fonts]. You should move that .ini into a backup folder & then run Fallout 3 & so it will recreate your .ini in the default style. See if the CTDs still occur with the default .ini. Don't forget if you stay with the new .ini you'll have to make those DARNUI [Fonts] changes again. If that still does not fix it, you can always drop that other .ini back in. Hope this helps! Prensa

daninthemix - Hello! Are you using Fallout Stutter Remover 4.0.7? I do notice, in your sr_Fallout_Stutter_Remover.ini, you're using the Heap replacement: bReplaceHeap = 1 The Fallout Stutter Remover 4.0.7 ReadMe says: "Section: Heap{} This stuff does not really work for Fallout yet. Do not use. " Turn it off by setting it to: bReplaceHeap = 0 & see if that stops the CTD problem. Hope this helps! Prensa

daninthemix - Hello! I see you're using Apocalypse Armory, great mod, did you use the V191_BETA_COMPLETE pack? If you did, you MUST have the new .esm & .esp from V193_UPDATE. It fixes a CTD bug that was in the 1.91 version. To check the patch has taken, open up FOMM & left click on Apocalypse Armory.esm & make sure it says 1.93 down at the bottom of FOMM. Do the same for Apocalypse Armory.esp, if either say 1.9, 1.91 or anything other than 1.93 you've got the old files in still. In that case drop the Apocalypse Armory.esm & Apocalypse Armory.esp from V193_UPDATE into your data folder, saying yes to overwrites. Note that only the Apocalypse Armory.esm & Apocalypse Armory.esp will say 1.93 Beta. The Apocalypse Armory patches will still say 1.9, that's perfectly normal. You can get the Update at Apocalypse Armory on the Nexus: http://www.fallout3nexus.com/downloads/file.php?id=14773 If you do have Apocalypse Armory version 1.93 then all is well with Apocalypse Armory. You'll have to try a bit of troubleshooting. Try running Fallout 3 with all your other mods unticked. If it works fine with the other mods turned off, you'll know one of the them is the culprit. Turn them back on one at a time, checking in between in game to see if the problem returns. That way you can track down the mod causing the problem. Obviously, certain mods require others to work so turn them on together when checking. Hope this helps! Prensa

palmbay45 - Hello! Have you taken care of Archive invalidation? Affects all mods that add textures. Unless taken care of new textures will change textures like chameleons! Either download & activate: ArchiveInvalidation Invalidated http://www.fallout3nexus.com/downloads/file.php?id=944 Or, if you use FOMM click on Toggle Invalidation on the right. Hope this helps! Prensa

DonVitoo - Hello! Sounds like the Fallout 3 multi core bug. Does the game freeze mainly in small interiors, locking up & then CTDing? Fallout 3 has trouble with multi core computers, mainly with ones that have more than two cores & use hyperthreading. There is a fix, you need to edit your Fallout 3 .ini file. The one you want to change is: For XP: My Documents\My Games\Fallout3\ For Vista & Win7: Documents\My Games\Fallout3 The file you want will be called: FALLOUT.ini Open the .ini with Notepad & change this line: bUseThreadedAI=0 to: bUseThreadedAI=1 & insert this line under it: iNumHWThreads=2 Save & close your ini. Hope this helps! Prensa

ricmoors - Hello! I'm running Fallout 3 on a Win7 Home Premium 64-bit Operating system & in the default folder in Program Files (x86) with no trouble. Can I just get a few things clear first, you're instaling Fallout 3 from a disc? It's just you mentioned Steam. The GOTY disc does not need any more official patching, it should already be 1.7.0.3. If you've installed from disc into the default directory it should be in: C:\Program Files (x86)\Bethesda Softworks\Fallout 3 Go to that location & look at the files & folders. Do any of them have little padlocks on them? If so, drag the affected files/folders onto your desktop & move them back again. Are you using Fallout Mod Manager (FOMM)? http://fallout3nexus.com/downloads/file.php?id=640 It will really help you out with using mods. If you don't have New Vegas, just get "Old FOMM". Once installed, you can check that your load order is correct. As others have said on here, Fallout 3 crashing on startup is often due to a missing master (.esm) file. Make sure in FOMM that your load order is Fallout3.esm FOLLOWED by the DLC .esm files. I don't use G4WLive & it gave me problems when I tried installing the DLCs & stopped Fallout 3 from running with them, fortunately FOMM has a workaround. In FOMM go to - Tools - Install Tweaker & tick the box next to "Use fake XLive.dll" & see if that helps you to run Fallout 3. Hope this helps! Prensa

CliffordConan - Hello! "now that I've reinstalled it, it doesn't have the normal Fallout 3 icon but the generic thing for an icon" Do you mean the Fallout 3 shortcut that you click on to launch the game? Just right click on the icon & select - properties. A window will open, down at the bottom of that will be "Change Icon", select it. Another window will open, if the Pip-Boy icon isn't shown there click on Browse & navigate to where your Fallout 3 is installed & click on one of the Pip-Boy icons in there & click OK. This should change the icon back to the normal Pip-Boy face. Hope this helps! Prensa

BlackRampage - Hello! You beat me by a few minutes! You must have got your reply in just as I was doing mine, I must be getting slow.... :) I think your right about Vista saves being the same location as Win7 too. Prensa

CliffordConan - Hello! I don't use Steam so I'm not sure if the savegames are stored elsewhere with that setup but normally all you'd have to do is move your savegames back into: On Win7: C:\Users\ YOUR NAME \Documents\My Games\Fallout3\Saves On XP: My Documents\My Games\Fallout3 & you can play as normal. Hope this helps! Prensa

OversleptAgain - Hello! You can use the console to exit Hamilton's Hideaway. Open the console by pressing the key under Esc & type ONE of these: coc megatonplayerhouse coc megatonmoriartyssaloon coc tenpenny03player This will get you out but you should try to get to the bottom of the problem. It could be a mod causing the trouble. You could check FO3Edit to see if any of your mods are changing something in Hamilton's Hideaway. Get FO3Edit here: http://www.fallout3nexus.com/downloads/file.php?id=637 Run FO3Edit, it will present you with a list of your mods click OK. In the "Editor ID" search box at the top type: hamilton FO3Edit should now jump to Hamilton's Hideaway & be displaying it's details in the right window. Note that all mods making changes to Hamilton's Hideaway will be displayed in columns starting with Fallout3.esm. If any other mod is listed after Fallout3.esm make note of it's name & close FO3Edit. Disable the mod you made note of in FOMM & see if you've fixed your CTD on exiting Hamilton's Hideaway. If that does not solve it or you couldn't find any other mods directly altering Hamilton's Hideaway then you're going to have to do a bit of trial & error. Untick all of your mods & run with only Fallout 3. If you can exit Hamilton's Hideaway without CTD then you will know for certain it's a mod causing it. Turn back on your other mods one at a time, checking in between to see if you can still exit. This way you will track down the culprit. Hope this helps! Prensa

jb00sted - Hello! Are you carrying any live iguanas like Fonger mentioned? When you are teleported to the spaceship in Zeta or use the Anchorage Simulation all of your gear is taken & placed into a container. This is okay for vanilla items but certain mod added items are known to cause a CTD when placed in containers. A simillar CTD can occur with the transition to Tranquility Lane & the move from Vault 87 to Raven Rock. Known culprits are live iguanas from the iguana mod or the version built into Mart's Mutant Mod. Scripted Night Vision Goggles have also been suspects. Just having those items in your inventory at the above mentioned points will cause a CTD, just make sure they are not on you at those points. I'd recommend checking your inventory for those known culprits or any mod added (particularly if it has some scripts attached) item that you are carrying just before transportation. The Unofficial Patch fixes loads of things that the official ones don't even go near, it's best to keep them if you can. Only the Unofficial Fallout 3 Patch - Broken Steel.esp patch has a bad bug & there is a fix for that posted in the UF3P Discussion section. Hope this helps! Prensa

Jeoshua - Hello! I recommended the FSR_4-0-7 version because it's the first version I used & it worked amazingly well almost straight out the box. Only had to tinker with the MaximumFPS setting. Really helps with the smooth running of Fallout 3 on my quad core. & like I said, I don't seem to need the .ini multi core fix with it running. I've tried the WIP version & didn't find it as smooth even with altering the various settings. Of course, how effective it is probably depends on what set up you've got so others might find the WIP the same or better. It's just that if I recommend something I like to stick to what I know well. With me, the FSR_4-0-7 version has a proven track record. Prensa