Hi,
OK, Ive had chance to take a look a little further.

Firstly the crash happens both when right clicking the navaid or when using the radio stack ( the radio stack does reflect the cockpit panel frequencies correctly).
Whilst I dont have a large sample size the crash occurs 100% of the time.

I tried switching to the P3D connect method (which I believe just needs the connect method changing in the connection options - and no changes to config file). This results in the error:-

15:05:39.7 SetFSConnected: System.BadImageFormatException: Could not load file or assembly 'LockheedMartin.Prepar3D.SimConnect, Version=3.4.0.0, Culture=neutral, PublicKeyToken=null'. An attempt was made to load a program with an incorrect format.
File name: 'LockheedMartin.Prepar3D.SimConnect, Version=3.4.0.0, Culture=neutral, PublicKeyToken=null'
   at Plan_G.Model.lm_SimConnect.Connect(IntPtr myWindow)
   at Plan_G.ViewModel.MainViewModel.SetFSConnected(Boolean value) in C:\Users\Tim\source\repos\Plan-G\ViewModel\MainViewModel.cs:line 5425

As you rightly suspected, the log file doesnt help, it just stops dead at the time of the crash:-

---===+++ 30/09/2020 +++===---

15:04:22.4 Starting Plan-Gv4 build 4.0.0.228
15:04:22.4 OS is Microsoft Windows NT 6.2.9200.0
15:04:22.4 Plan-G Files folder is: C:\Users\garet\OneDrive\Documents\Plan-G Files
15:04:25.9 Map tiles cache: C:\Users\garet\AppData\Local\GMap.NET\
15:04:26.3 Map provider: BingMap © 2020 Microsoft and its suppliers. All rights reserved.
15:04:26.3 Map cache mode: ServerAndCache
15:04:26.8 Program in: C:\Local\Plan-G v4
15:04:26.8 Data in: C:\Users\garet\OneDrive\Documents\Plan-G Files
15:04:26.9 Starting timer
15:04:26.9 DownloadCurrentMetars thread started
15:04:26.9 Metar14Z.TXT started
15:04:26.9 Metar13Z.TXT started
15:04:29.4 Stopping timer
15:04:29.4 StartMap
15:04:32.7 NdbsInBounds 0
15:04:33.0 VorsInBounds 1
15:04:33.4 AirportsInBounds 1
15:04:33.7 AirspaceInBounds 18
15:04:34.0 NdbsInBounds 0
15:04:34.1 VorsInBounds 1
15:04:34.1 AirportsInBounds 1
15:04:34.3 AirspaceInBounds 18
15:04:34.7 Metar14Z.TXT done
15:04:34.9 Initiating SimConnect FSX connection.
15:04:35.2 SIMCONNECT_RECV_OPEN
15:04:35.2 SimconnectOnRecvOpen Connected to P3D/FSX
15:04:35.2 Connected to sim
15:04:35.4 Traffic update:6 planes
15:04:35.5 Transponder: 30292
15:04:35.8 NdbsInBounds 0
15:04:35.9 VorsInBounds 0
15:04:36.0 AirportsInBounds 0
15:04:36.1 AirspaceInBounds 12
15:04:36.6 Metar13Z.TXT done
15:04:36.6 DownloadCurrentMetars done
15:04:39.5 ProcessMetars done
15:04:54.1

---===+++ 30/09/2020 +++===---

When running Plan-G on a second computer using the option to set NAV or COM frequencies correctly changes the appropriate radio within MSFS ( ie I can see the frequency change on the cockpit display ) but then the remote Plan-G then crashes to desktop.

I have tried the same test on a copy of 228 running locally ( ie on the same PC as MSFS ) and the frequency is changed but Plan-G does not crash to desktop.

Seems only to be a problem when running Plan-G remotely via simconnect.

How weird. Always happy to try anything out if I can be of help.

Re the AI traffic - it was more a general question, I was curious if the other "remote" users were seeing the same or whether it was just me before I raised it as an issue.  I will do some more checks later (eg see if V4 running locally shows the traffic ) and start a new thread as requested.

Thanks

Thanks for the detailed reply (although I think it is the latest release that fixed the problem so my question was directed to Tim )

However, I wonder - do you see "AI" traffic being displayed? I have enabled it in "options" but I still see no AI traffic being displayed.  Traffic does exist and it is still displayed correctly in the old version 3 software but not in V4

Brilliant :-)

228 Working for me too, great news!

Out of techy curiosity, any idea what the issue was?

Not chance to do the further testing as we discussed - but have just tried 225, same problem

But what version and build of Windows are you using?

Thanks, quick!

