Thank you for the kind words. The FMS won't have enough data to perform its calculations without all mandatory fields being completed (including Cost Index). I know we do have an "INITIALIZE COST INDEX" scratchpad message simulated that generates if all other mandatory fields have been completed, but I'm not too sure what the real aircraft would calculate if no Cost Index is entered. We'll make a note to investigate that further. Mark - Just Flight

We don't natively support any external FMS hardware or software at this time. However, we do recognise that FMS hardware and software have become more accessible to larger parts of the community in recent years, and supporting them in our products is something that we have logged on our internal feature request trackers for evaluation. Mark - Just Flight

Thanks for reporting this. We have just taken a look at this, and we believe we've found a scenario where that can occur. That's now logged on our internal trackers, and we'll include a fix in a future update to the product(s). Mark - Just Flight

I will if and when it recurs, thanks Martin.

Thank you for the feedback. We have logged this on our internal trackers, and we'll look into this for a future update. Mark - Just Flight

This would be great! The Warrior I fly has a GTN650 and dual G5's and this would make it so much better. I have the TDS GTN package but would be so much better with dual G5's also. Just Flight...........please make this happen!

Lmao yeah, I was just being grumpy

@Chimaeira Yes, I muddled it over for a while before deciding to purchase one. Glad I did though, it is a nice piece of hardware.

It makes sense, but in any case, the manual doesn't explain it well; it was a copy-paste from the original manual, and they didn't even notice that this version has "auto" instead of "cont1." Another thing is that there's no information on the MFDU indicating that the ignition is on, as the manual also states.

Breaking: I found a way to solve the problem It can probably be done smarter, but the way it was solved was to delete (or rename) the Packages folder, MSFS will rebuild it after a restart, copy Bsq King Air and Asobo King Air from MSFS2020 to the Community folder and restart the sim. I am soooo happy, because now I can run the Gps via Glassout. And it turned out that I was not the only one with this problem, my brother in law had the same problem. But @Black-Square : pretty pretty please with sugar on the top: please release a 2024 version. I got cat pictures

It's not so much a question of "do we have failures or don't we", but rather how deep the system simulation is. To me, deep system simulation means the systems need to behave realistically when things go wrong or when a pilot mistake is made. Like others have said above, what's the point of coding deep system fidelity if nothing is ever out of the ordinary. And by that I don't just mean catastrophic events that force you to land immediately. It's more like the little things that happen on a daily basis in airline operations. Chances for a hot start, HYD pressure that can drop for whatever reason, INS issues, a pack that runs hot... just things so that system monitoring and checklists have meaning. Without that, it's hard to enjoy deep system simulation, because there's no reason for it to exist when no parameter can ever go out of line. So yes, please, add system failures, errors, acting up, randomness. I have no problem with paying extra for this. It's just that flying with knowing nothing can ever go wrong is, how should I say, not very fulfilling.

We intentionally link the brightness of the forward galley lights to the cockpit door position to prevent light from bleeding into the cockpit when the cockpit door is closed. Therefore, with the cockpit door closed, the forward galley lighting controls will not have any effect. When the cockpit door is open, the cabin lighting controls will all be fully functional. Mark - Just Flight