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.