@jmarkows Yes, there was also a stealth update to the priming workflow, even if it was not specifically discussed in this topic. Now it agrees with the one from the POH/other Lycoming planes, and was also changed by Nick in the checklists. He probably just omitted the same part in the descriptive section by mistake.

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.

@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

Glad I could help. Good luck!

@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

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

I bought BATC and I can confirm it works great, it avoids the native ATC bug and does better traffic injection than other tools.

Interesting. I didn't change anything either. I'll work on it on my side then to see what I can find. Thanks for the quick confirmation.

got it - button needed to be pulse/momentary....thanks

@Rich said in Commander Update v0.1.1: @Fabbi It's down to how long the paths get inside the package folder. In the case of the Commander, this html path often pushes users over the limit: bksq-aircraft-commander114\html_ui\Pages\VCockpit\Instruments\Generic\Misc\bksq-aircraft-commander114\BlackSquareTablet\Shared\Assets\commander114ElectricalVisualizer.svg If you add the path to your Community folder to that, in my case it becomes 271 characters long and Windows won't allow it, even with 64bit versions of the installation software. Other aircraft have shorter names and more people fall under the path size limit. As this is one of the longest we've had, more people are seeing it. For the Commander, I've expanded the default installation option in the installer to pre-check whether the package will fit inside the path limit, and if it won't it will send you to the custom location option that will get you around this limit. Hope that helps explain what's going on. Thank you so much for this information.