Any hope for this at all?

@Petzep This is an excellent explanation of MTBF, and I have now pointed several other commenters in this direction to read it. Thank you for taking the time to write it

Although I'm always interested in more persistance and aircraft ownership features, it's really the inconsistency of Asobo's state saving that's holding me back. I don't want to create all these ownership features, just for some users to find their progress erased on some random load of their simulator. That would be more frustrating than not having the features, in my opinion! In the meantime, this conversation might interest you. It's all about how to think about MTBF, and how it differs from other damage models.

thank you to both of you. i would prefer to have control over the beta for better taxing. i give up some throttle range for that. bp_spets i will your setup thanks a lot!!

Came here to also post an observation but this seems related so I'll post here too. I use a Streamdeck to monitor trim values, which saves mousing down to look all the time. I use (A:ELEVATOR TRIM POSITION,DEGREES) I have noticed the following on the Bonanza TC The plane loads in with my Streamdeck showing 0 degrees elevator trim If I enable Settings > Flight Interface > Instrument Tooltips - that also confirms 0.0 degrees On the aircrafts trim markers, its showing around -1.5 degrees (the first D below 0) Moving the trim to 0 on the aircraft trim marker is showing me +2.1 degrees from the sim I can see the plane marker ranges from -15 to +15 ish and the sim is -20 to +20 degrees, so I would not expect the numbers to be perfectly align. However the fact that 0 is not 0 did throw me off. If I bind a button to "0 (>A:ELEVATOR TRIM POSITION, NUMBER)" it will reset as above - sim showing 0, trim marker at -1.5. So this would explain why when the OP sets their trim to 0 is getting a +2 degree climb Maybe this is how the aircraft really is??

I bet your moving your mouse up and down - try moving it left and right while holding the left mouse button. I'm able to scroll quickly both directions. Same thing for the cowl flaps - took me a while to figure that out.

After some research I finally got the mixture lever for the A36TC to work with axis and Oh's by using IE:BKSQ_TURBOCHARGEDMIXTURECONTROLLER with axis min 0 and max 1 float rounding. I suppose this would work for spad.next as well.

From what I can see on reference photos, the 146 and RJ should both share the same centre pillar design on the windshield, and that is reflected in our 146 and RJ products. I can see there is a slight taper on both real aircraft, so I've logged that on our internal trackers as something to possibly look into adding in the future. We intentionally added the current type of weather radar to the RJ, as that was the only weather radar we had available to us at the time of release. We do have a feature request logged on our internal tracker to model an additional type of weather radar, but nothing is planned at the moment. Mark - Just Flight

Dang! Thanks, working now! I just overlooked this option and only saw the checkbox above this one. I made an update of the TDS between flying the Bonanaza and the Baron, maybe this reset it.

Do you think that in the future, the consumption of motor oil and its replacement will be feasible?

Thanks, I was curious if your useable fuel figures were simply just a number. Silly me...

I absolutely agree! The customer support is top notch. I'd say, the best I experienced in 20 years of simming.

@Black-Square Excellent, thanks!

Thank you, I’ll dive into the Spad community

@Ape42 That's some fairly impressive RPN. Would you like a career with Black Square Simulations? Thank you for providing that for my users! I didn't know that automated scripts were possible with SPAD. That's very good to know, and seems like an optimal solution for this particular question.

You might be able to reliably retrieve that data from... C:\Users\[USERNAME]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\bksq-aircraft-bonanzapro[variant]\state.CFG (slightly different path for MSFS 2020)

So I retried and managed to get it working. The only thing i did different is to select loc1 on the hsi instead of vloc on the GPS cdi. Maybe that's the clue?