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...
I have recently switched to MO from FOMM after a Windows Reinstall (Win7 64bit) and have had no problems with it whatsoever with Skyrim (so far).
But when I try to run Fallout 3 with a handful of mods through the FOSE link in MO it crashes instantly with the above Steam error ("Application load error 5:0000065434").
I have posted in the Steam forums about this problem and will feedback anything useful here.
The game loads fine from Steam (obviously mod-free) and from FOMM (though my mods do not appear when using FOMM).
It also appears to load fine when I click on the fose_loader in the game folder though that will not load my mods will it? even if I have MO open in the background.
I have tried all the standard fixes (editing the Fallout.ini and fallout_default.ini files with bUseThreadedAI=1
Used LOOT to set my load order.
Setting Fallout3.exe, FalloutLauncher.exe and fose_loader.exe to compatibility to Win XP SP3.
Running fose_loader as admin.
Adding d3d9.dll to the game folder.
Running without mods enabled and with (same crash).
Renaming ClientRegistry.blob from the Steam install folder.
Here is my load order:
[spoiler=Load Order]# This file was automatically generated by Mod Organizer.
Unofficial Fallout 3 Patch.esm
I am fresh out of ideas so any help from you guys would be greatly appreciated!.
Other than this problem, I am having a blast with MO! I successfully modded my Skyrim back to it's previous state within a few hours!.
Thank you for your time.
I've just noticed an odd behaviour with my save game files from FO3.
With Fallout 3 and FOSE installed I was expecting to see alongside my saves, files with the *.fose extension that match the saves generated within FO3, this is the same manner that happens with all the other extenders, however they are absent.
So my question is: do FO3 saves not use the extended save format or are saves only generated if FOSE has modified some data in game?
FOSE is installed correctly and I can see it is loaded by both the main menu screen and by GetFOSEVersion in the console.
I've never noticed before so I am completely clueless as to what is supposed to happen. I'm only going on what the other extenders do.
Also, call me stupid, but I can't find the official support foums for any of the extenders. I'm assuming they are on the BethSoft forum somewhere but I just can't see them.
Recently Browsing 0 members
No registered users viewing this page.