"A component of the Fallout Script Extender has stopped working.&

[Voryn]

Fixed: I extracted FOSE into the directory AND the data folder, no sure why but now it works perfect, not sure why they didn't mention putting one of those files in the data folder.

Update: LIVE was disabled fine when running FOSE, and I had already moved the DLC into the data file (forgot to mention I had). I think the problem was the src folder needed to go in the data folder, and FOSE never mentioned putting it there.

 

Earlier I was having some problems with Fallout but I had several mods and it could have been any of them. However, I deleted ALL Fallout files on my system including saves, dlc, and the program files. Then I did a clean install to my hard drive (Not in the program files), updated to the most recent patch, and downloaded and installed all DLC. This puts the game at fully funtional, all DLC, eveything working perfectly, no mods whatsoever. Then I install FOSE (Fallout Script Extended) according to the readme. I extract and put the .dll files, the src file, command doc (not sure if it's needed but wth) and the fose_launcher in the game directory (main directory, not the data file). Then I run it and several things happen. First, a command box appears, then a message saying "A component of the Fallout Script Extender has stopped working." Then Fallout starts. The game runs and plays fine (The error message is still open on desktop, and I can close it and it will remove the command box but Fallout will stay running) except that I cannot save. This is the same problem I had with all the mods installed, and now with ONLY FOSE on my system, I can safely say that it is the problem. I can play the game, start a new game, or load saves that I have moved from my LIVE account, but am unable to save in any way. I'll save, quicksave, or have it autosave and the saving message will appear in the top left but if I go to load there's nothing there. Also if I delete the saves that I moved from my LIVE account into the save file and then go back to the load screen, they'll have re-appeared. So essentially my problem is that a component of FOSE stops working, and causes me to be unable to affect the Fallout 3 saves file while in-game, both in terms of creating and deleting saves. Any help anyone can provide would be greatly appreciated, as this is making modding near impossible.

[koalagundam]

I extracted FOSE into the directory AND the data folder

 

I have the same exact problem you describe, but your solution does not make any sense. What do you mean by this?

[mechine]

Heh Heh Heh, They didn't mention it because Fose goes with the other stuff like GECK, FOMM, FO3edit inside the Bethesda softworks/fallout 3 folder, which is pre data folder, all the tools go in the folder which contains the data folder (in other words) Putting FOSE inside the actual data folder or having two copies is a bad idea. What could of happened is that one of your mods is looking for fose in the data folder, which just means some idiot thought they new how to make mods, made one, then you came an picked it up.

 

Idk it could just be a messed up install, they don't always work out you know, plus you can lose bits of data durring download. There's something called data loss, which is usually associated with wireless or satellite communication. Kind of cool, bits of data just vanish into thin air while it's traveling. Neat huh. Doesn't happen that often though, so you could try to just download an install it again, but I wouldn't have more than one copy installed if you paid me to, especially in the data folder. It might make little green men pop out of your computer an start eatting your face off. Yeah we'd want to avoid that.

 

 

Then it might have to do with how you are actually launching it. FOMM will launch fallout 3 via FOSE if it detects it, so maybe reinstall both, there are many versions of each program, it could be that you have a incompatable match. If you are useing FOSE then also using FOMM is a no-brainer, so long as when you install an you launch FOMM and the tab for launch game say launch FOSE then that's how you launch the game from now on, short of wanting to change the fallout3defaultlauncher.exe grapics settings. After you install FOSE an FOMM the only use for the game disc as well as the default launcher is for the game settings interface.

[koalagundam]

ive reinstalled everything, and i still can't save my game, even with all mods turned off(leaving only dlc).

 

im running 1.7 if that matters.

[mechine]

Crash on save means that your save game you loaded is corupted. The start of the game will autosave, an if you mean that you are crashing there, then it means you have problems deeply rooted in your install/build of fallout 3. A new game start shouldn't crash ever, if it does, then that means you need to keep working on making your installs an builds cleaner.

 

 

 

What happens is that while you are playing, your game went corupt threw poopy data, which can happen an your game is actually crashing an can be that way from up to an hour or more before it actually CTD (crash to desktop) mean while you are running around putting heads on posts an creating new save games, locking that poopy data in there, next time you load it, then you run into weird problems like crash when you save, or crash when you fast travel, or much wierder stuff.

 

 

 

Load up your save game, then fast travel somewhere, then spin the camera around, press Esc load the save game again, it should be faster now, try to save like that, if you can't fast travel at all then just run around, or go into a building, then come out spin the camera or something an then load the save game, an try to see if it crashes again. I know it helps me run secondary programs in the background when I'm playing fallout, for some reason the second load of a save just runs faster.