Simconnect

[tim arnot]

Plan-G uses the RTM version of SimConnect (in theory that means it's not dependent on anybody having a *particular* version of FSX - you shouldn't require SP1 or SP2 just to read aircraft telemetry and weather data!). The build you've gone back to is actually using SP2 by mistake!

I'm still working on a solution for the current build...

Several people have mentioned not seeing the aeroplane symbol. I'll change the default for the next build.

[robcap]

I'm still working on a solution for the current build...
Several people have mentioned not seeing the aeroplane symbol. I'll change the default for the next build.

Good luck with the developement. I'm looking forward to this, a tool dearly missed since FS Navigator didn't come to FSX.
And I found the airplane symbol, activation and options were just hidden where I didn't look ;-)

R.

[jschall]

Jeff, I'll also suggest you try the 355 build I linked to two posts up. Let me know if it works.

Did either of you have to reinstall FSX for any reason?

OK, Tim, I installed 355 in its own folder, it starts up ok, then I started FSX with a flight plan I had created with PlanG.

Then I pressed the Connect button, and it became greyed, the Disconnect button became dark.

BUT, there was no connection, because the mini-instrument panel did not update, and there was no aircraft-icon on the map.

Here is part of the log:
===============================
12:46:25 PM Connect button clicked
12:46:25 PM Testing mFSConnect.IsConnected
12:46:25 PM Calling ConnectToSimConnect
12:46:25 PM Checking SimConnect properties.
12:46:25 PM Initialising event handlers
12:46:25 PM Calling mFSConnect.Connect.
12:46:25 PM Connecting.
12:46:25 PM Initialising data request.
12:46:25 PM SimConnect event handlers & data definitions initialised
12:46:25 PM SimConnect connection established.
12:46:25 PM Requesting Plan weather for CSB3 St-Mathieu-De-Beloeil
12:46:25 PM Requesting Plan weather for ZHU HAUTS-BOIS (MONTREAL) (407 KHz)
12:46:25 PM Requesting Plan weather for CYHU Montreal/St-Hubert
12:46:25 PM Connected to FSX
12:46:25 PM SimConnect Exception received: WEATHER_UNABLE_TO_GET_OBSERVATION
12:46:25 PM SimConnect Exception received: WEATHER_UNABLE_TO_GET_OBSERVATION
12:46:25 PM
PLAN WX OBSERVATION: %sCYHU&A26 011620Z 05102KT&D63NG 06002KT&A887NG 06103KT&A1801NG 06603KT&A2716NG 06604KT&A3630NG 06805KT&A5459NG 06606KT&A7288NG 06809KT&A9117LG 06908KT&A10336NG 07308KT&A11860NG 14KM&B-1526&D1974 CLR 14/11 07/03&A887 02/00&A1801 -3/-5&A2716 -8/-11&A3630 -20/-22&A5459 -32/-34&A7288 -45/-47&A9117 -53/-55&A10336 -57/-60&A11860 Q1021 @@@ 30 7 60 2 | 60 2 61 3 | 90 -3 66 3 | 120 -8 66 4 | 180 -20 68 5 | 240 -32 66 6 | 300 -45 68 9 | 340 -53 69 8 | 390 -57 73 8 |
12:46:25 PM DisplayFlightPlanDetail: StartPosition
12:46:25 PM DisplayFlightPlanDetail: TAS
12:46:25 PM DisplayFlightPlanDetail: totalDist
12:46:25 PM DisplayFlightPlanDetail: totalTime
12:46:25 PM DisplayFlightPlanDetail: WindDirection
12:46:25 PM DisplayFlightPlanDetail: Altitude
12:46:25 PM DisplayFlightPlanDetail:
12:46:25 PM DisplayFlightPlanDetail: checking weather
12:47:38 PM DisplayFlightPlanDetail
12:47:38 PM No plan - erasing line
12:47:48 PM AddAirportToPlan -1
12:47:48 PM Airport = CSB3 St-Mathieu-De-Beloeil
12:47:48 PM AddNode!
12:47:48 PM Calculating route!
12:47:48 PM CalculateRoute: fr each node
12:47:48 PM CalculateRoute: first node
12:47:48 PM CalculateRoute: GetDefaultStartPos
12:47:48 PM CalculateRoute: DefaultStartPosition done
12:47:48 PM CalculateRoute: Heading and ground speed
12:47:48 PM CalculateRoute: magvar
12:47:48 PM CalculateRoute: FINAL MEF calc
12:47:48 PM CalculateRoute: FINAL extend for diatance
12:47:48 PM CalculateRoute: done12:46:25 PM Connect button clicked
12:46:25 PM Testing mFSConnect.IsConnected
12:46:25 PM Calling ConnectToSimConnect
12:46:25 PM Checking SimConnect properties.
12:46:25 PM Initialising event handlers
12:46:25 PM Calling mFSConnect.Connect.
12:46:25 PM Connecting.
12:46:25 PM Initialising data request.
12:46:25 PM SimConnect event handlers & data definitions initialised
12:46:25 PM SimConnect connection established.
12:46:25 PM Requesting Plan weather for CSB3 St-Mathieu-De-Beloeil
12:46:25 PM Requesting Plan weather for ZHU HAUTS-BOIS (MONTREAL) (407 KHz)
12:46:25 PM Requesting Plan weather for CYHU Montreal/St-Hubert
12:46:25 PM Connected to FSX
12:46:25 PM SimConnect Exception received: WEATHER_UNABLE_TO_GET_OBSERVATION
12:46:25 PM SimConnect Exception received: WEATHER_UNABLE_TO_GET_OBSERVATION
12:46:25 PM
PLAN WX OBSERVATION: %sCYHU&A26 011620Z 05102KT&D63NG 06002KT&A887NG 06103KT&A1801NG 06603KT&A2716NG 06604KT&A3630NG 06805KT&A5459NG 06606KT&A7288NG 06809KT&A9117LG 06908KT&A10336NG 07308KT&A11860NG 14KM&B-1526&D1974 CLR 14/11 07/03&A887 02/00&A1801 -3/-5&A2716 -8/-11&A3630 -20/-22&A5459 -32/-34&A7288 -45/-47&A9117 -53/-55&A10336 -57/-60&A11860 Q1021 @@@ 30 7 60 2 | 60 2 61 3 | 90 -3 66 3 | 120 -8 66 4 | 180 -20 68 5 | 240 -32 66 6 | 300 -45 68 9 | 340 -53 69 8 | 390 -57 73 8 |
12:46:25 PM DisplayFlightPlanDetail: StartPosition
12:46:25 PM DisplayFlightPlanDetail: TAS
12:46:25 PM DisplayFlightPlanDetail: totalDist
12:46:25 PM DisplayFlightPlanDetail: totalTime
12:46:25 PM DisplayFlightPlanDetail: WindDirection
12:46:25 PM DisplayFlightPlanDetail: Altitude
12:46:25 PM DisplayFlightPlanDetail:
12:46:25 PM DisplayFlightPlanDetail: checking weather
12:47:38 PM DisplayFlightPlanDetail
12:47:38 PM No plan - erasing line
12:47:48 PM AddAirportToPlan -1
12:47:48 PM Airport = CSB3 St-Mathieu-De-Beloeil
12:47:48 PM AddNode!
12:47:48 PM Calculating route!
12:47:48 PM CalculateRoute: fr each node
12:47:48 PM CalculateRoute: first node
12:47:48 PM CalculateRoute: GetDefaultStartPos
12:47:48 PM CalculateRoute: DefaultStartPosition done
12:47:48 PM CalculateRoute: Heading and ground speed
12:47:48 PM CalculateRoute: magvar
12:47:48 PM CalculateRoute: FINAL MEF calc
12:47:48 PM CalculateRoute: FINAL extend for diatance
12:47:48 PM CalculateRoute: done
===================================

