Bonanza Professional

Thank you so much

Normally, I would offer you a custom code solution to extract that state from my software as an L:Var, but the GTX 327 is the only piece of default avionics still in use in my aircraft. I've been meaning to create my own version for ages now, but I know it's also low on the priority list for most of my users. You can still make an edit to the default simulator's files to get what you want, but be prepared for it to reset every time the simulator updates. You can also make a package with an improved GTX 327 to keep in your community folder. I would be happy to give you some pointers on that, if you need any.

Any possible update on this? Am I wrong for having my hopes up that we will have G3X in the Bonanza and Baron at some point?

I love this attention to detail! I just started flying the B36T after spending a lot of time in the Baron and noticed the fuel discrepancy and thought it was a bug too LOL.

Thanks for sharing your thoughts. As usual, I have considered almost all of these at one point or another. The variable flow rate, in particular, I have come really close to implementing in some of my aircraft. The donning and doffing, you will see implemented in my Starship, King Air, and TBM by pressing the tabs on the mask to inflate the quick donning function. As for the "effects", I really wish there was a good way to do this in MSFS, but I have yet to see an addon come up with a clever solution. The only options I've considered are very ham-fisted, and I wouldn't feel confident about their reception. I will keep looking for clever solutions, but for the time being, I would say that variable flow rate is the most likely of these that you might see from me. Thanks for sharing! I hope my message doesn't sound like a dismissal of any kind. The only way I know what features will be most enjoyed by the community is when you share them with me, so I am always happy to hear from you!

I'd absolutely buy the Doctor Killer!

@Black-Square So there is some hope that it will happen someday. Oh God, that would be amazing.

@fenthanyl I know the feeling. I'm also one to try solve my own problems before asking for help, probably to a fault. I'm just glad it's working now and you're able to enjoy this unique method of navigation. As always, let me know if there is anything else I can do for you!

Yeah, I looked a lot closer at this, and I have now decided that I just couldn't see the instrument lights, and it's not a bug. I can see the instruments well enough, but was expecting a bit more illumination if I turned on the lights. All good.

@Iconography Didn't know that was a work around, thank you!

@Black-Square Thank you for the clear and honest explanation — that makes perfect sense now. I understand the limitation of MSFS using a single, rather crude crash detection system for multiple failure cases, and why this forces a compromise. While it’s not entirely satisfying from a realism standpoint, I appreciate the transparency and the fact that this is a platform limitation rather than a design choice. Thanks again for taking the time to explain it in detail.

@ThargorV8 @Black-Square With Vatsim and SI, GNA 340 works perfectly, just make sure you have the VATSIM "Monitor all" option on in the tablet options (I forget the exact name of the setting...). One thing I do want to mention is that I've noticed many addon liveries seen to cause the aircraft light's to appear brighter and a few other graphic anomalies despite them saying they are compatible with msfs2024. Frustrating, but I've been happy with the default liveries in the meantime.

simple answer, just use tds, its tremendously better than pms. 🫠

@lilycrose Thanks, good to know! I’ll dig into it a bit more on my end and see what I find. Really appreciate your help!

Thank you very much

@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?

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.

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