Hi 

Just wondering if anyone has a solution for running SODE in both P3Dv5 & 6 on the same computer? I have SODE v1.7 installed currently, working fine for P3D v5. However I can't see any jetways in P3Dv6 after activating SODE. The latest online conversation I can find suggests SODE v1.8 is required for P3Dv6, but I have read it caused problems in P3Dv5. However when I try and install SODE v1.8 it seeks to over-ride v 1.7.

In summary how can I have both SODE versions installed and applied to the effective P3D platforms?

cheers

Edited March 9Mar 9 by Ian S

Sorry, quick update, I've just realised that I had SODE v1.8 installed, it must have snuck in with an airport install or something. Anyway, that simplifies my question and I have adjusted the topic title - any tips for getting SODE working in P3Dv6? It appears in my addons.cfg and I have registered and activated it on the SODE interface, but no jetways are appearing, any ideas?

thanks

@Ian S, the SODE log should give a clue to any problems.

I don’t have v6 but given you can’t have independent installs for SODE I’m not sure this problem is solvable. The SODE forum has seemingly closed so no help possible from the developer.

Have you tried installing both v1.7.1 (for v5) and v1.8 for v6? You would need to change the install path but if that works that should work.

Hi Ray

When I try and run a second install, I am basically prompted to run a repair or replacement of the existing instal in C:\Program Files (x86)\12bPilot\SODE . It doesn't seem to give the option for a second install.

I've re-ran everything, SODE is working fine in v5 but no jetways in v6, nor the red X, just nothing. 

I've checked the add-ons.cfg 

in v5 it states

[Package.0]
PATH=C:\Program Files (x86)\12bPilot\SODE\P3Dv5
TITLE=SODE
ACTIVE=true
REQUIRED=false

and v6 it states 

[Package.0]
PATH=C:\Program Files (x86)\12bPilot\SODE\P3Dv6
TITLE=SODE
ACTIVE=true
REQUIRED=false

In those respective folders there are identical .xml files apart from

<AddOn.Description>SimObject Display Engine P3Dv5 (c) 12bPilot</AddOn.Description>
  <AddOn.Component>
    <Category>EXE</Category>
    <Path>..\SimObjectDisplayEngine.exe</Path>
    <CommandLine>P3Dv5</CommandLine>

<AddOn.Description>SimObject Display Engine P3Dv6 (c) 12bPilot</AddOn.Description>
  <AddOn.Component>
    <Category>EXE</Category>
    <Path>..\SimObjectDisplayEngine.exe</Path>
    <CommandLine>P3Dv6</CommandLine>
 

and and in the UI both are shown as "registered" and "active" so they appear a complete mirror install but one works and the other doesn't. Interestingly, I checked the logs as you suggested , the start states the same for both, notably "Targetting platform [P3Dv5]" I suspect that is the issue, just need to work out how to change the "targetting platform" for P3Dv6 

[18:55:00.665] INFO  : SODE Version '1.8.0'
[18:55:00.665] INFO  : Targetting Platform [P3Dv5]
[18:55:00.673] DEBUG SODE.SETTINGS : All Settings successfully read.
[18:55:00.673] DEBUG SODE.SETTINGS : Current Settings (1) -> SoundEngine=1; WatchDog=0; SecMenuHotKey=NONE
[18:55:00.673] DEBUG SODE.SETTINGS : Current Settings (2) -> UserJetwaySound=1; PrimaryHotKey=1
[18:55:00.673] DEBUG SODE.SETTINGS : Current Settings (3) -> AircraftStateTriggeredAutoDockingEnable=1
[18:55:00.673] DEBUG SODE.SETTINGS : Current Settings (4) -> AIDetection=1; AIJetwaySound=0
 

any advice would be appreciated.

cheers

Ian

@Ian S, we’re in uncharted territory here. It’s not something I’ve ever done myself. However, putting key words into google reveals this:-

 

The SODE Platform Manager determines the targeted Prepar3D (P3D) platform primarily by scanning the Windows Registry to detect the simulator's installation path. 

 

Key Detection Mechanisms

• Registry Keys: SODE looks for specific registry entries under HKEY_LOCAL_MACHINE\Software\Lockheed Martin or HKEY_CURRENT_USER\Software\Lockheed Martin.
  • It specifically checks the SetupPath key for each P3D version (v1 through v6) to confirm the simulator is installed and to locate the Prepar3D.exe file.
• Version Separation: The Platform Manager treats each detected version as a completely separate entity.
  • If a registry key is missing or points to an invalid folder, that specific version will not appear in the Platform Manager tabs.
• Registration Process: Once a platform is identified, SODE uses Prepar3D.exe itself to perform necessary file changes (such as updating exe.xml or dll.xml) to register the SODE module within that specific simulator environment. 

Troubleshooting Platform Detection

If a specific P3D version is not being targeted or detected:

• Verify Registry Paths: Use the Registry Editor to ensure the SetupPath for your P3D version matches the actual installation folder.
• Reinstall SODE: If the registry was corrected after SODE was already installed, a reinstall can trigger a fresh scan of the available platforms.
• Check Configuration Files: SODE writes entries into exe.xml and dll.xml located in C:\ProgramData\Lockheed Martin\Prepar3D v[X]. If these files are corrupted or read-only, SODE may fail to register even if the platform is detected. 
   

Check via the P3D Addon menu the correct version number is shown for v5 (1.7.1) and (1.8) for v6.

If they’re correct versions are running for each we can eliminate that problem. If they’re not then check the Registry. A edit may be all that’s needed to ensure the right version runs for each sim.

Thanks Ray, some success. After some tweaking it became apparent that SODE was now working fine on P3Dv6, however not at the airport I use for a lot of testing, Imaginesim WSSS. 

However, i have now fixed the problem and have jetways at WSSS. 

For the benefit of others, I located the SODE/xml folder and created duplicates of the files, ImagineSim_WSSS2_PD5_GP.xml & ImagineSim_WSSS2_PD5_Stands.xml and renamed the copies ImagineSim_WSSS2_PD6_GP.xml & ImagineSim_WSSS2_PD6_Stands.xml

Within those new files, I adjusted every <TargetSim ID="P3Dv5" entry to  <TargetSim ID="P3Dv6" for each gate.

Job done.

Ian

Edited March 12Mar 12 by Ian S

Well done Ian. This could prove useful to anyone else running v5 and v6.