Bonanza Professional

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

Yes, that's correct. I must have eliminated that variable during development. You can use the B:Var, K:TOGGLE_PROPELLER_DEICE, A:PROP DEICE SWITCH:1, or set the circuit directly with A:CIRCUIT SWITCH ON:30.

Has the update already been released? I own the Bonanza Professional. It’s amazing. But unfortunately, my progress is not being saved. If I enter the game, refuel to full tanks, end the flight and close the game, then start the game again, the fuel tanks are only half full. The throttle levers are also in a different position. Could this be affected by whether the aircraft is streamed or installed locally?

I have my fingers and toes crossed for this. I honestly believe I wouldnt fly anything else if we had G3X in the Bonanza and Barons.

Yes it will, we're waiting for it to happen too, really should be this week.

If your using the PMS GTN 750 I believe you can disable those messages - system->setup->options->messaging system.

@Black-Square I know the issue now. it is causing by the falcon71-kln90b. now I updated to the latest version and the tablet is working again

My great uncle flew around the world with Bob Reiss in N9675R, a converted A36 Bonanza with an Allison B17. In the 1994 trip they had an engineering firm plan out and engineer 100 gallon tip tanks (670lbs). After installation it was clear that even though in flight the bending moments margin would be adequate (although reduced), the taxiing was the largest issue with higher accelerations in the Z+ and Z- directions resulting in a limitations that only 55 gallons could be carried. So the stock bonanza can, if begrudgingly, carry 55 gallons on the tips. In his recollections of the time, he stated that it was common in the more remote areas to take off about 50% over MGW when fully loaded with fuel compared to a stock Bonanza. He would say that it flew, it just had to get going much faster to do it.

@Buzz Very cool, thanks for the find

If it's always returning to this value, I suspect this is related to the broken state saving with SU4 that you may have seen others complaining about. Unfortunately, there isn't anything I can do about this, except pressure Asobo to look into this issue for SU5. In the meantime, there is currently a discussion on the official forums about a workaround with how you exit the simulator. That might be worth a try. Also, have you tried editing the state.cfg? I think others have had luck setting any values in there as they like.

Already discussed here