Jump to content
  • 0
sutex

Mod Organizer FOSE installing with FO3 GOTY

Question

I can see no instruction to install FOSE , with Fallout 3 when using MO.

 

Do I just drop FOSE into the GOTY folder, given the scripts ?

There was a suggestion by Youtube video , about MO not do to this, but it focus is Skyrim

https://www.youtube.com/watch?v=jGKhdiJYBqo

 

Very new to MO , Have run mods and managers before , but using MO for first time .

 

Have a CLEAN  installl of the game  DATA folder backup, have saves so using those mods , for my new MO install

 

WHAT I HAVE

Steam Fallout 3 GOTY .... Patched with Updated FALLOUT patch latest

FOMM fork .... Installed to default , MO points to it  exe, works

FO3Edit_3_0_31_EXPERIMENTAL-637-3-0-31 ... Installed into own Folder (FO3edit) inside of Fallout3 GOTY

 

 

 

A side note, with FO3edit , still a bit confused do I check or uncheck backups.  When I first ran FO3edit, I closed it after opening. A box popped up saying there was a problem in Overwrite. I removed the FO3editbackup it was refering too. Correct ? as all I have at the moment is the DEFLAUT esm plus the Updated Patch Overwrite is emtpy in MO , I have no mods installed, as yet.

Edited by sutex

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

1. Copy the .dll files and fose_loader.exe to your Fallout 3 directory. This is usually in your Program Files folder, and should contain files called Fallout3.exe, FalloutLauncher.exe and the G.E.C.K. (if installed).

 

2 FOSE will be automatically setup in MO on the next startup, run it from there.

Share this post


Link to post
Share on other sites
  • 0

1. Copy the .dll files and fose_loader.exe to your Fallout 3 directory. This is usually in your Program Files folder, and should contain files called Fallout3.exe, FalloutLauncher.exe and the G.E.C.K. (if installed).

 

2 FOSE will be automatically setup in MO on the next startup, run it from there.

NOT the src , that has common , fose folders inside , ONLY the dll & the fose.exe  ... correct ?

Share this post


Link to post
Share on other sites
  • 0

ok thanks I have done that , again when clicking fose in  MO, a dos box opens for a second , but FO3 won't launch, Not good

 

Running FOSE directly from the FO3 GOTY folder the game starts.  How to fix this otherwise cant use MO

Edited by sutex

Share this post


Link to post
Share on other sites
  • 0

MO works fine with FOSE and other FO3 utilities and mods. Look at the "Clear and Present Danger" guide in my signature for detailed instructions, and on the associated forum posts here and here. There are some mods that can install using the version of FOMM built into MO, and a few that need FOMM-fork which can run with MO. There are examples in the guide for both cases. The guide has a small troubleshooting section including some typical reasons why the game fails during launch.

 

By the way, the current FO3Edit version is 3.0.32 which came out in July 2014.

Share this post


Link to post
Share on other sites
  • 0

Not working for me  , also been told src folders needed , & that fo3edit 31 better for FO3 than 32 ,  , but thanks for the link would never have known about it , given search never showed it

Share this post


Link to post
Share on other sites
  • 0

The FOSE src folder isn't needed, it just has information for those who want to understand it more deeply such as those building scripts to use with it.

 

If you read the sticky post at the top on the Nexus page for FO3Edit it suggests not using 3.0.31 to clean FO3 mods; use 3.0.32 instead.

Share this post


Link to post
Share on other sites
  • 0

 Following this guild , https://wiki.step-project.com/User:Kelmych/Fallout3 2nd time still FOSE will not start from MO,, can someone tell me why.?

 

On Win 7 64bit  FO3 GOTY ,, AS of first post , I need FOSE working

 

01:15:29 [D] configured profile: Vanilla Fallout01:15:29 [D] starting C:SteamLibrarySteamAppscommonFallout 3 gotyfose_loader.exe from command line01:15:29 [D] save C:/SteamLibrary/SteamApps/common/Fallout 3 goty/Mod Organizer/webcache/cookies.dat01:15:29 [W] failed to remove tutorial control  "MainWindow"01:15:29 [D] save C:/SteamLibrary/SteamApps/common/Fallout 3 goty/Mod Organizer/webcache/nexus_cookies.dat

 

 

Placed a bug report as , it's a problem 

Edited by sutex

Share this post


Link to post
Share on other sites
  • 0

There is a troubleshooting section at the bottom of the guide that might help. It sounds like you already ran fallout so the registry entries and Fallout.ini and FalloutPrefs.ini were created in "user name"DocumentsMy GamesFallout3. Did you try adding the two Fallout.ini entries in the guide under "Fallout 3 Dual-Core and Multi-Core Fix" using the ini editor in MO? On my system I get a CTD if these entries are not present.

 

Did the loading proceed far enough to provide entries in fose_loader.log or fose.log in the GOTY directory? If so it would help if you provide the contents in a post.

 

Are the five lines you posted the only entries in "mo_interface.log"; the entries in my log are not quite the same as the ones you posted? Are you using MO 1.2.11 ? Did you try reinstalling MO in case the installation had a problem?

 

Here is what I have in the bottom of my "mo_interface.log" when I startup:

