Just wondering if this is on the radar at all? Thanks!

I figured it out looking at your code. To get to the analog altimeter settings it's K:KOHLSMAN_INC and K:KOHLSMAN_DEC parameter 3 - parameter 1 is the pilot side display, 2 is the copilot display. You translated ALT_BaroAdjust_*_1 and _2 but nothing for the 3rd one. But this works.

also would love to have the ability for the 2nd GPS to be a GTN 650 like you have in the baron, bonanza and duke.

All ok now, the livery conversion worked.

@Black-Square I was able to reproduce the issue on my end as well. FL200 Max Range Power set by FF, torque is too high [image: 55c410dc-0cc6-42d6-b68d-dca6a471e265.png] Max Range Power set by Torque, FF is too low [image: c09d82dd-39de-4616-a1db-9264c16913ad.png] FL240 Max Range Power set by FF [image: 4da3ae34-6927-4382-8093-7fe04920efe1.png] The trend continues. I didnt grab an image of the set by torque at FL240 as I had a GFI outlet I had to replace. Thanks, Crash

@Black-Square we are taking care of that for your new products Nick. Still very much a work-in-progress, so far from finished. The panels are coming for both the Bonanza / Baron Pro in pilot and co-pilot view. AVNX Baron Pro Keep up the great work! The planes fly great and are much fun to fly around with. [image: preview_baron.jpg?ex=6a31f2d1&is=6a30a151&hm=f9bd001f2caece5ad2835a04df26cfd960cbfd3f2ce61a2f7c7555d9950c29f0&=&format=webp&width=2898&height=1630] Best regards, Pete

Just want to chime in and say I have this exact same issue with the speed gauge. I also notice it on both the kFC-150 (the red screen text, not the buttons) and the autopilot annunciator panel. Now here’s the weird thing - two days ago this happened no matter what I did. Then yesterday, everything was clear. No changes to settings, anything else. I’ve also had this on the A2A Aerostar, so my guess it’s an Asobo bug and not aircraft. It happens to only certain instruments or text, but not others. There must be something common with these gauges or text that makes them blurry. If you look away momentarily and then back the gauges become clear for a few seconds, then go blurry again.

My $.02, I'd happily pay an upgrade fee for a 2024 native TBM with custom sounds, etc. An avionics retrofit would be awesome as well, something I think BKSQ has floated previously. A cup of coffee, if you will

@Black-Square that's good to know that it's not expected behavior. I don't think so, but I'll check next time I'm in the game, and I'll report back with a more detailed explanation of what happened when

I believe this ITT change is incorrect in this checklist. The official POH checklist indicates otherwise — it actually calls for a slight torque drop instead. That torque drop can indeed be verified during the procedure. See official POH below [image: cb6b1c51-6beb-49d8-9a1d-15b1bd0145d5.png]

Thank you! That all makes sense - the reason I think it's worth addressing in a future update is mainly because as implemented, a gyro failure would have a disproportionate effect because there isn't a back up

@Black-Square Yes this worked. It is the AI Auto-Trim. Thanks so much

Yep, I was right - descend doesn't work from the copilot side autopilot panel either. Works fine from the pilots side - too bad I can't tune the pilots side to a VOR. I think I'll be hand flying the end of this looking at the other side. What I was expecting was if the AHRS and CDU x sides were on that the two main displays would basically display the exact same as the copilots - wrong expectation? Also noticed that ATC 1/2 doesn't seem to work - transponder stays on the pilot side.