Jump to content


Photo

Fallout 3 GOTY Application load error 5:0000065434 When Launching FOSE from within MO

mod organiser fose fallout3

  • Please log in to reply
36 replies to this topic

#31 GSDFan

GSDFan

    Jarl

  • VIP-Supporter
  • PipPipPip
  • 1,028 posts

Posted 29 May 2015 - 06:48 PM

Unfortunately I don’t have an answer for this and my interpretation of the logs may be wrong, but I may be able to shed some light for others to build upon.

 

 From the logs it looks like MO is doing the following:

  • Running and hooking fose_loader.exe and doing its housekeeping and preparing to load Fallout3.exe. This from ModOrganizer_15_05_29_12_00.log.
  • Running and hooking Fallout3.exe and doing housekeeping and preparing to run FalloutLauncher.exe. This is from ModOrganizer_15_05_29_12_00_1.log.
  • Running and hooking FalloutLauncher.exe. This is where I think the problem is. We should not be doing this, the game should be starting at hooking Fallout3.exe. This is from ModOrganizer_15_05_29_12_00_2.log.

We need to find out why after Fallout3.exe is hooked and I assume not launched, FalloutLauncher.exe is being launched and thus giving the appid fault. If anyone has any ideas or knows if my analysis is flawed please chime in.

 

One thought is to rename the FalloutLauncher.exe and run FOSE and see if it changes anything.


  • 0

#32 GrantSP

GrantSP

    The antipodean

  • VIP-Supporter
  • PipPipPipPipPipPipPipPipPipPipPip
  • 4,302 posts

Posted 29 May 2015 - 08:54 PM

I think your understanding of what the logs are saying is correct. These logs are indeed showing the process of hooking and launching Fallout3.exe is not succeeding and the next executable in line is being called, FalloutLauncher.exe.

 

Can you examine your ModOrganizer.INI, or look a the settings in MO's UI with the 'Executables' list, and see if the Steam appid is applied to any of the Fallout executables, fose, Fallout3 or the launcher? If it is missing, and most likely it is, what happens if you add it to the Fallout 3 exe? That's the field labelled 'Overwrite Steam Appid'.

 

Additionally, just to make it easier for comparisons, can you make a new profile with ONLY the base game files, no mods, run the game and post those logs? Ensure you have MO managing archives checked in the new profile and all the BSAs are checked in the 'Archives' tab.


  • 0

#33 RevReese

RevReese

    Citizen

  • Citizen
  • 14 posts

Posted 31 May 2015 - 09:00 AM

My MO INI file:

MO INI File

 

Also the FOSE modify executable dialog has "Overwrite Steam AppID" ticked and 22300 in the box as per advice further up in this thread.

 

Unticking this has no effect, the error (5:0000065434) occurs.

 

I also checked the fallout3 and fallout launcher modify executable dialogs and there is nothing in the box and overwrite steam appid is unticked.

 

I applied the overwrite steam appid to fallout3.exe and the (P:0000065432) occurs.

 

 

I have created a vanilla profile using only the base game files and no mods and the problem still occurs (P:0000065432).

 

Thank you all for the help, this is turning into quite the mystery!.

 

Logs from running FOSE with vanilla profile and overwrite steam appid selected: https://www.dropbox....1052015.7z?dl=0


Edited by RevReese, 31 May 2015 - 09:16 AM.

  • 0

#34 GrantSP

GrantSP

    The antipodean

  • VIP-Supporter
  • PipPipPipPipPipPipPipPipPipPipPip
  • 4,302 posts

Posted 31 May 2015 - 07:17 PM

A mystery indeed!

 

What happens when you assign a working directory to the FOSE settings in MO and also set it to close on launch?


  • 0

#35 RevReese

RevReese

    Citizen

  • Citizen
  • 14 posts

Posted 01 June 2015 - 08:04 AM

I do love a good mystery!.

 

I'm not sure what you mean by "working directory", I have it set to the game directory and the fose_loader.exe

Setting it to close on launch still brings up the P:0000065432 error.


  • 0

#36 GrantSP

GrantSP

    The antipodean

  • VIP-Supporter
  • PipPipPipPipPipPipPipPipPipPipPip
  • 4,302 posts

Posted 01 June 2015 - 07:41 PM

I just meant that the 'Start In' field actually had something in it. Not that it should make a difference, but it can't hurt to try things, we've lucked out on just about every other method! :confused:

 

Sorry to say it, but I'm out of ideas.


  • 0

#37 RevReese

RevReese

    Citizen

  • Citizen
  • 14 posts

Posted 02 June 2015 - 07:43 AM

Ah okay i get you!.

 

It is currently empty though trying it with the Fallout directory brings up the P:0000065432 error.

It was worth a shot, thank you to all of you for the help, looks like back to FOMM for now (and hope i don't run into any mysteries there too!).

 

It's just so strange that MO works beautifully with New Vegas and Skyrim! i remember having a similar problem with Oblivion for a while too but that sorted itself out eventually.

 

Seeing as this seems to be a steam problem, I will try the steam forums again and report back here if anything works.

 

Thanks again for all the help!.

 

EDIT: I reverted back to FOMM and it loaded first time and everything is running okay so far! so for anyone reading this who has tried all the above help and still having no joy (please don't let it just be me!), just use FOMM, it worked for me!.

 

I have kept MO installed for FO3 in case an update or something in the future fixes it automagically! :;):

 

A big thank you to everyone above for their help and advice, sadly nothing worked for me, but i am sure any future readers will find something of use somewhere in this thread!.


Edited by RevReese, 03 June 2015 - 12:21 PM.

  • 0



Also tagged with one or more of these keywords: mod organiser, fose, fallout3

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users