Viewing 1 post (of 1 total)
  • Author
  • #489

    Section A: SODE General

    • I have installed SODE, but it doesn’t move the jetways at airport XYZ! The log says something about ‘Lists are still empty’…

      When you don’t have an airport installed on your machine, that doesn’t include SimObjects that need to be controlled by SODE, then SODE is pretty much useless!
      SODE will then only run in external jetway triggering mode to ensure that fsdreamteam (FSDT) sceneries that might be installed can be driven with GSX. SODE will also only show a single entry in the Add-Ons menu: Test DLL Connection.
      Once you install an airport with SODE SimObjects, the Add-Ons menu will show more options including the in-game text-menu.
      SODE does nothing to your default sceneries or airports that don’t use SODE SimObjects!

    Section B: SODE Installer

    • Installer Error: There is a problem with this installer package, A program required for this install to complete could not be run

      Option 1: If you still have the entry in the control panel for the old version, you can try to execute the “Repair” option first. This should restore all necessary files on your harddrive, one of which is used during uninstall (SODEPlatformManager.exe).
      After repairing, you should be able to uninstall the old version properly.

      Option 2: When you exactly know the version number of the old SODE install, you can also download that legacy installer from here:
      Historic Downloads
      Re-run the appropriate installer and then uninstall.

      Option 3: The last resort is to use a Microsoft utility that cleans up corrupted MSI installs.
      For all Windows versions: Microsoft Installation Fixer Tool

    • “The Registry holds an invalid path to your Prepar3d.exe”:

      To find your Prepar3D.exe file, SODEPlatformManager.exe reads out the path from your registry. The registry key in question is:
      HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4
      Note that SODE does not edit that path, it is set during install of Prepar3Dv4. If you move the P3Dv4 folder manually, this does not update that registry entry! The correct procedure would be to uninstall and re-install Prepar3Dv4 if you want to have it installed in an other location.

      There could be also another key in the 32-bit part of the registry (WOW6432Node):
      HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v4
      This entry is not made by SODE or by the Prepar3Dv4 installer! This entry is created by some other add-on (Migration Tool for example) and it is not correct and should not be there (Prepar3Dv4 is 64-bit, so why should the key be in the 32-bit part of the registry?!).
      Unfortunately, the SODEPlatformManager.exe (V1.5.3) gets fooled by this key and will report the “Invalid Path” error because it scans the 32-bit part registry first.
      This behaviour is corrected in the V1.5.4 release where it only scans the 64-bit part for Prepar3D v4.

      Solution: You have to use the tool “regedit” to find the relevant registry key(s) and manually edit it to the actual installation path of Prepar3D.exe.

    Section C: SODE Log

    • Where can I find the SODE.log file?

      The log file is located at C:\ProgramData\12bPilot\SODE\log and is called SODE.log.
      You can also access the log file through the SODEPlatformManager.exe -> Tools -> Show Log.

    Section D: Simconnect.log

    • How can I generate a simconnect.log?

      A certain indication if SODE is correctly loaded is the simconnect.log, which is written by the simulator itself.
      For example for P3D3v4, you need to create a simconnect.INI file in your %USERPROFILE%\Documents\Prepar3D v4 Files.
      The contents of that file are


      Start your sim and observe that a console window (simconnect server output) is launched together with the sim. When the Scenario screen is loaded, close the sim. Now, there should be a simconnect.log file in your P3Dv4 root directory.

      To stop logging the simconnect server messages, just delete the simconnect.INI file you created at the beginning. The console window should not be launched anymore when you start the sim the next time.

    • This topic was modified 4 years, 4 months ago by 12bPilot.
    • This topic was modified 3 years, 9 months ago by 12bPilot.
    • This topic was modified 3 years, 9 months ago by 12bPilot.
    • This topic was modified 3 years, 6 months ago by 12bPilot.
    • This topic was modified 3 years, 3 months ago by 12bPilot.
    • This topic was modified 2 years, 9 months ago by 12bPilot.
    • This topic was modified 1 year, 11 months ago by 12bPilot.
    • This topic was modified 1 year, 11 months ago by 12bPilot.
Viewing 1 post (of 1 total)
  • The forum ‘FAQ: Frequently Asked Questions’ is closed to new topics and replies.