@toby23 It's a great plane! I don't fly it enough because I have a slight preference for the more manual 146.

@Black-Square Thanks

Thanks for response

@adomeitus +1. Same here. Noticed it twice so far. Taking it out of beta made the annunciator go out again.

@Derek could you please assist me sir, and remove the broken link image in my post above? I tried to edit it but I passed the time window for that. I placed the updated image on the permalink of the AVNX website itself. That way users don't end up at broken links or media. Appreciate your help. Pete

Hi Mark, curious when this next update will arrive for the RJ? Would love to see the external textures updated, textures aligned correctly and walkaround mode implemented. Appreciate that is a lot of work, would happily pay for an upgrade like this.

@maquinn78 said in Newb - Aircraft won't start: I am a totally idiot when it comes to this stuff. But I also just want to fly. I did one successful flight, then I started a second from the airport I was already at, engine died mid flight. I restarted the flight, turned off all failures because I don't want that. Can't get the engine to start. I just want to fly. I don't care about realism of gas and a turbo prop and all that right now. I just want to fly the $40 plane I bought. Please help, I know I'm a dumb newbie. Look, I get your eagerness to fly, but all BlackSquare aircraft are professional-grade. They're complex. It would be good of you to read some of the manuals. They're very instructive and will definitely help you get to grips with the basics of the systems. It might seem a bit intimidating for those without much experience (which seems to be your case) but with a little dedication, it all works out. Good luck!

@micstatic You may want to create a new post for that suggestion, and see what other people think about it!! I was only reporting some oddities here, but it could be nice addition to have more flexibility in avionics.

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.

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

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

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