For some reason this morning Mod Organizer has suddenly decided to start launching the FalloutLauncher Replacer when clicking the FOSE option within MO - selecting the 'Fallout 3' start option in MO crashes with an error (I'm at work, will post screen later) - and I cannot figure out why. The only change from two days ago is that I installed a new graphics card (updated drivers and DirectX 11 installed).
I click 'play' in Steam, it opens the FalloutLauncher Replacer, I press '3', MO opens, I select FOSE, click 'start' and it opens the FalloutLauncher again. Obviously I stop there and hit 'ESC' to Exit and close the FalloutLauncher - which crashes and Fallout.exe needs to be force-quit in Task Manager.
If I select option '1' after originally opening from Steam, the game client opens as expected - and the vanilla game runs fine from there.
I can't recall if selecting option '2' in the initial FalloutLauncher to run with FOSE works or not. I'll update later.
I know I've seen someone else post about this issue, but I cannot seem to located that particular thread discussion. - ah, nevermind, found it.
I'll check the fix found in the other thread, when I can tonight, though any help would still be appreciated.
Seems like I just can't ever completely get through the guide without some issue rearing it's ugly head. Thank goodness Fallout 4 is out soon...
Question
13thGeneral
For some reason this morning Mod Organizer has suddenly decided to start launching the FalloutLauncher Replacer when clicking the FOSE option within MO - selecting the 'Fallout 3' start option in MO crashes with an error (I'm at work, will post screen later) - and I cannot figure out why. The only change from two days ago is that I installed a new graphics card (updated drivers and DirectX 11 installed).
I click 'play' in Steam, it opens the FalloutLauncher Replacer, I press '3', MO opens, I select FOSE, click 'start' and it opens the FalloutLauncher again. Obviously I stop there and hit 'ESC' to Exit and close the FalloutLauncher - which crashes and Fallout.exe needs to be force-quit in Task Manager.
If I select option '1' after originally opening from Steam, the game client opens as expected - and the vanilla game runs fine from there.
I can't recall if selecting option '2' in the initial FalloutLauncher to run with FOSE works or not. I'll update later.
I know I've seen someone else post about this issue,
but I cannot seem to located that particular thread discussion.- ah, nevermind, found it.I'll check the fix found in the other thread, when I can tonight, though any help would still be appreciated.
Seems like I just can't ever completely get through the guide without some issue rearing it's ugly head. Thank goodness Fallout 4 is out soon...
5 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now