Hi Damien,As you suggested, I have reinstalled SDK SP1a, then SDK SP2 on my XP PC. But I still receive the error message, and it refers to SP1. I have also re-installed SDK, SDK 1a and SDK 2 on my Vista server.Both machines now show FSX SP2 SDK, and the XP client shows 2 versions of SimConnect Client.Any ideas?Cheers, Richard

I just went through this myself last night, after attempting to reinstall my simconnect facilities on my wide-client PC. From what I can determine, ASXsp2 needs the exact version of Simconnect.msi that came with the FSX SDK, SP1(a). What you must understand is the simconnect.msi that we copy out of the SDK folder change versions with each SDK update; and I think ASX is version checking the simconnect facilities installed. Simconnect installation are cumulative, like .NET Framework entries, in your Add/Remove Programs table. You need to install all simconnect.msi versions as you patch forward the SDK.(Very specific order)Uninstall all SDKs.Uninstall all simconnect entries from Add/Remove Programs.Install the SDK from FSX Deluxe DVD.Copy the simconnect file to safe location and rename "simconnect_RTM.msi"Install SDK SP1a patchCopy the simconnect file to a safe location and rename "simconnect_SP1a.msi"(If you have FSX-SP2) Install SDK SP2 patch(If you have FSX-SP2) Copy the simconnect file to a safe location and rename "simconnect_SP2.msi".Now, on the wide-client PC, install all the different version simconnect files you just saved away, in-order, without un-installing any of them.Install simconnect_RTM.msiInstall simconnect_SP1a.msi(If you have FSX-SP2) Install simconnect_SP2.msiYou should now have two or three simconnect entries in your Add/Remove Programs List.FWIW, I have not had to change any of the ini/cfg files, locations, or versions, as described in the ASX Networking instructions. Once you have had simconnect working over the network, it seems all the other simconnect configuration files work over the various versions of the msi file without having to be changed or patched-foward.Hope this helps.PS, Damian or Jim, what I don't understand, is if ASXsp2 is looking-for and using the specific simmconnect_SP1a "pipe" and we have FSX-SP2 installed on the server, wouldn't there be some possible inconstancies? I ask becuase, ASX seems to do some funny things lately and I think it's becuase ASXsp2 is using a differnt version simconnect facility (sp1a) than what is installed in FSX (sp2). I need to e-mail this thought seperately to Jim but I also wanted to bring it foward publicly as well.

Hi,ASX is looking for simconnect version 10.0.61242.0.As this is our #1 support issue, we're trying very hard to make sense of things and come up with a solution. Unfortunately this is a common problem with FSX and other add-on vendors are having their share of problems as well.As SP2 becomes more accepted by the community we may build on the SP2 simconnect which avoids this issue. Right now we have "heavy resistance" by our customers, many who will not upgrade past SP1.Best,

Hi Damian,Understood about slow migration to simconnect-sp2. But do you agree, that using an older simconnect pipe (sp1a) into a FSX-sp2 environmnet could cause weird issues? I'm trying to trouble-shoot two issues and I'm having trouble figuring out where to start. My two big issues at the moment while testing for Jim are "super white-outs" where fog envelops everything but the 2D forward panel (including the interior of the VC) and loss (popping) of cloud layers. Both intermitantly. My best guess at the moment seems to coincide with the time I started using FSX-sp2. I think we starting to see the general migration to FSX-sp2 (dx9) as many of the original cfg tweaks don't seem to be required anymore and peformance is increasing (slowely).

Hi Al,Yes, certainly it could be a reason for some of the problems we're having. Technically according to those "in the know" this should not be an issue, but we have different experiences... :)Best,

So, does this mean that you don't plan to have ASX working via SimConnect with SDK SP2 installed for a while? Sorry for the question, but from your post it sounds like you are considering getting it working with SP2 somewhere down the road, but until then, SimConnect isn't going to work?I hope this doesn't come across as whiney, it's an honest question :)Thanks,-stefan

Hi Stefan,No, ASX works fine with FSX SP2. The problem is that we use an SP1 dependancy on SimConnect so that we have dual compatibility (SP1 or SP2), but some SP2 installations have problem installing SP1 SimConnect properly. Technically, FSX any version should include all installations of previous and current simconnect versions.We are considering building on an SP2 dependancy but this eliminates compatibility with SP1. Best,

