Jump to content


Photo

FOSE crashes loading through MO (Fallout 3)


Best Answer GrantSP , 02 August 2017 - 05:12 PM

You are modding SSE, which means you used MO2. If you are still using MO2 for FO3 I suggest switching to MO 1.3.11

Go to the full post


  • Please log in to reply
4 replies to this topic

#1 karamille

karamille

    Prisoner

  • Members
  • 3 posts

Posted 02 August 2017 - 05:21 AM

Sorry if this has been covered elsewhere, but I couldn't find anything that quite matched my situation. 

 

I've successfully used MO for Oblivion and SkyrimSE, and I thought it was working alright with FO3 as well, up until I tried to actually launch the game. 

 

FOSE runs fine if launched outside of MO, but from MO it immediately pops up with "A component of the Fallout Script Extender has stopped working". 

 

I've used LOOT to sort load order before trying to launch anything. 


  • 0

#2 GSDFan

GSDFan

    Jarl

  • Moderators
  • PipPipPipPipPipPipPipPipPip
  • 845 posts

Posted 02 August 2017 - 08:21 AM

You should check with Windows task manager, you will probably see an executable that was launched through MO was not closed after the crash. FOSE can't hook into the game if it is still in memory and thus the error message. In any case MO should be Restarted. This should be done for any executable that crashes from MO.



#3 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,907 posts

Posted 02 August 2017 - 05:12 PM   Best Answer

You are modding SSE, which means you used MO2. If you are still using MO2 for FO3 I suggest switching to MO 1.3.11



#4 karamille

karamille

    Prisoner

  • Members
  • 3 posts

Posted 03 August 2017 - 04:04 AM

Oh. I'll be damned. It is MO2. I never even noticed, assumed that if it was 2, it'd say so! Well then. I'll see about swapping to 1.3 then. 

 

@GSDFan, it crashes regardless of whether I've only just opened MO or not, I restarted it a lot due to a separate issue that's only mildly irritating and is something I can live with. But perhaps I won't have the issue using the other version of MO that apparently I should have been using anyway. We shall see. 


  • 0

#5 karamille

karamille

    Prisoner

  • Members
  • 3 posts

Posted 03 August 2017 - 06:05 AM

Yep, changing to the correct MO fixed it, and at least one CTD is gone now. Thanks for kindly pointing out my silly mistake!


  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users