• Content count

  • Joined

  • Last visited

About 12bPilot

  • Rank

Recent Profile Visitors

132 profile views
  1. Without that file, you won't see any jetways and SODE will not know about the existance of those. Uninstall or re-install of SODE does not modify anything in this folder, so I can't explain why the file disappeared. I'd recommend to re-install the entire KMSP scenery. I think it's the new Flightbeam Manager that puts that xml file into that folder when you select the "SODE jetways" option.
  2. Is there a 'Flightbeam_KMSP.xml' file in C:\ProgramData\12bPilot\SODE\xml?
  3. Hey Pete, In this case, SODE can not be the cause. SODE can only take down the simulator via the DLL module SimObjectAnimationModule.dll. But that is only active when you use SODE jetways, and is otherwise idle during loading of the sim. The message you initially saw was due to the fact that your sim crashed due to another module and SODE did not get notified about that by the sim, and hence SODE kept running thinking that the sim was still alive. When you restarted the sim, it tried to launch another SODE process but SODE didn't allow it because there was that "zombie" SODE instance still running from the previous (crashed) session. That's what the message is there for, to avoid multiple SODE processes running after a sim crash, which can be caused by whatever module. Now that you have disabled SODE and even the PMDG777, then there is no doubt that some other module is causing your crashes. That's all I can offer you as help... Lesson learned for me is that I need to come up with a mechanism that detects a sim crash reliably so as to shutdown SODE as a consequence. Good luck for your further investigations. -Jeffrey
  4. Thanks. There's an error code when trying to register SODE through Prepar3D.exe. Ok, if you unregister SODE so that the registration status turns red and then reboot your pc and launch P3Dv3, will it still crash? Is there a SimObjectDisplayEngine.exe in the task manager (shouldn't be if unregistered)?
  5. Hi, Can you launch SODEPlatformManager.exe and try unregister/register SODE again for P3Dv3? After doing so, could you navigate to C:\ProgramData\12bPilot\SODE\log and post the files SODE.log, PLTMGR.log and PLTMGR_DETECTION.log? I suspect there are double entries in the dll.xml/exe.xml files. Thanks.