@sbanks75 I've got the same issue. Even after the update I still need to use the turbo mixture assignment for the normally aspirated version. Perhaps the update didn't install properly.

Hi Mark, thank you for the reply. Sure i'll. Alberto

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]

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

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.

@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

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

Again a few minutes ago, huge storm over Geneva with many lightnings and not a single dot in the vectorscope. I eventually got some random dots when I switched the gear out.

@Mark fair enough, appreciate the thorough response

@Mad_X i am sorry, my english is very bad, i am not from the US. i dont understand what you mean, sorry

@venemair thanks for your reply . My experience echoes your own as flew back to EGNX from EIDW last night and no such issues. I was keeping a much closer eye on the amber band on the speed tape and the ATS handled things fairly well, all be it with a bit of hunting when heading downwind, but it did a reasonable job of maintaining the speed. Wind on finals was realistic and did a pretty smooth landing, so inconsistent, but will keep persevering!

@Black-Square I am also experiencing some strange behaviour. I am not sure if this started after 1.1 or was there with 1.0. The "VR Tablet Static Position" option in the tablet is always resetting back to an "On" state for every flight. I turn if off and at the start of the next flight, it is back on again. This is happening for the TC variant only. I am able to toggle it off on the normal variant and it stays off.

In the engines.cfg documentation for the SDK, it says that the default airspeed minimum for the Hobbes elapsed time is 25 knots. So given that, you should have less time on the Hobbs meter than the tach time.