So, PlanG "thinks" it's connected to my FSX, but it's not, really.

Hoping for a solution soon!

- Jeff Schallenberg
Mont Saint-Hilaire, Québec

[tim arnot]

It's definitely connected, because it's pulling back weather observations. As I said above, you need to enable the aircraft icons in Options.

[robcap]

WOOOHOOO TIM!!!

beta 362 has me connected.
I also at first had no dice, and the 10.0.60905 did not connect.
I deleted the entry form Winsxs, as you indicated in the post by Andre.
Then I re-installed from the SDK. Now I'm off exploring the other possibilities.

See attached log file.

I also like that you fixed the pop-up for the Google earth application loading. Now everything just start's-up as intended.


Cheers mate, and thanks for this great product. I will follow up on the developement.

[jschall]

OOOPS!

This is new behaviour with version 362.

It won't connect anymore (358 was connecting fine).

Here is the relevant output from the log file:

5:28:07 PM Connect button clicked
5:28:07 PM Testing mFSConnect.IsConnected
5:28:07 PM RibbonButton_Click_ConnectFS exceptionSystem.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.FlightSimulator.SimConnect, Version=10.0.60905.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.FlightSimulator.SimConnect, Version=10.0.60905.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   at Plan_G.FSConnect.get_IsConnected()
   at Plan_G.Window1.RibbonButton_Click_ConnectFS(Object sender, RoutedEventArgs e)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Here again are the simconnect.dll folders on my PC:

C:\WINDOWS\WinSxS\x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.60905.0_x-ww_429211e9
C:\WINDOWS\WinSxS\x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.61242.0_x-ww_35e8ee9a
C:\WINDOWS\WinSxS\x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.61259.0_x-ww_fb842f5a

