Intermittent garbage flight identifiers for traffic with MSFS 2020 and ForeFlight

[astenlund]

Intermittent garbage flight identifiers for traffic with MSFS 2020 and ForeFlight

[brion]

I added some debug output to DataSender.cs and it looks like the strings are already garbage at that point, so it may be in the data marshalling via SimConnect.

airline: 0â’Ã4k2Ãíb�ÃÒ_7ÃíÀ�ÊpBÃäõŽÃöä=à flight: 133 tail: SWA133 out: XTRAFFICMSFS,3353,37.69818,-122.20931,174.5,-822.1,1,310.069,156.1,0â’Ã4k2Ãíb�ÃÒ_7ÃíÀ�ÊpBÃäõŽÃöä=à 133
airline: Skywest flight: 3357 tail: SKW3357 out: XTRAFFICMSFS,3416,37.69227,-122.32688,1515.2,-846.2,1,207.941,156.1,Skywest 3357
airline: íÀ�ÊpBÃäõŽÃöä=à flight: 2185 tail: QXE2185 out: XTRAFFICMSFS,3419,37.55457,-121.95625,16956.4,6.8,1,353.015,342.5,íÀ�ÊpBÃäõŽÃöä=à 2185
airline:  E=<	� flight: 47 tail: HAL47 out: XTRAFFICMSFS,1924,37.72932,-122.21379,12.7,0,0,132.424,7.8, E=<	� 47

SWA - Southwest
QXE - Horizon Air
HAL - Hawaiian Airlines

[brion]

The garbage characters are consistent for a given plane across invocations, which makes me think MSFS is just sending garbage data -- if it was a marshalling problem I'd expect different garbage on different invocations as structures got re-allocated.

Worst case: heuristic check for non-ASCII characters, and count that as invalid data for the Airline field. If the source data is guaranteed to be ASCII, that should clear it up mostly. :)

[brion]

Good news: this seems to have been resolved in the recent sim update! No longer seeing this happen, so no need to correct for it. Closing.