Jump to content
  • 0
Sign in to follow this  
13thGeneral

Mod Organizer opens FalloutLauncher Replacer window

Question

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...

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

It was brought up in the Nexus forums, in regards to my dilemma, that it's possible the .ini files were corrupted or not generated properly with the new graphics card settings. Also that I may have to reinstall the fINIp3 files as well.

 

Not sure this was the issue - as I'm not at home to test it - but its a possibility. I'll be trying it as soon as I can.

Edited by 13thGeneral

Share this post


Link to post
Share on other sites
  • 0

Just for the obvious troubleshooting, did you do a full uninstall of the prior device drivers (using a program like Device Driver Uninstaller)?  That's one of my preferred methods for resolving graphics related issues at the start, a clean uninstall for the install of the up-to-date drivers and such.  After that, definitely checking on the .ini's naturally.

 

<snipped by SergeTroy>

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...

You do remember Fallout 4 is a triple A game, right?  Bugs Galore await ... :D  I'm probably just going to keep playing my 3 - 7 year old games and watch YouTube load up with vids on it, myself.

  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0

Just for the obvious troubleshooting, did you do a full uninstall of the prior device drivers (using a program like Device Driver Uninstaller)?  That's one of my preferred methods for resolving graphics related issues at the start, a clean uninstall for the install of the up-to-date drivers and such.  After that, definitely checking on the .ini's naturally.

 

You do remember Fallout 4 is a triple A game, right?  Bugs Galore await ... :D  I'm probably just going to keep playing my 3 - 7 year old games and watch YouTube load up with vids on it, myself.

lol, yeah, that was a slightly tongue-in-cheek remark. I expect a lot of bugs, though I'm at least hoping it doesn't crash as much as Fallout 3.

 

I did a "clean install" of the ini files but it's possible that they left residual settings. I just don't see how that would be creating this issue; I removed all the .ini files and launched the vanilla client to allow it to regenerate them, but I'm still having the issue.

 

UPDATE: Tried deleting and allowing the game to regenerate the ini files, again, and replacing them with the fINIp3 files, again, as well as checking BSA management and Archive-Invalidation were checked. None of that worked. I thought about it a bit, read the FalloutLauncher Replacer, FOSE, Mod Organizer, and fINIp3 install and setup instructions again, and looked at the guide instructions again, and... I realized I had forgot to copy the new ini files into the Mod Organizer profile(s).*

 

~facepalm~

 

So, in conclusion - SOLVED

 

*I've had a bit of a cold and blame it on the fever.

 

Edited by 13thGeneral
  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0

Congrats, as long as it got worked out at the end, no real issues.  Have to admit I didn't have much in the way of suggestions beyond regurgitating what I've picked up from Gopher and Kelmych's guides, etc., sometimes a little better phrased if you're an uber layman, like me, othertimes not so much.  :P  Yeah, once the comment was made in regards backing up the originals I went mad with that, making sure to back up and 'read only' the first launcher ini's as well as the fINIp3 when first set 'vanilla.'  I haven't done my current experimental-finale of the ini's, mostly because I'm still suspicious of things.  :shrugs.

Share this post


Link to post
Share on other sites
  • 0

Congrats, as long as it got worked out at the end, no real issues.  Have to admit I didn't have much in the way of suggestions beyond regurgitating what I've picked up from Gopher and Kelmych's guides, etc., sometimes a little better phrased if you're an uber layman, like me, othertimes not so much.  :P  Yeah, once the comment was made in regards backing up the originals I went mad with that, making sure to back up and 'read only' the first launcher ini's as well as the fINIp3 when first set 'vanilla.'  I haven't done my current experimental-finale of the ini's, mostly because I'm still suspicious of things.  :shrugs.

Yeah, I've been through the guide process several times, and each time encountering a different issue, resulting in having to start over. Luckily this time was just an oversight on my part.

I've been very meticulous this time around (4th.. 5th time??) in the installation and setup, so as to know exactly what is being done. This will teach me yet another lesson; esp not to mod while ill.

I'm dreading the Merge/Bash section, because that's where it gets a bit tedious and tricky.

 

Thanks for your help in getting my brain on the right track for the solution.

Edited by 13thGeneral
  • Upvote 1

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.