Just tried it on the copy I have on my laptop, gives an error....

corflags : error CF008 : The specified file does not have a valid managed header

I tried running corflags on itself and got the same message - so it likely means nothing.

Sorry, I also meant to add that whilst "googling" I came across something called CorFlags.exe, part of the dotnet SDK apparently, allows you to configure an EXE to force it to run as 32bits ( clearly aimed at misbehaving 64bit apps). I was wondering there is any benefit in trying it, whether it would prove anything.

If so, I dont suppose you have a copy in your development enviroment to share - to save me having to install the entire SDK that I have no use for?

Hi,
Unfortunately I am running out time now and wont be able to do much other than follow this thread ( and try anything out on my W10 laptop - but wont have any access to a running FSX/MSFS system until next weekend).

The client is just  low powered little box - its only roll is to run Plan-G on a separate monitor. No flightsim on there - it'd run like a dog but might be enough to test your theory! I cant think of anything else I have that uses simconnect (unless you can jog my memory what may use it -I have a load of arduino stuff I started playing with ages ago but from memory I think that was FSUIPC and WIDEFS.


I dont have the FS system running at the moment but tried V3 on the client with it set to connect to P3D, interestingly it reported.....

20:15:40.2 Initiating SimConnect P3D connection.
20:15:40.2 SetFSConnected: System.IO.FileNotFoundException: Could not load file or assembly 'LockheedMartin.Prepar3D.SimConnect.dll' or one of its dependencies. The specified module could not be found.
File name: 'LockheedMartin.Prepar3D.SimConnect.dll'
   at Plan_G3.Model.lm_SimConnect.Connect(IntPtr myWindow)
   at Plan_G3.ViewModel.MainViewModel.SetFSConnected(Boolean value)

I then tried V4 222 and it reported:-

20:12:02.8 Initiating SimConnect P3D connection.
20:12:02.9 SetFSConnected: System.BadImageFormatException: Could not load file or assembly 'LockheedMartin.Prepar3D.SimConnect, Version=3.4.0.0, Culture=neutral, PublicKeyToken=null'. An attempt was made to load a program with an incorrect format.
File name: 'LockheedMartin.Prepar3D.SimConnect, Version=3.4.0.0, Culture=neutral, PublicKeyToken=null'
   at Plan_G.Model.lm_SimConnect.Connect(IntPtr myWindow)
   at Plan_G.ViewModel.MainViewModel.SetFSConnected(Boolean value) in C:\Users\Tim\source\repos\Plan-G\ViewModel\MainViewModel.cs:line 5431

Thats about as much as I can do until next weekend - if you think of anything Id be happy test it out on my W10 laptop, even if its only to try and get the elusive "HRESULT E_FAIL" result!

Thanks for your efforts

Gareth

Thanks for the update, makes sense.  I have just loaded it onto the plan-G computer, Sadly Im afraid the result isnt any better.

I have also just tried running it in "compatability" mode for W8, W7 and XP - all with the same result.



---===+++ 12/09/2020 +++===---

18:51:56.7 Starting Plan-Gv4 build 4.0.0.222 32-bit
18:51:56.7 OS is Microsoft Windows NT 6.1.7600.0
18:51:56.7 Plan-G Files folder is: C:\Users\garet\OneDrive\Documents\Plan-G Files
18:52:00.9 Map tiles cache: C:\Users\garet\AppData\Local\GMap.NET\
18:52:01.5 Program in: C:\Local\Plan-G v4-222 32bit
18:52:01.5 Data in: C:\Users\garet\OneDrive\Documents\Plan-G Files
18:52:02.1 Starting timer
18:52:02.1 DownloadCurrentMetars thread started
18:52:02.2 Metar17Z.TXT started
18:52:02.2 Metar16Z.TXT started
18:52:04.7 Stopping timer
18:52:04.7 StartMap
18:52:05.1 MEFs: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\MEF.db'
18:52:06.6 Metar16Z.TXT done
18:52:08.6 NdbsInBounds 0
18:52:08.7 VorsInBounds 0
18:52:08.8 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
18:52:09.6 AirportsInBounds 0
18:52:09.7 AirspaceInBounds 0
18:52:09.8 MEFs: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\MEF.db'
18:52:10.0 NdbsInBounds 0
18:52:10.0 VorsInBounds 0
18:52:10.1 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
18:52:10.1 AirportsInBounds 0
18:52:10.2 AirspaceInBounds 0
18:52:10.5 Metar17Z.TXT done
18:52:10.6 DownloadCurrentMetars done
18:52:10.9 Initiating SimConnect FSX connection.
18:52:11.0 SetFSConnected: System.BadImageFormatException: Could not load file or assembly 'Microsoft.FlightSimulator.SimConnect, Version=10.0.61259.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. An attempt was made to load a program with an incorrect format.
File name: 'Microsoft.FlightSimulator.SimConnect, Version=10.0.61259.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   at Plan_G.Model.SimConnect_FSX.Connect(IntPtr myWindow)
   at Plan_G.ViewModel.MainViewModel.SetFSConnected(Boolean value) in C:\Users\Tim\source\repos\Plan-G\ViewModel\MainViewModel.cs:line 5421


