Autopilot issues when using TDS GTNXi

[coldnebo]

Hello,

We thank you for your input, however, the TDS GTNXi is NOT using the default Asobo autopilot logic. This is a misconception that we want to clear up, we have our own, custom coding based on how the real unit behaves. We will definitely look into proving all logic where there is room for improvement.

I had a similar problem with the KAP140 autopilot and we traced to the TDS tray app. 

During the investigation I cleared my Community folder and uninstalled many mods from Marketplace. Not even the tds-gtnxi-gauge was installed.  But I forgot that I had added the TDS app to exe.xml startup, so the TDS tray app was running minimized.  When we finally saw that, I tried running without the TDS app and everything worked normally.  I then looked at the TDS Manager and saw that I was behind by a few updates.  I updated the TDS, renabled the mod, ran the tray, and then the Asobo C172 steamgauge KAP140 worked normally.

This issue was first tracked on the JustFlight support forums, then WBSim, then WorkingTitle, and finally the MSFS Forums. It has taken months of investigation and discussion to find this issue.


My guess is that the TDS tray app is using Simconnect events to establish a handshake or at least react to the tds-gtnxi-gauge mod being activated in the sim?  

For some reason the old tray app reacted to re-engaging the AP by (I think) sending a quick series of events that broke the KAP 140 in the Asobo C172 steamgauge aircraft.  I don't know the details of this, but we have a video recording showing how simply starting the TDS app breaks the KAP 140 reengage in a way that could only be cleared by restarting the flight.

But guesses aside, it would be nice to know what's really going on.