Thanks, @gazdav787 I think I've found the cause. My code has the form 1·(>L:GNLU910_L_FMS_XXXXX_ANIM,·Number) (WAIT:150) 0·(>L:GNLU910_L_FMS_XXXX_ANIM,·Number) But in this case is not necessary to come back to 0

Same here, I can't get my Logitech Radio Panel to work with the Dukes (in MSFS2024). I then exited the flight, launched in with a default Asobo aircraft and the radio panel worked fine, so then exited that flight and launched back into the Duke and the panel went off. I confirmed that Master and Avionics switch positions didn't seem to make any difference ... so not sure what's going on there as it's OK with other aircraft (although standby frequency selection currently doesn't work in the FenixSim A320).

Thanks for the quick reply :).

I would like to join the party here. This airplane is absolutely amazing! The detailed work with the external as well as internal model as well as with the flight physics and the engine, failures etc. - really top notch!

Any update on this? Also the yoke's chrono wont turn on and the KN 62A DME while turns on doesn't display any info. Ah and the autopilot on Nav mode wont follow the tuned VOR for the selected radial. When I turn the cuopler knob to NAV it snaps back to to hdg.

@Black-Square 2-4 months! Might as well spend more to buy that time then. I think its a better way to support the dev as well but obviously the surplus conversion rates are going to govt. Nevertheless, 2-4 months is quite substantial

@KarsPilot If you contact Just Flight about this we will be happy to discuss: https://www.justflight.com/contact-us

I agree it would be great to remove the KNS81... I get your point, but in reality no one I could think of would keep a KNS81 when fitting e.g. a GTN750. Also, you can easily check your navigation with your Navigation Software like Navigraph. That all being said, could you maybe explain how to remove the KNS "with the gap"? I figured with my avionics layout it wouldn't hurt too much. Also, is it possible to remove the MD41-328? Not that helpful with a GTN xD Kind Regards, Jannik S.

Thank you for your willingness to resolve any issues we report to you.

I suspect it’s a problem in Wwise where the position is set wrong for certain objects which Windows spatial doesn't use.

Yep - it's real taxiways. First pic is real taxiways on and 2nd pic is with it off. I've noticed this at a few other airports too - just kept forgetting to report it. Hopefully it's a code fix and not just one off fixes. It's always the sign that's wrong. [image: 93b6eb0d-5023-4f78-b50b-54601c0868ec.jpg] [image: a004a75d-9ee3-47e0-a88c-8dd65ea043c5.jpg]

I think that behavior might actually be expected. The continuous-flow masks are only effective up to about FL250. As you approach that altitude the oxygen partial pressure becomes too low for the mask to maintain normal blood oxygen saturation, so the SPO2 reading starts to drop. The FL250 ceiling is basically the altitude where the system can still keep the pilot functional, not necessarily at 90% saturation. For extended flight, most guidance recommends keeping SPO2 around 90%, and increasing oxygen flow or descending if it starts dropping into the high-80s.

Not sure you read the thread (particularly Nick's responses rather than my drivel), but those vars aren't (or weren't) being exposed, they're only internal. So AAO/SPAD/Mobiflight can't see them, at least not until you make the changes to expose them that Nick and I talk though up above. All sorted now though!

@hunterdouglas I think this is something that Just Flight support would be best placed to help with. See: https://community.justflight.com/topic/2/product-support

As long as it's an option - and not forced upon the user -, it's fine. I personally don't want anything turning red, blue, etc.