18:52:13.6 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
18:52:13.7 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
18:52:14.6 ProcessMetars done
18:52:33.0 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
18:52:34.1 Cleanup

Righty, I can confirm that the 32 version of 221 does not connect, results in the same error as per the log below

My Simconnect.cfg file ( which is located in the same directory as the Plan-G Binaries ) looks like this

[SimConnect]
Protocol=IPV4
Address=192.168.1.16
Port=4506
MaxReceiveSize=4096
DisableNagle=0

which matches the settings in the working version 3 and the simconnect.xml.

The Plan-G logfile is below - if I understand what it is complaining about is that it cannot find the 64bit simconnect DLL.....which from your comments it shouldnt be?

As an side, once you press the "connect button" and the error is produced the connect button continues to be greyed out with only the disconnect being available - it doesnt time out trying the make the connection as V3 would if there was a genuine comms issue.

--------------------------

16:10:02.2

---===+++ 12/09/2020 +++===---

16:10:02.2 Starting Plan-Gv4 build 4.0.0.221 32-bit
16:10:02.2 OS is Microsoft Windows NT 6.2.9200.0
16:10:02.2 Plan-G Files folder is: C:\Users\garet\OneDrive\Documents\Plan-G Files
16:10:04.9 Map tiles cache: C:\Users\garet\AppData\Local\GMap.NET\
16:10:05.6 Program in: C:\Local\221\Plan-G v4 32bit
16:10:05.6 Data in: C:\Users\garet\OneDrive\Documents\Plan-G Files
16:10:05.7 Starting timer
16:10:05.7 DownloadCurrentMetars thread started
16:10:05.8 Metar14Z.TXT started
16:10:05.8 Metar15Z.TXT started
16:10:08.2 Stopping timer
16:10:08.2 StartMap
16:10:08.5 MEFs: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\MEF.db'
16:10:09.0 Cleanup
16:10:09.4 Metar15Z.TXT done
16:10:12.3 NdbsInBounds 0
16:10:12.3 Metar14Z.TXT done
16:10:12.4 DownloadCurrentMetars done
16:10:12.4 VorsInBounds 0
16:10:12.6 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
16:10:13.4 AirportsInBounds 0
16:10:13.5 AirspaceInBounds 0
16:10:13.6 MEFs: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\MEF.db'
16:10:13.8 NdbsInBounds 0
16:10:13.9 VorsInBounds 0
16:10:13.9 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
16:10:14.0 AirportsInBounds 0
16:10:14.0 AirspaceInBounds 0
16:10:14.5 Initiating SimConnect FSX connection.
16:10:14.7 SetFSConnected: System.BadImageFormatException: Could not load file or assembly 'Microsoft.FlightSimulator.SimConnect, Version=10.0.61259.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. An attempt was made to load a program with an incorrect format.
File name: 'Microsoft.FlightSimulator.SimConnect, Version=10.0.61259.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   at Plan_G.Model.SimConnect_FSX.Connect(IntPtr myWindow)
   at Plan_G.ViewModel.MainViewModel.SetFSConnected(Boolean value) in C:\Users\Tim\source\repos\Plan-G\ViewModel\MainViewModel.cs:line 5421


16:10:15.6 ProcessMetars done
16:10:17.1 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
16:10:17.3 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
16:10:29.9 User Waypoints: Data Source = 'C:\Users\garet\OneDrive\Documents\Plan-G Files\Data\UWpts4.db'
16:11:01.0 Cleanup
16:11:57.9

Thanks for the reply.
The firewall is open here (and likely also for the other user) - it has to be for the V3 software to work (which it does as with both FSX and MSFS as per my findings this morning).

I dont believe its a firewall issue for that reason - and, unless the error message is incorrect, the error suggests some other issue. The error also occurs without any simconfig.cfg file being present on the remote computer - which I am guessing means it would either error or, as seems to happen when run locally, attempts to connect via a pipe? I say this as the latest built that I tested this morning worked happily on the local MSFS computer without any config file.