So, is it because the keys are not acceptable to Plan-G v. 362?

Your suggestions would be appreciated.

- Jeff Schallenberg
Mont Saint-Hilaire, Québec

[andre]

Hello

I did :


Posts: 121



View Profile Email Personal Message (Offline)
   
   
Re: Simconnect
« Reply #10 on: August 31, 2009, 04:12:43 PM »
   Reply with quote

The file it is complaining about is 60905, which is one of those you listed. Which means it's not a simple problem of trying to load a different version of SimConnect to the one you have.

One suggestion I can make is that you try a slightly older build (355): http://www.tasoftware.co.uk/plan-g/files/PlanG_Beta0.zip


and now the plan-g is working.

I see my plane , the plane is moving

i am happy , the plan-g work  ;D ;D ;D

all run well

thank you

andre

[jschall]

Well, I fixed the problem with Plan-G, but created another problem...

I deleted the 3 folders under WinSxS listed above, and re-ran SimConnect.msi.

But which one to run?

I found EIGHT copies of SimConnect.msi on my WindowsXP SP3 /FSX SP2 system:

C:\Program Files\FSX Google Earth Tracker\lib (v10.0.61259.0)
C:\Program Files\FSMap\SimConnect\RTM (v10.0.60905.0)
C:\Program Files\FSMap\SimConnect\SP1 (v10.0.61242.0)
C:\Program Files\FSMap\SimConnect\SP2 (v10.0.61259.0)
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Tileproxy (v10.0.61242.0)
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\lib (v10.0.61259.0)
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM (v10.0.60905.0)
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1 (v10.0.61242.0)

So, there are 3 different versions on my system, some of them supplied with other FSX add-ons like FSMap.

I chose the one you recommended, the RTM version in the SDK.

And that fixed Plan-G.

BUT it disabled one of my essential FSX add-ons, FS-Force (http://www.fs-force.com), which refuses to load because it can't find SimConnect  :'(

I am sure I can get FS-Force working again, but it may interfere with Plan-G if it installs a second version of SimConnect! In the FS-Force documentation, they recommend the version in "C:\ ... \SDK\Core Utilities Kit\SimConnect SDK\Lib", which is the most recent version 10.0.61259.0.

IMHO, Plan-G's installer should look for the most recent SimConnect, and so avoid this kind of installation problem.

I will let you know how I make out with FS-Force...

Update: I completely uninstalled FS-Force and re-installed it from their web page. But it still cannot find SimConnect.

My next step is to run the version 10.0.61259.0 of SimConnect.msi...

- Jeff Schallenberg
Mont Saint-Hilaire, Québec

[tim arnot]

You should run each version of the MSi in turn (RTM, SP1 then SP2), and everything will be happy.

We do not use the SP2 version of Simconnect because not all our users are running SP2, and we have no reason to force them to use it against their wishes.  ;)

[jschall]

All's well that ends well.

I ran the version of SimConnect.msi recommended by FS-Force, and  it added a second version in WinSxS. It didn't bother Plan-G.

I still respectfully think the Plan-G installer could look for the "best" available version of SimConnect on the target system, not the lowest common denominator, avoiding the hassle that several users have just gone through.

- Jeff Schallenberg
Mont Saint-Hilaire, Québec

[Gloster Approach]

Well wadda ya know! It works. I can connect my laptop to FSX on my main PC. Just thought it might help if I added my set up. I installed FSX last year from the package that was re-released as a bundle (FSX deluxe with all the patches incorporated plus Acceleration).

In this installation the version of simconnect installed by the .msi file in the SDK is 60905. The SDK/simconnect files were installed on the laptop directly from the disk.

[picnic]

I've also got an XP SP3 PC that fails to load simconnect 60905 even though it exists within my WinSxS structure. One thing I noticed it that my registry thinks the PublicKeyToken for 60905 is 67c7c14424d61b5b where as the error Plan-G generates says the PublicKeyToken is 31bf3856ad364e35

I expect I'm taking rubbish but I'm loath to simply delete the WinSxS folders as there are numerous entries in the Registry associated with these various versions.

[tim arnot]

If it helps, move it somewhere else rather than delete it. I've moved that folder and put it back masny times in the course of testing, with no adverse effects. But if you run the installer while that folder is still in place, it won't be reinstalled. It's not the dll itself that's important (there are clear copies of it on the dvd), but all the extra guff that goes in the registry etc, and that's what gets broken.

[picnic]

I've now deleted the 3 WinSXS folders and just installed the RTM SimConnect.msi. My SimConnect debug log still says I'm running a later version so I assume FSX itself is not running a version in the WinSxs as there is only the RTM version there now  ??? However what ever state it is in now Plan-G is talking to FSX :)

Any idea what breaks the installation/registry entries for this Tim?

[tim arnot]

No. Just that it's "fragile".