Bonanza Professional

@Black-Square Thanks I have tried your suggestion, that is good for me

Thanks you all for your answers. So it is a mix of all you three! @jmarkows Yes, I forgot about the variables at the end of the great manual! so now I could set up my bravo as I wish! @Black-Square Yes, the process is similar to the Starship but the name of the variable in the starship contains the system number which make It easier even without the manual to find. Great airplane, great work ! @MiRexer Thanks for the clarification. with the variables in the manual I could solve it.

[image: d688593e-dfe1-41a6-b46b-80ba8f6b9d42.png] Side note PSA: With HDR off and setting light shafts to off does "fix" the ridiculous landing light bloom in msfs2024. with the downside of never having light shafts... I guess you can turn it back on in bad weather...

Perfect, that worked a treat. Thank you!! My Stream Deck+ now accurately shows the ARM state.

I think is something with the Sim itself, This happens also with the PA-28 and the SWS pc-12. Im moving the Heading Bug and suddenly right before arriving to the hdg i want it jumps straight like 40 more degrees. so I have slowly go back.. Same thing happens with the CRS Bug.

If by "bug" you mean a typo in the checklist, then yes. It's fixed now.

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

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

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