Just had a look at the wheel debug, it looks like the velocity angle is constantly changing from anywhere around 180 to -180. Not sure if this has any relevance however.

Oh OK, thanks. Would be much better if you could assign unique registrations to each livery (as you say, the UI definitely gives this impression). Odd, because before you change the number to one of your choice, all the original reg numbers are different livery to livery (from memory). Cheers.

Hi Villajota, It's possible .... I use my own C# program to set the values (using LVars and SimConnect) - never used hardware, so this morning I tried to see if I could roughly do the same using SPAD.neXt (I don't have AAO) and my WinCtrl (WinWing) 777 FMC unit, and looks like it can be done, so hopefully the following may help you and set you in the right direction. The R_TRP_Knob_outer LVar turns the switch to N1 , TEMP , V1 , V_CROSS and V_DOT positions. Values are 0 -> 4. In SPAD.neXt, I set an event so that when the "Prev Page" button is pressed it decreases the value of R_TRP_Knob_outer by one and likewise for the "Next Page" button event, each press increases the value of R_TRP_Knob_outer by one. (Spad.Next allows me to set min/max values for these events so that I can ensure that the values can't go below 0 or above 4). Next step was to set up two different buttons to change the values of the TRP display using the R_TRP_Knob_inner_dec and R_TRP_Knob_inner_inc LVars. Using the . and +/- buttons on the WinCtrl FMC unit, the . button press event was set up so that for each press I write a value of 1 to the R_TRP_Knob_inner_dec Lvar and the +- button event set up so that a value of 1 is written to the R_TRP_Knob_inner_inc Lvar. This results in the value in the TRP decreasing for each press of the . button and increasing for each press of the +- button. The value that changes is governed by the position of the R_TRP_Knob_outer knob. Using the above method, I've been able to change the Temp and the V1 , V_CROSS and V_DOT values, using my FMC hardware unit.

Glad it's working well for you, and glad that my suggestions were over the target. Thanks for letting us know for anyone else who might search with a similar problem! A great weekend to you, as well

If you have everything configured correctly, the maximum climb or descent rate from the pressurization controller should be 2,000 ft/min. That can be quite uncomfortable for passengers, so most operators keep their rate knob at more like 800-1,200 fpm. As you point out, the aircraft will easily outpace this, but that's just one of the challenges of operating an aftermarket conversion like the Turbine Duke. Let me know if you have any more questions about this. I'm always happy to help.

I have found the same issue. Normally I need to restart the flight, sometimes more than once, to make the aircraft page appear. I've tried saving and not saving state and the result is the same.

@Tim-HH said in Dual GTN option: @Black-Square I fully agree with Ryan! A dual GTN 750 Xi would be perfect. It is also the most common GTN configuration in the TBM 850. [image: N885CA-Panel_1-scaled.jpg] I made a little Photoshop edit just to show you how awesome it would look in your TBM [image: TBM-Dual-GTN.jpg] This would absolutely be hands down amazing!! What would really be a cherry on top would be the headphone simulation like the pro bonanza and baron have once we get a proper sound set!

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

Thanks for the email guys now officially updated to 2024 ! Great upgrade don't know if you have the option but if poss could you drop the dev a thankyou for the free upgrade ? Cheers !

YEAH!!! That worked!!! Thanks so much, Mark!! And THANK you and your team for this amazing plane.

@AvApollo I've done that. I didn't try @firefox1 's suggestion. Although, the Ground Handling on the Starship seems vastly different, so I think the reinstall did fix most issues.

All right. Thanks

@ozilla Yes, absolutely!

@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

This is indeed good information. I had a careful look and the settings for Bonanza and Baron were indeed different. Although the autoslew function was checked, the OBS needed to be changed from GPS to VOR1. Good to know!!