Makes sense, thanks for the answer.

@fizzboy Just for the record, the GTN 650 from PMS50 and TDS can be used to drive the autopilot from the secondary position, just not the GNS 430. I've asked Working Title if they were willing to supply this functionality, and actually spent a large amount of my own time trying to implement it as a proof-of-concept, but the code involved was above my paygrade, unfortunately.

@Black-Square Have you had a chance to take a look at the recently implemented changes to the turbine engine simulation in SU6? From what I've read so far from other devs it sounds promising: [image: 4bdfd7b9-8af0-41a6-b6ec-ce65171ff19e.png]

I’ve just emptied my community folder, the EFB is back to action ! Thanks for your help ! What kind of mod is usually conflicting with the Starship ?

I've heard a few complaints about this recently in many aircraft, including default ones. I think Asobo messed up some interaction code in their last update. Since I believe this is squarely on their side of things, I haven't gone looking for a solution yet, as these things often clear up quickly once they are reported. Since you say it's supposedly your mistake, would you mind sharing what that mistake supposedly is? Perhaps I can confirm whether that's the intended behavior. Here is the relevant FAQ from the manual: Why is the autopilot behaving strangely with hardware inputs? In order to implement altitude & VS preselect and more advanced features in the easiest way for cockpit builders to access, external hardware must use the HTML events described in the “Instrument Events” section of this manual and NOT the native autopilot events. Let me know if there is anything else I can do for you!

Did this ever get fixed or are there plans to fix it to allow for Lock interaction? I'd hate to have to go back to Legacy for exactly one airplane that requires it.

That makes sense, thanks for your quick response.

@daifuco Many thanks for the kind words and appreciation! Even with being partially deaf it’s amazing to hear how it has changed your experience for the better.

Had the same today. After disconnecting the EXT Power, it still remains available.

So, back to the topic? Next week release? Here’s hoping.

i recently got a new PC (AMD 9950X3d2, 64GB DDR5-6400 RAM, RTX 5090) and on this new system i also have these very subtle periodic microstutters every second like before. fresh system, no other software except for windows and flight sim. it's very subtle so maybe a lot of people don't notice it and it varies in intensity. sometimes it's gone, then it comes back. basically i just use MSFS 2024 ultra settings. nothing changed from these settings. and like before, only with black square aircraft (in this case i only tested the TBM unlike last time)

@FHamo Have you supplied power to the avionics buses?

[image: 74cdb550-1cfa-4cd6-9b7e-a72b85112a12.png] Thanks for responding both. Here's my cockpit setup. I think I've traced it to my hardware though - the issue only happens when I use the AP panel on my Honeycomb Bravo, and doesn't happen if I use the mouse to control the altitude selector. I use the same controls in all my BS aircraft though and this is the only one it happens in. Any ideas?

Can't speak to KSZP specifically, but the vast majority of my scenery library are 2020 products that haven't yet been updated for 2024 and they work just fine in it. Asobo's claims of backwards compatibility were overstated for complex things like aircraft, but I haven't seen many issues reported for scenery.