P3D v3 [SOLVED] SODE not in Add-Ons Menu

[RobdeVries]

Hi there,

I'm aware of this thread.
My situation. I installed Aerosoft's VaeroyX (latest installer). After creating a scenario in P3Dv3 in Vaeroy all is flat, only a photoscenery under layer. Searching the AS forum it was revealed that this is a SODE issue.
However the version of SODE that ships with VearoyX was installed properly and was registered and activated.
For good measure I uninstalled and reinstalled but to no avail. Then I updated to the latest SODE installer 1.3.4.. I noticed that this is installed in a different default location(?) i.e. C:\Program Files (x86)\12bPilot\SODE.
Then I noticed that ingame there's not even an entry in the Addons menu of P3Dv3.

I checked exe.xml and dll.xml and all seems fine to my eyes.
Here is the contents of exe.xml in C:\Users\<YourName>\AppData\Roaming\Lockheed Martin\Prepar3D v3: no such file in this location
Here is the contents of exe.xml in C:\ProgramData\Lockheed Martin\Prepar3D v3:

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="AceXML" version="3,0" id="exe">
   <Descr>AceXML Document</Descr>
   <Filename>exe.xml</Filename>
   <Launch.Addon>
   <Name>SODE</Name>
   <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectDisplayEngine.exe</Path>
   <CommandLine>P3Dv3</CommandLine>
   </Launch.Addon>
</SimBase.Document>

Here is the contents of dll.xml in C:\Users\<YourName>\AppData\Roaming\Lockheed Martin\Prepar3D v3:

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>viva_P3D.dll</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\iBlueYonder\Heron's Nest\Scenery\viva_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>D:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
</SimBase.Document>

Here is the contents of dll.xml in C:\ProgramData\Lockheed Martin\Prepar3D v3:

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="AceXML" version="3,0" id="dll">
    <Descr>AceXML Document</Descr>
    <Filename>dll.xml</Filename>
    <Launch.Addon>
        <Name>SODE Animation Module</Name>
        <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>TargetInfo</Name>
        <Path>Gauges\TargetInfo.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Fury_1500</Name>
        <Path>Gauges\Fury_1500.dll</Path>
        <DLLType>PDK</DLLType>
    </Launch.Addon>
</SimBase.Document>

So I'm a bit at loss as to what's going wrong...

 

[12bPilot]

Looking fine setup wise...
By chance, does your startup scenario contain the avatar as the default vehicle? There was a bug that lead to a disconnect of SODE when loading p3d with the avatar. This is fixed with v1.4.0, which will be released mid september

 

[RobdeVries]

Looking fine setup wise...

That's bad news...
Nope no avatar as default vehicle. The F22.

 

[12bPilot]

Could you attach the SODE.log please? It's located at C:\ProgramData\12bPilot\SODE\log or accessible via the SODEPlatformManager.exe -> Tools -> Show Log
As a last resort, I can offer a TeamViewer Session. It's the most efficient way for me to support. I'm available today and tomorrow for a session if you wish -> just send a PM

 

[RobdeVries]

Well Jeffrey, thanks very much for trying to help me out. I did one last resort uninstall, reinstall and it somehow solved the problem..

I've come to think of it..
I had also some trouble having the new Justflight TB10/TB20 Tobago/Trinidad to show up ingame.
"Accidently" I reinstalled a A2A aircraft and noticed that all was broke and could not be repaired. A quick glance in the A2A FAQ learned that:

P3D - Installed but nothing works and all is broken!?

P3DV2/3 sometimes wont install the required simconnect files. No worries though as they are provided by Lockheed in the following directory;
\Lockheed Martin\Prepar3D v2\redist\Interface\FSX-SP2-XPACK\retail\lib (replacing 2 with 3 if using P3DV3).

So I reinstalled the required simconnect files, and lo and behold the A2A aircraft, worked, Vaeroy works and the JF TB10/TB20 works....so it might has to do something with simconnect(?)

So an admin might close this thread marked solved.

 

[12bPilot]

so it might has to do something with simconnect(?)

Most of the external add-ons rely on a FSX-SP2 simconnect version, even in P3D. This version is not automatically installed with P3D, but needs to be manually installed as descriped above. If you have FSX in parallel, the required SimConnect is already on your computer of course.

I will mark the thread as solved.