Hi Al!After spending hours trying to get ASX SP2 to work with SimConnect SP2, I was about to post my problems and posit that ASX SP2 won't work with SimConnect SP2. But Damien assures us that it will work. Have you got this working?I have religiously followed your instructions above (assuming that by wide-client PC you mean SimConnect client). But on starting, ASX gives the XEngine message "SimConnect SP1 managed version was not found to be correctly installed on this system. It is recommended to uninstall and reinstall the FSX SP1 update so this can be repaired. ..." It thus appears that ASX SP2 is specifically depending on SimConnect SP1 being available which, for me, it isn't because each SP install explicitly requires the deletion of the previous SP, unless I cancel the installation.I shall next try reinstalling SimConnect base + only SP1 on both client and server to see whether the error message is literally true.I am close to tearing my hair out (what little is left)! Damien, have you anything that you can advise?Cheers, RichardPS The ASX Support page does not mention the availability of ASX SP2.

Hi Richard,So SP1 Simconnect is not installed on the client machine. You'll need to install the simconnect.msi file that is included in SDK SP1A. To get this, you must uninstall SP2, SP1, then the SP1A SDK update. The simconnect.msi will then be in the SDKCore UtilitiesSimConnect SDKlib folder.I know this is a big pain and wish it was much easier. FSX and SimConnect installations are proving to be very problematic, and it appears not even MS knows for sure what is going on. Its a shame that simconnect.msi for SP1 (or any version) cannot be distributed by anyone (such as us), or offered as download on the FS insider site.We are investigating two potential plans to make things better. One is to offer two different builds for SP1 or SP2 simconnect (which eliminates most simconnect install problems), or eliminate SP1 compatibility and always build on the latest (SP2).Best,

@ Richard,For the record, and I could be wrong, but I don't think there is an official SP1 update to the SDK any more. It was superceded by SP1a. Could this be why some people are having so much trouble with the version-checking of ASX (ASXsp2 is checking for the SP1a version only "61242")? Maybe re-download the SDK SP1a and SP2 patches directly from FS-Insider website (they are exactly what I used along with RTM form the DVD).When I fixed/re-installed my simconnect-client(wide-client) the other day, the exact SDK updates and order that I used are listed in my instructions above. So, in my Add/Remove programs I have three simconnect-client entries from the three msi files I ran.Simconnect_RTM.msi -> Simconnnect Client v10.0.60905.0 -> 17.2MBSimconnect_SP1a.msi -> Simconnnect Client v10.0.61242.0 -> 76.0KBSimconnect_SP2.msi -> Simconnnect Client v10.0.61295.0 -> 145.0KBNotice the size differences of the installations; RTM is the full-installation of the simconnect-client; where SP1a and SP2 are much smaller patches to the original baseline. As Damian indicates above, ASXsp2 needs to see "v10.0.61242.0" installed to properly execute at this time.@ Damien,I also noticed, that the versions of the AI-traffic.exe files changed between SDK updates as well. So I have both exe's on my simconnect-client and both versions seem to connect to my FSXsp2 installation; for whatever that's worth.I sure would like to try any FSX-sp2 (simconnect-client_SP2) tricks you have up your sleve; even beta. I get spurious "super white-outs" as I call them, at start-up and lower-level flights, whereby nothing inside or outside the aircraft is visable, except the 2D panel in the forward-view only. If I then slew up above the layer, the "super white-out" clears-up. I have just completely unistalled ASX last-night in preperation for more trouble-shooting tonight.

