I've been trying to figure out how to get hte most recent sim connect so that my add ons will work in FSX steam edition. Can someone help me? I've seen that others are able to get theirs working, I just want to know how to do it.

I've been trying to figure out how to get hte most recent sim connect so that my add ons will work in FSX steam edition. Can someone help me? I've seen that others are able to get theirs working, I just want to know how to do it.

I found the below on the A2A FSX-SE forum. Might be worth trying.

Al

 

Simconnect installation

Some users may also have to install simconnect. You can do this by running the simconnect installer included with FSX Steam, edition. The default path for this is;

"Steam\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi"

Thank you, trying that out now. Now for the long fun time of reinstalling the add ons.

Ok so I clicked on it and I think it installed but FSX still isn't recognized by my add ons. Why is it that my installers will not recognize FSX while others will, and apparently all is the same?

Ok so I clicked on it and I think it installed but FSX still isn't recognized by my add ons. Why is it that my installers will not recognize FSX while others will, and apparently all is the same?

I think if you could clarify a few things it would be helpful, and then perhaps others might be able to better respond with some advice.

 

 Are talking about FSX in the above quote, or FSX-SE?  It would be best if you don't use FSX if you really mean FSX-SE. Are you running a dual system with both FSX and FSX-SE installed, or do you just have FSX-SE installed? What addons, in particular, fail to install?  There are installers that will work with a stand alone FSX-SE system, but not with a system that has both FSX and FSX-SE installed.  Below is some information posted in the AVSIM FSX-SE Compatibility Testing Thread by Virtuali that you may find helpful:

 

 

INSTALLERS

 

FSX:SE can be installed in two different ways: alone or alongside FSX. Let's call the installation alongside FSX the "Dual mode".

 

In "Dual Mode", FSX:SE is kept separate from FSX, not just in a different folder, but also with all its registry keys, configuration folders, scenery.cfg, fsx.cfg, in different folders than the FSX one.

 

The advantage of the "Dual Mode", is that you can install FSX:SE without affecting your standard FSX installation.

 

The disadvantage is that 3rd party add-on installers WILL have to be modified, in order to recognize the new registry keys and folders, otherwise they'll all try install into the normal FSX. And if an installer or a product need to use the FSX.CFG for any reason, it will have to be updated to recognize FSX:SE, because the FSX.CFG is now named FSX_SE.CFG, but in "Dual Mode" only!

 

The "Single mode" is when you install FSX:SE on a new system with no existing FSX installation. In this mode, FSX:SE will use the SAME registry keys, shared folders, configuration folders, etc, as if it were FSX, and the FSX.CFG is still named FSX.CFG. It's basically FSX for almost all purposes, just installed into the Steam folder.

 

The advantage of this mode, is that any existing installer will likely work unmodified, because it will find everything to recognize a normal FSX installation. The only exceptions will be installers that explicitly check for the FSX.EXE build number, and might refuse to proceed because FSX:SE has a different build number for the .EXE.

 

IN-GAME COMPATIBILITY

 

This might probably be divided in some areas too:

 

1) Add-ons (airplanes/sceneries) that use plain FSX SDK - These will probably work without any issues, provided the installation issues are sorted out.

 

2) Add-ons that use Simconnect - Simconnect has changed, but it's backward compatible with the old versions, provided the required libraries are installed. This changes somewhat depending if you install FSX:SE alongside FSX, or on a brand new system that never had FSX installed into.

 

If you install it alone on a new Windows installation, you'll have to install the FSX Simconnect runtime libraries, which can be found in the SDK folder under the FSX:SE installation, look for the 3 legacy interface .MSI installers.

 

If you don't do this, no FSX Addon using the FSX (SP1 or SP2/XPACK) version of Simconnect will work, unless the developer will recompile it using the FSX:SE edition of the Simconnect library, but I don't think many developers will do that, considering the are NO new features in the updated Simconnect.

 

3) Add-ons that use FSUIPC4 - None of them will work now, since they will all require an updated version of FSUIPC, but of course all of them would work, once the new FSUIPC will come out.  [update -- the new FSUIPC the supports both FSX and FSX-SE is now available.  -- Al]

 

4) Add-ons that use FSDT Addon Manager/Couatl - Like FSDT sceneries, Flightbeam sceneries, the QW757, GSX, etc. - It's the same as with FSUIPC4, they all require an updated version of those two modules which, fortunately, it's already done and updated installers should be online in a few hours, tomorrow at the most.

 

5) Add-ons that use any other kind custom .DLL/GAU module to access directly FSX memory locations - They are in the same situations as the two cases above: they will have to be updated because since FSX and all it's .DLLs has been recompiled, almost all memory locations has changed, which means every add-on that used such techniques to interact with FSX must be updated, otherwise it will likely cause crashes and almost certainly won't work.

 

Al

Why would I suddenly start talking about FSX? If the original post was about FSX-SE? Add ons like PMDG, and FS Labs Concorde just will not find FSX-SE on my computer, despite the fact that I've seen posts on steam saying that they work fine. I've also installed the 3 .msis I think, is there a way to check to see if they are installed? Why should I have to clarify each reply of the same post what I am talking about? Isn't that overkill? Maybe I should just be hyper literal all the time too.

For the sake of continued clarity, yes. Do you have a "dual" installation? In other words, did you install FSX:SE with FSX:MS (DVD version) already installed?

 

If so, the two versions have different Registry entries, which is why your installers cannot find "FSX:SE."

IF you have put FSX and FSX-SE on different drives, or different folders then have you tried using Flight 1's Registry Fix tool  to point to your FSX-SE location??

 

Would this work or would it screw up subsequent installations for FSX ?? I assume you have have to run it each time you wanted to add Aircraft or some scenery in both locations.

Well I did, but I uninstalled FSX, after I couldn't get anything to install, then reinstalled FSX,-SE to no avail, I did realize that there were some aircraft still installed, so I uninstalled a couple as a test, still to no avail, maybe they're still in the registry.  CCcleaner help with that?

Uninstalling FSX after having installed FSX:SE won't help at all, since the Registry entries for FSX:SE remain unchanged, as does all of the internal .exe and .cfg files.

 

At this point, if you uninstall FSX:SE completely, then manually delete any left over files, and folders. Then when (re)installing FSX:SE it will look act and feel just like regular FSX!

 

Frankly there is a much simpler way of 'fixing up the mess' but I hesitate to detail the steps since it involves some manual Registry editing.

I am at least competent enough in the Registry to delete keys, I've never attempted to add anything however, always been a bit hesitant to do that. I think I will uninstall everything, delete the FSX keys and whatnot TH|EN do it again, I will say the DTG FSX seems like it will be far more stable than any previous version. I may wind up using this over P3d

Well so far I've managed to delete all the registry entries I could find with C:\FSX, but it still has yet to fix the problem, I'm at a loss as what to do.