Siinful

Well I didnt find my retail copy yet but after doing a full reinstall seems to have fixed the issue. Oddly I didnt do anything different then what I did when installed it the first time but FOSE is launching correctly now at this time. Thank you GrantSP in trying to help me solve the issue.

Like I said in the last post I tried renaming the fose_launcher.exe to FalloutLauncher.exe to see if that would atleast get it to boot into the game with FOSE loaded which it did not. That is why it says it is launching FalloutLauncher.exe instead of FOSE. In the mean time I am going to try reinstalling the steam copy and MO to see if it changes anything while I try to find my retail copy. Things got shuffled around and I lost track of it but I know it is around somewhere.

Steam has been running before I try starting FOSE in MO just tried it without and it just boots Steam back up then same issue. Changing the FOSE loader to FalloutLauncher like suggested in the other thread didnt help either just got stuck in the infinite loop of trying to launch. Here is a log of the first round of it trying What's the chances uninstalling FO3 and MO then doing another clean install might help anything? Only other thing I can think to try is hunting down my retail copy where ever that might be and pray it doesnt have the same issue.

During that attempt I was using this launcher which was shown in the Clear and Present Danger guide here. Also I had this LAA patch for the Fallout.exe and and GFWL Disabler installed. So now I have restored all the original exe files and this is the most recently log after trying again after removing all of that.

It generated two at the same time. 1st. 2nd. Looking at the last few logs it only made to logs at the same time when I try to load FOSE.

Sadly neither of those two things helped. Also tried reinstalling MO over again but thats didn't help either.

Yup I did run it once outside of MO with and without FOSE. Running FOSE outside of MO works like normal and typing "getFOSEversion" in the ingame command console gives me to most recent version so I know it loaded it. Its really weird first problem I have had with MO since I have started using it with the other games.

I seem to be unable to get the Fallout 3 Script Extender to correctly load in Mod Organizer. When ever I attempt to launcher the FOSE_loader.exe in MO it instead tries to load the default FalloutLauncher.exe instead. So far I have tried deleteing the default FOSE shortcut MO makes when it detects and making a new one but it still does the same thing. All the other shortcuts work fine LOOT, Default Launcher, FO3Edit, etc. This is on a fresh install of the Steam version of Fallout 3 - Game of the Year Edtion after runing it once outside of MO to make sure all the normal INI files are made and adding the LAA patch. My New Vegas and Skyrim installs of MO dont appear to have this issue. NVSE and SKSE launch fine along with all the other tools. I am on Windows 7 64 bit is that matters.