Sign in to follow this  
Guest KenAdam

Simconnect confusion (SP1A version)

Recommended Posts

I'm updating the Delphi translation of the SimConnect headers, butI'm confused by the new version of SimConnect.dll supplied with SP1A.The examples shows that the manifest should be "version=10.0.61242.0", and in the WinSxS directory there is a matching folder x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.61242.0_x-ww_35e8ee9abut the dll in that folder has a version of 10.0.61355.0 (fsx-sp1.20070510-2038).Does this make sense?Anyway, the real problem is that although I've installed the new SDK and then the new Simconnect.msi, when I try to run my test application (using 61242 in the manifest) I get a "Version Mismatch" exception and it looks like FSX is still loading the original (60905) version of SimConnect.Is there something else I need to change?I've proved (by various file rename and manifest changes) that my application is using the "61242" DLL.According to the help, the dwIndex returned by the exception will be 4 for the RTM version and Major/Minor version for SP1 onwards.I get 4, which implies that it isn't even using SP1 (the only previous version I had installed).The Simconnect log reports "0.00000 SimConnect version 0x00000002" on startup, which is what it has always reported.TIARegards,Ken

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

[Apologies if this gets through twice - I logged in but when I posted, the forum decided I wasn't logged in...]Disregard the above posting, unless like me you didn't install FSX SP1 before FSX SDK SP1A, in which case you now know what to do ;-)I'm still confused about the simconnect versioning in the WinSxS folders, and Simconnect itself now reports "0.00000 SimConnect version 10.0.61242.0", whereas FSX reports with the 61355 version (both in "about" and via simConnect).Now I've just got to find out why running the recompiled SetData test app (Delphi version) hangs FSX when I try to re-position...Ken.

Share this post


Link to post
Share on other sites

>The examples shows that the manifest should be>"version=10.0.61242.0", and in the WinSxS directory there is a>matching folder>x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.61242.0_x-ww_35e8ee9a>but the dll in that folder has a version of 10.0.61355.0>(fsx-sp1.20070510-2038).>>Does this make sense?Yes. Apparently the VersionInfo version number is that of the PRODUCT (i.e. FSX), not the build of the SimConnect implementation. Seems rather confusing to me, but the guys at MS seem to think it makes sense. ;-)RegardsPete

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this