@RPGamerous said in Avidyne IFD 550/540 in Black Square addons:
"The entire JS engine isn't designed to just be reloaded at random during flights. So even third party instruments should not be trying to implement a hot swap feature."
I'm going to tread very lightly here, because I am not an expert in how all these avionics work, but I have created my own hot-swapping features for my RNAV computers and Starship, and it did not require rebooting the entire JS engine. As far as I'm concerned, the only "hot-swapping" features that are necessary are: 1. Stop writing to output SimVars, such as AP variables, CDI, GPS data, etc., and 2. Minimize code execution and memory usage.
As far as I can tell, this is what third party avionics do, and as long as we respect each other's "locks" on GPS OVERRIDDEN, and AVIONICS MANAGED, it all seems to work swimmingly.
HOWEVER: I'm sure I'm oversimplifying based on my own avionics, which don't have to support nearly the number of features or target platforms that Working Title's do, so please do no misinterpret my commentary to be anything more than my own observations. I understand the pain of MSFS development intimately, so I respect whatever challenges WT faces, and whatever decisions they have arrived at, no doubt with much contemplation. I suspect the rub might be with their internal autopilot implementation, since it's one of the things that sets them apart from these other 3rd party avionics developers, but don't quote me on that.