I hope this will be made available for purchase. This would make for an awesome addon for the addon. A G3X mod would be a Day 1 pucrhase of the Bonanza PLUS the mod for me.

Indeed, sounds like a fuel leak failure. Check the failures page of the tablet interface for "active failures", or click "reset all failures."

Many thanks for the reply. Apologies, I should have included the fact I’m on Xbox. So no option to interact with all those lovely variables accessible to PC users. It varies between addons which status lights work on the Turtle Beach “SIP”. All lights work for many a/c. It’s a fantastic feature for those of us on Xbox, for instance when the landing gear is in motion the corresponding light illuminates yellow, turning green when down and locked. The Master Caution and warning lights always strike me as odd as not working in the Black Square modules. Although it’s all a black art to me - I’m sure there is a very sensible reason! I’ve played flight sims on PC for 20+ years, but am largely content on Xbox for a variety of reasons so really want to remain on the Wonder Box. It’s just a shame that some basic game features are only available via third party software. Another minor source of frustration is the lack of mappings to standard key binds in many cases. The altitude pre-selection in the Starship being a good example. Similarly in the JF146, there is no way for Xbox users to map the “arm altitude” button to a keyboard/controller button. Regards.

I believe C208 is next on agenda along with the commander 114 and aero commander 685... I do know Nick plans to bring over all the steam gauge overhaul aircraft so the king air will come eventually. Hopefully it's not too far out. You can port the analog king air into msfs2024, I believe you have to disable the king air in msfs2024, copy the asobo msfs2020 king air and black square king air folders into msfs2024 community folder and it should load up and work with only minor lighting issues (that is the light's are abnormally bright).

@Black-Square Yeah everything is completely fine now. I just wanted to ask, even though it’s a bit of a different topic and I don’t want to create a new thread for it—I noticed that the aircraft is already a bit dirty by default, which is nice, but does it no longer get visually dirtier along the way?

Sound update - the quality of the sound of the Baron is MUCH better than the Duke IMO (piston duke). So good on the Baron that I taxi with the pilots window open to hear it better :).

I think that's exactly right. IIRC I got those SIMCONNECT Vars from within Developer Mode (Tools -> Behaviors) I think they are correct, since assigning button presses to them results the breaker tripping/resetting in the virtual cockpit. But in SPAD Data Monitor 'CIRCUIT CONNECTION ON:40' isn't changing state. Same for 41,42,43,44,45. I'll look at Dev Mode to see whether the Vars are changing state there.

@AlphaEcho You're more than welcome to join the server anyway. You don't have to be an RJ maniac. The topics will stay focused on the 146/RJ though.

@Black-Square if only Microsoft allowed freeware on the marketplace...

@neinnunb great. Thank you for the answer. Maybe I will buy it and give it a try

+1 - really hope the team can seriously consider / explore the 650s as a post-release update.

I'm not able to replicate that behaviour on my side with the latest version of the 146 and GSX, so it'll definitely be worth creating a ticket with Just Flight Support. In the ticket, if you could provide the information that you have in this thread, plus the video that you have recorded, then that will put our support team in the best position to attempt to replicate that, and log it for further investigation if required. Mark - Just Flight

From our internal testing of the post-SU4 updates, we reliably see the correct state recalled on the first flight of a session, and then it becomes inconsistent on subsequent flights in the same session. Mark - Just Flight

Sorry, I didn't give much thought to the term "optional". Your explanation is clear. Thank you.

Ok, clear. Thank you

That workaround seems to work for me. Thank you for the suggestion.