>Hi Al!>After spending hours trying to get ASX SP2 to work with>SimConnect SP2, I was about to post my problems and posit that>ASX SP2 won't work with SimConnect SP2. But Damien assures us>that it will work. Have you got this working?Yes, works fine. Understand my configuration; look at my sig below each post. On my FSX rig, I have been running FSX (patched to SP2). On my simconnect-cleint (wide-client) rig; I ran ASXsp2, with the three simmconnect*.msi files I mentioned above.>I have religiously followed your instructions above (assuming>that by wide-client PC you mean SimConnect client). But on>starting, ASX gives the XEngine message "SimConnect SP1>managed version was not found to be correctly installed on>this system. It is recommended to uninstall and reinstall the>FSX SP1 update so this can be repaired. ..." It thus appears>that ASX SP2 is specifically depending on SimConnect SP1 being>available which, for me, it isn't because each SP install>explicitly requires the deletion of the previous SP, unless I>cancel the installation.>>I shall next try reinstalling SimConnect base + only SP1 on>both client and server to see whether the error message is>literally true.Whey would you install the simconnect-client (simconnect*.msi) files on you FSX PC? They only need to be installed on the client-PC to talk over the network to your FSX installation.>I am close to tearing my hair out (what little is left)! >Damien, have you anything that you can advise?Remember, FSX has its own internal simconnect functionality local to that PC. You are installing that functionality remotely on a client-PC with these msi files. It does not matter where you install the SDK. The point is to get at the simconnect.msi installation file (each version) to save and rename them for installation on the client-PC. The SDK is nothing more than a collection of docs, files, and executables. It does not installing anything functional to the FSX environment, so you can install it anywhere to get at the msi files.>PS The ASX Support page does not mention the availability of>ASX SP2.Patches are here: http://www.hifisim.com/support.php?title=H...oduct%20SupportGood luck...

To Al..Many thanks for your help so far. Having tried Damian's latest ideas, I do not get a simconnect.msi file for SP1a in my client SDKCore UtilitiesSimConnect SDKlib folder. So I tried to copy over the file from the server. This hasn't worked because I am unable to share the client file on XP because, it says, Program Files is a folder used by the OS. Likewise I cannot share the server library from my client.To Damian..I am going to give up trying for now and get on with some other work. I wish you well in trying to fathom the difficult. I am really looking forward to a simple (to the end user) installation process for whatever combinations are the solution to this real hassle. Please do ensure that the installation process is real easy, including the undoing of existing installed software, otherwise thousands of users will be yelling!Good luck, and if you want someone to beta test a solution, you have an eager beaver!Cheers, Richard

>To Al..>Many thanks for your help so far. >>Having tried Damian's latest ideas, I do not get a>simconnect.msi file for SP1a in my client SDKCore>UtilitiesSimConnect SDKlib folder. So I tried to copy over>the file from the server. This hasn't worked because I am>unable to share the client file on XP because, it says,>Program Files is a folder used by the OS. Likewise I cannot>share the server library from my client.Are you administrator when you install the SDK and when you attempt to share-out the "program files" folder? I don't normally install FS or any games under C:program files because it can be a nusuance, especially under Vista.Try installing the SDK (starting with the FSX DVD) temporarily to a directory directly on your simconnect-client PC, in a directory you newly create, such as C:FSX SDK then start with my instructions above, copying, renaming, and patching.

To update this with what worked (mostly) for me:On my Client PC (A macbook pro running xp via bootcamp) I installed the SDK off of the FSX disc, and then installed the SP1A patch from fsinsider. Following that, I ran the simconnect.msi to get simconnect working.ASX starts up and no longer complains about a bad simconnect, which it was doing when I had installed the SP2 simconnect.msi. It connects to FSX and updates just fine and dandy, no problems, so it works as well as it did when I was running ASX on my main FSX pc.Only issue I noticed so far is that when I end my flight in FSX, ASX crashes on the client machine. It's done this 2 out of 3 flights so far.So, I didn't have to screw aroudn with my FSX install at all to get ASX working over the network, just had to install the SDK temporarily on the client pc.Note: This is running FSX with SP2 on the main PC.-stefan

>>Good luck, and if you want someone to beta test a solution,>you have an eager beaver!>>Cheers, RichardHi Guys We are logging each forum message and email we get to address any issues you guys have so please bear with us as we work with you.If you are seriously interested in a place on our beta team please send us an email giving the following details.1. FS experience (including versions used current and past)2. Previous and Current beta experience3. System specs4. Amount of time you can realistically spend testing and reporting for us.ThanksCarl Hackmanhttp://www.hifisim.comhttp://www.hifisim.com/banners/hifi-dev-sigbanner.jpg