NUCLEAR777 Posted April 13, 2013 Share Posted April 13, 2013 Hello, I recently wiped my Fallout 3, and did a fresh install. After words, I installed a few mods then got Archive Invalidation. I started up the game, it crashed at the start-up screen. Next I turned off EVERY single mod, including DLC. Tried it again, still crash. Then I tried the Archive Invalidation through FOMM. Still a crash. I have been looking for hours on why it is doing this, please some help would be great. Link to comment Share on other sites More sharing options...
SoulReaver911 Posted April 13, 2013 Share Posted April 13, 2013 (edited) So is it crashing without Archive Invalidation Invalidated? Some comp specs may be helpful. Specifically what OS you're running. Edited April 13, 2013 by SoulReaver911 Link to comment Share on other sites More sharing options...
NUCLEAR777 Posted April 14, 2013 Author Share Posted April 14, 2013 No, I can run Fallout 3 WITH some Mods without Archive Invalidation. However If I turn it on (Archive Invalidation), it crashes even without mods.My Specs are:Processor: Intel® Core i& CPU 860 @ 2.80GHzRAM: 4 GBOS: Windows 7 64 BitVideo Card: ATI Radeon HD 5450 LIke I said, I can play WITHOUT Archive Invalidation, but need it for mods/textures. Link to comment Share on other sites More sharing options...
SoulReaver911 Posted April 14, 2013 Share Posted April 14, 2013 (edited) Just checked out your processor (pretty smooth I must say). You've got plenty of ram. I use the HD5670 myself, and they're similar - no probs here. Windows 7 is the problem. Here's what I would do in your situation, and I suggest going through each step, even if you can seemingly play the game half-way through the list. 0: If you have Fallout3 installed in "C:\Program Files (x86)" or in "C:\Program Files" you may consider reinstalling somewhere else, that is while you're ahead and before you've installed a ton of mods. Archive Invalidation Invalidated apparently has problems otherwise. 1: Re-download Archive Invalidation Invalidated and reinstall in any directory (preferably where you can get easy access to it, such as the top directory for Fallout install, or in your tools folder.) Ensure that it is exactly 247kb (for program version) or 1kb for the manual zip. While you're at it, download it from the Dallas server, as I am assured that is a legit download. 2: Go ahead and deactivate it (probably isn't by default). I've gotten into the habit of reactivating after installing a lot of mods just to be sure. 3: Check to see if you have ffdshow decoders installed. You can search for them in the windows start button, and they'll probably show up if you have them installed. The reason you're doing this is so that if you do have either the audio, video, or both decoders installed, you can ensure that Fallout3.exe is NOT using them. Once you find it, open up its settings and select "Direct Show Control" from the list on the left. You'll see a little check-box on the right that says "Don't use ffdshow in:" In the text slot you'll see an unbelievably obtuse number of programs that are by default not allowed to use the decoder (you can guess why.) Make sure that fallout3.exe is in fact listed among these. Make sure that it is listed in this dialog in BOTH the audio and video converters. Apply, and push ok to save it if you had to change it. 4: After this, go ahead and grab one of my favorite tools for Fallout3, the Fallout3 Configurator, or FoFig as I lovingly call it. What this does: FoFig is a gui for the Fallout3.ini located inside C:\Users\%YOURUSERNAME%\Documents\My Games\Fallout3 ----(or whatever hard-drive the operating system is installed on if not "C") Go ahead and delete the file named "FALLOUT.INI". After doing so, you're going to get the Fallout Launcher to create a new one, because you and I, we're just cautious that way. All you need to do is make sure Archive Invalidation isn't active and run the game through the launcher just the one time, with or without mods. Make sure to actually start up the game so that you are at the main menu. Now you can get out of the game and backstage to FoFig. What you're mainly using FoFig for in this case: After installing it, and loading it up, FoFig will find your newly created .ini and you can start messing with it. You can go ahead and set up all your graphics settings if you want, but it is the Performance Tab on the left that we need to modify. Here are the settings that are pertinent to this discussion as I use them: http://newscalea.com/pics/help/FoFig.jpg However, there is one modification that you can use in FoFig that I cannot. Where it says "Havok Threads" go ahead and change this to four. Explaination: Fallout3 sucks at using quad-core processors. However it can use dual-core nicely. The reason I can only use two and yet you can use four is because if you check your cpu's specs you'll see that each of the 4 cores that make up your processor has TWO threads, making for a total of EIGHT threads. You should be able to use four threads just fine(i.e two processors.) However, it doesn't hurt to just try two for the time being, to ensure there aren't any problems. 5: Get FO3 RAM Boost It has a wonderful description of what this does on its webpage. It also has pictorial install instructions. Basically you're going to make it so that Fallout3.exe uses about 3.4 gigs of that ram you've got installed (the .6 accommodating for OS RAM usage and what not,) whereas before it was using about half of that. Tip: DO NOT MESS WITH THE FOSE_LOADER.EXE USING THIS METHOD. Will cause massive crashing. Of course no worries if you don't use FOSE, but honestly why wouldn't you? 6: OPTIONAL: Get the OmegaDrivers for your video card. AMD Catalyst This is an alternate driver for your video card which allows for a lot more control. It's highly suggested. AMD Catalyst Drivers 13.3 beta will do nicely. 7: Use Fallout Mod Manager to install all of the mods you're using, manually making FoMods as you go. I explain this in more detail here. 8: Reactivate Archive Invalidation Invalidated. 9: Well? What are you waiting for?! Give it a go! also 10: Consider using FO3edit to manually resolve conflicts among mods. I'm too tired to explain this in detail but luckily for you, there is an amazing Tutorial. Good luck. Edited April 14, 2013 by SoulReaver911 Link to comment Share on other sites More sharing options...
NUCLEAR777 Posted April 14, 2013 Author Share Posted April 14, 2013 0. Already Have.1. Done. but No Go. Freezes at Bethesda Loading Screen.2-10...Done all of these.....improved quality of game, however STILL Archive Invalidation Freezes the game, however when I turn it off it WORKS Perfectly. I don't understand...I need answers! Link to comment Share on other sites More sharing options...
M48A5 Posted April 14, 2013 Share Posted April 14, 2013 Do not use the standalone version of ArchiveInvalidation Invalidated! with FOMM. Uninstall the one you downloaded and make sure nothing is left of it on your hard drive. Only use the one that is part of FOMM. Link to comment Share on other sites More sharing options...
SoulReaver911 Posted April 14, 2013 Share Posted April 14, 2013 (edited) Now this is very strange indeed. http://cs.elderscrolls.com/index.php/Oblivion_Mods_FAQ#Archive_Invalidation This page describes in detail how to manually setup bsa redirection using a dummy file. Might be worth trying. Also, check to see if you have Archive Invalidation.txt anywhere in the game folder as this might be interfering. Make a backup and delete it. Do not use the standalone version of ArchiveInvalidation Invalidated! with FOMM. Uninstall the one you downloaded and make sure nothing is left of it on your hard drive. Only use the one that is part of FOMM. That's cool, didn't realize FOMM didn't require the separate .exe. This just might work. Tested myself and does the job just as well. I've had no problems using the external .exe before seeing as how using FOMM's archive invalidation toggles the external when it's there, however I can't understand why this might be interfering. EDIT: Found some more helpful comments from the download page. P1GMA Hello I found out how to fix the crash on start up error while using archiveinvalidated! You have to delete the menus folder in the Fallout 3 Data folder and it should work. Knight_Phoenix 12 kudos 236 postsI have Windows 7 64-bit. I had a working mod order with about 140 mods and a bashed patch. I installed 10 new mods, rebuilt the bashed patch, and then the game would crash on a new game. I tried running this tool and it still crashed. This install was at C:\Games and when I toggled binvalidateolderfiles to 0, I could start the game. However, the textures wouldn't show up. I tried many things to get this to work. Finally, after reading 30 pages of comments someone said they fixed it by installing to the default location of C:\Program Files (x86)\Bethesda Softworks\Fallout 3. I reinstalled to that directory and I can play the game again with binvalidateolderfiles to 1 and using a ArchiveInvalidationInvalidated!.bsa from a previous install. Hopefully, that helps someone. Edited April 14, 2013 by SoulReaver911 Link to comment Share on other sites More sharing options...
NUCLEAR777 Posted April 14, 2013 Author Share Posted April 14, 2013 HOW!? How did that work...Thank You SOOOOO Much! I deleted the menus folder.....Instantly no freezes, and can run any form of Archive Invalidation! I don't understand how it worked but thank you. Link to comment Share on other sites More sharing options...
SoulReaver911 Posted April 14, 2013 Share Posted April 14, 2013 (edited) hahaha, that is awesome can't believe that worked You might wanna drop P1GMA (link in the quote where it says his name) a thank you or something, he deserves it BTW, there are some mods that use the menus folder, such as fwe and darnified. If you want to use them, a fresh install of these mods probably won't affect your game's stability Edited April 14, 2013 by SoulReaver911 Link to comment Share on other sites More sharing options...
Recommended Posts