@jmarkows All aircraft except the Analog Series and the Velocity have this code. That's what allows me to do the gyroscope physics simulations that you may have seen in my YouTube videos.

@eracer1111 said in I'm confused about some of the BKSQ variables.: I own 13 Black Square aircraft I'm glad someone is keeping count Thanks again, and let me know if there is ever anything else I can do for you!

Controller profiles are something that is handled entirely by the simulator, and we don't have any influence over. MSFS 2024 allows you to have separate control schemes for each aircraft, which may cause the difference in controller profiles you're seeing. I believe there is also an option to "Apply to all aircraft" when creating a controller profile, which will apply the same profile to all aircraft, like how MSFS 2020 handles it. Mark - Just Flight

Thank you for the kind words. For future reference, you may be interested to know that there are tools within MSFS Developer Mode that can help you find LVARs for any control in any aircraft. With Developer Mode enabled, if you move your mouse to the menu bar at the top of the screen, and navigate to: Windows > Behaviours > Local Variables. Entering instrument names or abbreviations into the ‘Filter’ field will vastly speed up the process of finding LVARs. For example, if you are trying to find the LVARs used for the transponder, you can search for ‘XPDR' and you will find the following LVARs: "PED_AFT_XPDR_MODE". With the Behaviour debug menu open, it is also possible to automatically populate the "Filter" field with the LVAR name of a specific control. With the Behaviour debug menu open, move your cursor over any control in the cockpit and then press [CTRL]+[G], to populate the "Filter" field with the LVAR name. Hope that can be of some use. Mark - Just Flight

If anybody is wondering. The problem went away when switching from TAA to DLSS (both the old and the new version). Not sure if I will stay with DLSS, but for now that's what I'm using either way, so it's fine.

Enroute to Eagle CO with a setting sun. There just is no bad angle to take a pic of the Starship. [image: 9c8aed1c-3a42-4a13-9da6-4952e7a7bc8f.jpg] [image: 31496acf-8423-41d8-b33f-1d9fc9640bc1.jpg] [image: af4c6d16-f5de-4d08-b6be-50c80a64c826.jpg] [image: 60834b36-8759-45e4-b760-d0d77e16a2ed.jpg] [image: 8db7bc74-80a6-4a65-8d6b-7e2082571e2f.jpg] [image: afbb3a97-fbe1-44bf-9b10-ba1e28dd0605.jpg] [image: 6281c7b0-61b9-401e-bef2-04caf1c97092.jpg] [image: 0c447610-1afb-4b04-bf96-9a1e34e0afa3.jpg]

Cruise climb it is ;). Another quick question - what's up with Vr in the Turbine Duke (102)? The other airspeeds are relatively close to the piston Duke. The only thing I could think of it being able to counteract the torque in an engine failure needing the higher airspeed but it's even higher than Vmc. Tried finding a POH or info for the conversion but couldn't find anything out there (outside of your manual).

@Mark It was well within crosswind limits. I don't have tiller hardware. But there was no dead zone, so I'll try adding that to see it it helps.

Thank you, @gazdav787 , you've given me the clue I needed! Besides those variables, I've identified these ones: The buttons can be toggled using R_TRP_Climb, R_TRP_MCT, R_TRP_TOGA and R_Mstr_Climb. Send a 1 to those values and button will change state if it's possible. State of the buttons can be read using R_TRP_TOGA_redu_il1, R_TRP_TOGA_redu_il2, R_TRP_TOGA_redu_il1, R_TRP_Mstr_eng1_il1, R_TRP_Mstr_eng2_il1, R_TRP_MCT_il1, R_TRP_Climb_norm_il1 and R_TRP_Climb_max_il1. Each variable maps to a different state. Value of the display can be read using JF_RJ_TRP_Display_Value. Thanks!

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.

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

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

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