Whilst I appear not to have noted it in my earlier posting, I did try both the 32 and 64 bit versions connecting remotely to both FSX and MSFS - both produced the same error.  My gut feeling is that all versions are failing long before actually attempting to make the network connection

I will go and double check the 32 bit connection to FSX but I am reasonable sure it failed with the same message (you may recall I tried 218 version week for the reasoning ).

Will report back shortly

Turning into a real mystery this one !  :o

OK, as promised a coherent set of notes.  I have attempted to start afresh and rule out any confusion from previous installs etc.

The Plan-G computer is a
Gigabyte Brix GB-BXBT-1900 , a Celeron J1900 @ 2GHz 8GB Ram
Windows 10 Pro - Version 2004, Build 19041.508

The Flight Sim computer is a
Intel i7-9700K @ 3.6GHz ( Overlocked and is stable at 5GHz )
The motherboard is Asus Prime Z370-P II
16GB RAM

Both are ringfenced and neither have antivirus running and just the inbuilt firewall.


The Plan-G computer used to Run W7 Pro on an HDD but in an attempt to resolve the problem a few days ago it was installed with a fresh download of W10 on a new SSD ( so nothing inherited from W7 whatsoever).


This morning I removed the existing Plan-G V4 folders, including those under "Users"

I did a fresh download and install of V3.2.2.167  and configured it using the inbuilt options to connect to 192.168.1.16, IPV4 port 4506. I ran it once, to create the folders and then re-ran it after I had copied over PlanG3_FSX.sdf (only) from the old W7 HDD

I then ran FSX-SE on the Flight Sim computer and checked the remote connection - works fine. I then stopped Plan-G and FSX, started MSFS and then Plan-G - again, the remote connection worked fine.

So at this stage V3 is working remotely with FSX and MSFS

The Flight Sim computer
----------------------

Next I removed Plan-G from the Flight Sim computer and did a fresh download of V221 (note that I did not remove the files from under "user" ).

At this stage I did not create simconnect.cfg.

I ran the 32bit version and let it organise the 32bit Netcore download.

I started MSFS and got it to the point where it was "ready to fly". Connected Plan-G and it happily connected and display the location correctly.

I then did the same with the 64Bit version - with exactly the same results

So both 32 and 64 bit version work fine "locally"


Back to the Plan-G computer
---------------------------

I did a fresh download ( ie didn't copy from the other computer) of 221 onto the plang computer.  I have not copied the MSFS datafiles.

Ran the freshly installed 32 bit version - same error as before, ditto with the 64bit version

Tried both versions a second time using "run as administrator" - same issue.

Laptop.

I have a W10 pro 64bit laptop ( an I5 as I recall )  that is completely unrelated to the Flight Sim setup and has never had anything installed on it. I put V221 64bit version on it - exactly the same problem.


Thoughts.......

I notice that 221 shipped the simconnect DLL with the 64bit version and that the 32bit doesn't require it - so that rules out any issues with the SDK that MSFS downloaded here.

I am wondering if the message that's being produced is actually wrong or misleading - and the error may be something other than a file in the wrong format, eg a missing file ( I note that there are multiple copies of the simconnect dll in various places ).

I am wondering if there is something else installed or done by the SDK, or MSFS install,  that is not present on the non-MSFS computers and causing problems.  I know you said your laptop works OK - has it ever been used for development or had anything installed on it? Just trying to work out why that one works but others don't.

There is a an older discussion here (which whilst I don't profess to fully understand looks like it may have some relevance but it may mean something to you)...... https://forum.simflight.com/topic/90224-simconnectdll-location-setting/

Not sure that helps much but at least I hope it was an organised fresh attempt to work out what works and what doesn't.

Gareth

I have just had a quick look at 221 and it suffers the same error as before (both 32 and 64bit).

Re the other users comments - if you recall I had this issue on W7 before upgrading to W10, I dont think its a W7 Plang to W10 MSFS issue.

I have just installed PLanG on my W10 laptop and it also has the same problem ( W10 Pro, 64 Bit ) - tried both the 32 and 64 bit version.

I do not have an antivirus (other than the inbuilt Windows Defender ) on the PlanG or MSFS computers ( they are ringfenced - the antivirus overhead is something I dont need), as previously stated PlanG V3 was working on a dedicated PC connecting to MSFS and FSX on the Flightsim PC - so I dont believe it is a firewall issue.

I did take a look at procexp64 to see if there was some odd file or DLL being used that was present locally on the MSFS computer but not on the newly built W10 Plang computer - nothing obvious.
Tomorrow will be my last chance to investigate until next weekend but I will try and and do a little research and try and get you a coherent set of results, logs etc.