Bonanza Professional

@Derek It's honestly pathetic how (I won't name names) certain people at Asobo can look us in the eye and tell us "it's up to the developer" when it comes to hold-ups, releases and updates getting out. It's even more so when you provide screenshots from this very thread on the MSFS forums about this issue, they get deleted and you get banned with a "that's not happening" despite multitudes of other developers having the same issue.

Thank you for this post, I keep forgetting to come here and ask about this. It sticks out to me every time I fly the A36.

I got update 0.1.1a - taxi lights were working, but now I can’t get the Nav lights to work in the TP . Hope there is a complete update soon. Contrail didn’t even has more than V 0.1.1

The longer Barons wing is not approved for the tip tank etc, found this out while researching climb rates of the turbo normalized bonanza

@FrecciaKing Just to be clear, it's not in "reverse" with the power lever at idle. It's at ground idle. In flight, the power lever will be locked out of the beta range unless you have the "unrestricted beta range" option enabled on the tablet's options page. There are three ranges: The normal (flight) range down to "flight idle". The beta (ground) range down to "ground idle". The reverse range. I don't have any specific FSUIPC scripts to achieve what you're looking for (everyone wants something slightly different), but I know there are a lot of FSUIPC scripting experts on the forum. Hopefully one of them will see this post and provide the help where I lack expertise!

@Black-Square Is the three-press functionality correct, as opposed to the two-press?

And of course, thank you thank you thank you to Nick at Black Square. Hands down my favorite product for Msfs!!!

No rush intend. Enjoy family.

Hi Bucky! I'm glad you're enjoying the Bonanza enough to want even more Bonanza! I've had a few people ask me about the V35. Unfortunately, the redesign between the V35 and the A36 was so significant that it would be like developing a whole new airplane from the ground up for me. Usually I say something like, "that doesn't mean it won't happen eventually", but in this case, I think the majority of the community would rather see me work on more unique aircraft compared to the rest of my current fleet. Just a guess, though! Maybe they will tell me differently below. Let me know if there's anything I can do for you in the meantime

It may have been because I also had the analog version installed. I have removed it and things work much better.

The KLN-90B is v2.04 (Aug 20). The TDS GTNxi is up-to-date. (Recent update) I didn’t have PMS50 GTN, so downloaded the latest and installed. The PMS50 GTN doesn’t light up heading, nav or approach either. KX 155B did light up the autopilot modes. The GNS 530 and PMS50 GTN are failing to light up but the autopilot is functioning. Thanks. The KLN-90B is the v2.04

@Black-Square, no, I have a Bravo but all buttons are unmapped because all buttons and switches are managed by Stream Deck. I've double checked it anyway.

You can find almost all of the hardware inputs in the "Hardware Inputs & Outputs" section of the manual. For the autopilot, you will find the standard native bindings under the "Instrument Events" heading: K:AP_PANEL_HEADING_HOLD K:AP_NAV1_HOLD K:AP_APR_HOLD K:AP_BC_HOLD K:AP_ALT_HOLD

That's it. Thank you so much!

I'll try some of the others. I'm using the pms50 gtn750

Ok thanks i'll Look

@Outermarker and @hangar_101 Thanks chaps for your wisdom regarding the Asobo tablet - I wasn't aware it could was integrated as a 3D device. Having it and the Black Square tablet combined in the cockpit is sounding like a great idea