16:00:46 [D] configured profile: Pure Vanilla16:00:46 [D] activate profile "Pure Vanilla"16:00:46 [D] displaying main window16:00:46 [D] using load order from file16:00:48 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillamodlist.txt saved16:01:14 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillainitweaks.ini saved16:01:14 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillaplugins.txt saved16:01:14 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillaloadorder.txt saved16:01:14 [D] D:GamesFO3 Mod OrganizerprofilesPure Vanillaarchives.txt saved16:01:14 [D] save D:/Games/FO3 Mod Organizer/webcache/cookies.dat16:01:14 [D] save D:/Games/FO3 Mod Organizer/webcache/nexus_cookies.dat

Share this post


Link to post
Share on other sites
  • 0

fose_loader.LOG

 

launching: Fallout3.exe (C:SteamLibrarySteamAppscommonFallout 3 gotyFallout3.exe)clearing large-address-aware flagrecorrecting exe checksum (00E59548 -> 00E59528)crc = FE5B82AEhook call addr = 00C05F61load lib addr = 00D9B0F0dll = C:SteamLibrarySteamAppscommonFallout 3 gotyfose_1_7.dllremote memory = 001F0000old winmain = 006EE300

launching

 

fose.LOG

 

FOSE: initialize (version = 1.2.2 01070030)fallout root = C:SteamLibrarySteamAppscommonFallout 3 goty

plugin directory = C:SteamLibrarySteamAppscommonFallout 3 gotyDataFOSEPluginspatchedFOSE: deinitialize 

01:29:39 [D] configured profile: Vanilla Fallout01:29:39 [D] activate profile "Vanilla Fallout"01:29:39 [D] displaying main window01:29:39 [D] using load order from file01:29:41 [D] C:SteamLibrarySteamAppscommonFallout 3 gotyMod OrganizerprofilesVanilla Falloutmodlist.txt saved01:56:29 [D] C:SteamLibrarySteamAppscommonFallout 3 gotyMod OrganizerprofilesVanilla Falloutinitweaks.ini saved01:56:29 [D] C:SteamLibrarySteamAppscommonFallout 3 gotyMod OrganizerprofilesVanilla Falloutplugins.txt saved01:56:29 [D] C:SteamLibrarySteamAppscommonFallout 3 gotyMod OrganizerprofilesVanilla Falloutloadorder.txt saved01:56:29 [D] C:SteamLibrarySteamAppscommonFallout 3 gotyMod OrganizerprofilesVanilla Falloutarchives.txt saved01:56:29 [D] C:SteamLibrarySteamAppscommonFallout 3 gotyMod OrganizerprofilesVanilla Falloutinitweaks.ini saved01:56:29 [D] save C:/SteamLibrary/SteamApps/common/Fallout 3 goty/Mod Organizer/webcache/cookies.dat01:56:29 [D] save C:/SteamLibrary/SteamApps/common/Fallout 3 goty/Mod Organizer/webcache/nexus_cookies.dat

AFTER as I have said , read above CLICK FOSE RUN inside of MO does not work

 

08:42:52 [D] configured profile: Vanilla Fallout08:42:52 [D] starting C:SteamLibrarySteamAppscommonFallout 3 gotyfose_loader.exe from command line08:42:52 [D] save C:/SteamLibrary/SteamApps/common/Fallout 3 goty/Mod Organizer/webcache/cookies.dat08:42:52 [W] failed to remove tutorial control  "MainWindow"08:42:52 [D] save C:/SteamLibrary/SteamApps/common/Fallout 3 goty/Mod Organizer/webcache/nexus_cookies.dat 

Edited by sutex

Share this post


Link to post
Share on other sites
  • 0

Are these fose logs from when you tried to run FOSE from inside MO or outside MO? The logs of interest would be any that were written from your unsuccessful attempts to run FOSE from inside MO. The fose logs look fine; if they were written during your unsuccessful attempts to start Fallout 3 using the FOSE loader then they say that FOSE itself is successfully started and the problem isn't with FOSE but something that happens after FOSE.

 

You didn't say whether you tried including the changes to Fallout.ini that I mentioned.

 

I'm assuming you are using only the vanilla Fallout 3 files and no additional mods.

Share this post


Link to post
Share on other sites
  • 0

Following this , https://wiki.step-pro...elmych/Fallout3  yes I have done all that I can do Following this , Have done the ini , for muiltcore

As I have said , FOSE runs outside of MO ,, it does not run inside of MO , that is,  when I click on the RUN FOSE in MO nothing happens

 

As of the guide , I have not installed any MODS , because FOSE is not working yet. vanilla Fallout 3 files plus all the DLC

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

  • Similar Content

    • By 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...
    • By RevReese
      Hi all!.
       
      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
      iNumHWThreads=2).
       
      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.
      Fallout3.esm
      Anchorage.esm
      ThePitt.esm
      StreetLights.esm
      BrokenSteel.esm
      PointLookout.esm
      Zeta.esm
      Unofficial Fallout 3 Patch.esm
      aHUD.esm
      EVE.esm
      iHUD.esm
      Fellout-Anchorage.esp
      Fellout-BrokenSteel.esp
      Fellout-PointLookout.esp
      Fellout-pipboylight.esp
      Fellout-Zeta.esp
      megalight.esp
      Fellout-Full.esp

       
       
      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.
       
       
       
    • By GrantSP
      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.
       
      EDIT:
      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.

×
×
  • Create New...

Important Information

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