The result was that I did not get any of the overlays to work.įallout launcher from MO. Next the game was launched from fose_loader.exe while SCS running. This was repeated with SCS closed and the result was the same as should be expected. The result was I got only the Windows live overlay to run. Next Fallout 3 Executable, Fallout3.exe, was launched with SCS running. Note: If the Steam Client Service, here after referred to as SCS, which is the Steam Windows tray icon is stopped, it will start back up if it has been closed. I got both the Steam and Windows live overlay. The result was I got the launcher window.
Next the game was launched from FalloutLauncher.exe in the game directory. Of course no mods were available as MO is not running. The result was I had the Steam overlay and the Windows live overlay. The game was launched from the play button, which brings up the launcher window. So far it seems like I'm the only one with this problem.The following is my attempt to tackle and solve this problem. Please be aware this is a hack, and as such it is prone to failure from unseen events not encountered in my testing.įirst off testing was done to provide a baseline of the interaction of MO and Steam. I want to be able to run my game with mods through Mod Organizer while I have my hours played recorded from the same game through Steam.Īnd also have my Steam friends to see that I'm in-game playing through Steam.įallout NV & Skyrim works perfectly in that regard, but why doesn't Fallout 3?Įdit: Can somebody else (Mainly those who own Fallout 3 goty edition on steam and also uses Mod Organizer) test this out? I even tried renaming the fose_loader.exe to FalloutLauncher.exe and still the Steam overlay does not come up. I do use FOSE, however the Steam overlay does not even want to work for Fallout3.exe and FalloutLauncher.exe when run from MO either. I've been using Mod Organizer for Fallout 3 & Fallout NV, and I've noticed that the Steam overlay does not want to work for Fallout 3 when run from MO.
0 kommentar(er)
