fsx se and p3d 2.5 needed additional simconnects, howabout v3?

Does your addon need Simconnect with FSX-SE or P3D v2/3?

 

Rather than worry about it just install FSX RTM, SP1, and SP2 with P3D v2/3. For FSX-SE install FSX RTM and FSX SP1, FSX SP2 is installed by FSX-SE.

With FSX, FSX-SE, and P3D v2/3 installed the list of Simconnects should look like:

microsoft.esp.simconnect: 1.0.20.0, Simconnect.dll: 1.0.195.0
microsoft.flightsimulator.simconnect: 10.0.62615.0, Simconnect.dll: 6.2.62615.0
microsoft.flightsimulator.simconnect: 10.0.60905.0, Simconnect.dll: 6.2.60905.0
microsoft.flightsimulator.simconnect: 10.0.61242.0, Simconnect.dll: 6.2.61355.0
microsoft.flightsimulator.simconnect: 10.0.61259.0, Simconnect.dll: 6.2.61637.0

This is were i found mine in Prepar3D   :smile:   Loads of folders in here to play with 

 

 

ok thanks  :wink:

When we install P3D that process installs microsoft.esp.simconnect: 1.0.20.0 into the system environment, and makes a copy of the manifest files and folder containing the module file Simconnect.dll: 1.0.195.0 in "C:\Windows\WinSxS" the side by side folder.
 
Let's say we install P3D v2/3 on a fresh system and intend to use addons originally built for FSX, or that expect to find certain FSX versions of Simconnect on the system. We locate and run the appropriate SimConnect.msi:
 
.\Lockheed Martin\Prepar3D v3^{(or v2)}\redist\Interface\FSX-RTM\retail\lib\SimConnect.msi
.\Lockheed Martin\Prepar3D v3\redist\Interface\FSX-SP1\retail\lib\SimConnect.msi
.\Lockheed Martin\Prepar3D v3\redist\Interface\FSX-SP2-XPACK\retail\lib\SimConnect.msi

When we install FSX-SE the process installs microsoft.flightsimulator.simconnect: 10.0.62615.0 into the system environment. Usually this also installs FSX-SP1 SimConnect as well, but it may be worth checking. Same goes for FSX-SE; on a fresh system we locate and run the appropriate SimConnect.msi, but if we already installed for P3D v2/3 we need not do it again now:

.\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM\SimConnect.msi
.\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1\SimConnect.msi
.\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi

If we already installed FSX boxed versions to SP2 we would probably already have the three FSX Simconnect legacy files set up on the system properly.

Doing a search for Simconnect .dlls in the "C:\Windows\WinSxS" folder might show the existence of those Simconnect .dlls, but that does not mean they are installed correctly into the system environment. Only by testing the Simconnect interface programmatically will reveal its proper working order. Also, the existence or non-existence of Simconnect items in the Add/Remove Control Panel app has no bearing on the true state of the Simconnect system. When troubleshooting problems in the Simconnect system; remember that although certain programs can install a simconnect.dll file of their own located in their own directory and can explicitly load their module to connect as a Simconnect client, they generally run perfectly fine, but this way is not recommended practice for a number of subtle reasons and may be the root of problems in rare cases. Instead, ensure the system environment is already properly set up with the required versions of Simconnect installed from their .msi files, before installing and running addons.