The final Bonanza/Baron Pro in-flight picture, for anyone interested. [image: 85f9cb1c-a644-4a0b-8713-ac25978ad567.jpg] With the Caravan Pro work-in-progress. [image: 9d376bd7-5964-4a00-ab17-d19a4c4ef7d0.jpg]

Ron, Did we have a conversation about this when the Bonanza released? Here are the magneto increase/decrease events I put together for FSUIPC for the Bonanza; I looked and the Commander Lvar looks to be the same. I remember testing these with the Bonanza, and I don't see why they shouldn't work with the Commander, however I have a button box with a key switch that I have bound to the individual positions, so I don't actively use this. BT36_Magneto_Increase#(L:BKSQ_IgnitionPosition_1, number) ++ 4 == if{ 5 (>L:BKSQ_IgnitionPosition_1, number) } els{ (L:BKSQ_IgnitionPosition_1, number) ++ 5 min (>L:BKSQ_IgnitionPosition_1, number) } BT36_Magneto_Decrease#(L:BKSQ_IgnitionPosition_1, number) -- 0 max (>L:BKSQ_IgnitionPosition_1, number) Calling Magneto_Increase should increment the L:BKSQ_IgnitionPosition_1 LVar by 1 and max out at 5 (start), and Magneto_Decrease should decrement it by 1 to a minimum of 0. Drop the two of them into myevents.txt and reload your presets, you should be able to bind them to something and give them a whirl.

Are you sure you aren't mixing priming and starting?

When and where can I give you my money? This looks amazing! Maybe A2A could add it to there upcoming Legacy?

@Black-Square said in Just Massively Impressed: Thanks for letting me know! I often wonder how many of my users are out there flying my older planes, versus how much of this tends to be "fad" driven. I'm the kind of person who would pick a couple of my favorite airplanes and fly them forever, so it's harder for me to imagine how some users fly something new every couple of months or even weeks! The Analog King Air was my first purchase and the only reason I still have MSFS 2020 installed on my computer. I have all your other aircraft, but I always come back to the King Air. Really looking forward to the Model 300 in MSFS 2024!!!

@JabbyJabara Cabine secure and ready for takeoff are 2 different things. Working for the biggest airline in the world here. Cabine secure is when all passengers are properly seated with seatbelts and all overhead bin closed, all alleys free, etc... That's done before pushback, it's linked to parking brake, we release parking brake only when cabin is secure. Then the FAs do their safety briefing, check the cabin/passengers one last time and then take their seat, all of that is done while pushing back and taxiing. When getting close to takeoff (usually about being number 3 for takeoff), we make a last call for FAs to be seated for takeoff, then they reply by calling us and saying "ready for takeoff". So, it's 2 different things really. With the JF Fokker 100, I think they made a mix of both, which I think, should be corrected/improved. Just my 2 cents...

Thanks for your reply. the problem was i juste re-use the gtn750 from my new cessna caravan since months. with over gtn750 all worked fine, but for the cessna none. it was simply my map oriented north instead of heading. i was a bit confused. It was just nothing... Sorry, thanks again.

@George-Curious Interesting that the Default Asobo King Air does this. I'm away-from-sim for a few days, but I might try to repro that. If I'm able to, I'll tag the moderators on my original bug post in the FS2024 forums. I also might try to whip up a quick .NET app that monitors some of the NAV/VOR SimConnect variables and see if there's anything interesting going on. My hypothesis is that the VOR signal is intermittently dropping for a short period of time (seconds? milliseconds?), and since the autopilot can't receive it, it reverts to ROL or some other default mode. Perhaps some autopilots have a longer polling interval for receiving the signal than others, and are more resilient to signal drops. Since BKSQ likely uses common code for most/all planes, it might explain why I'm able to repro this behavior on all of them. All wild guesses, but it sort of makes sense as I think about this.

Can’t get mixture lever working since new update dropped, using AxisAndOhs. I’ve read this back but unclear if I’m supposed to be using a new binding. AXIS_MIXTURE1_SET always used to work

@fabristunt Fixed - sorry about that

@Voxen I had the same issue and followed your advise. But unless that, I was not able to install it into the community folder due to long file names, so I installed it in the default install adres of justflight (C:Justflight) and that worked. Thanks !

Thank you for sharing Since I always like to say that "I never get to fly my airplanes unless they are unfinished or broken", I derive most of my enjoyment of them from hearing that you've enjoyed them

@SkipperMacz In case you are interested, I have completed the project based on v1.1a. I have also updated the accompanying document. Check out the link: https://drive.google.com/drive/folders/1bt0euYHjSdla7srvA_8fSl4J8yQjiLlk?usp=sharing I added in all the axes and reconfigured a few things. There is now no need to have anything configured in FS2024 itself.

@MiRexer Well, that's the same technique I used when creating Turbine Duke panels . But I still think the results are preety nice

Glad I could help. Good luck!

I would love to see the ProLine 21 avionics but it feels a bit counter to the Black Square ethos… I hope I’m proven wrong!