Piston & Turbine Dukes

I have bound a toggle switch to it. Need to be done externally unfortunately. (L:bksq_TabletVisible, bool) ! if($=1,0,1) (>L:bksq_TabletVisible, bool) If you use Mobiflight for it (free), I just added it as a preset you can find under the name "BS Duke Toggle Tablet".

Sharing my experience. Below is my post in the PMS50 discord un Jun 29, 2025: Repeatable MSFS2020 CTD when PMS GTN750/650 is used. A/C is BlackSquare Duke. I've been testing this all morning, and can consistently and repeatably cause a CTD at the exact same position only when using the GTN750/650. I have NOTHING in my community folder other than the Blacksquare Duke and the PMS50 GTN750. When I try the exact route with the default DA62, no issues. When I try the exact route with the Blacksquare Duke and GNS530/430, no issues. When I try the exact route with the Blacksquare Duke and PMS50 GTN750, I get a CTD. I did this 4x times, and the CTD repeats consistently. I downloaded and installed the latest version 2.2.48 of the GTN750. Still CTD. If I don't use the GTN750, it does not CTD. I've read many post stating that PMS50 GTN750 cannot cause a CTD. I don't know what to say, but that's not my experience. Here's the flight plan. Cruise altitude is 13,000. Departure time about 10am local. KBTV DCT OMPEE DCT SQUAM DCT LIMER DCT KPWM The CTD occurs about halfway between OMPEE and SQUAM. Update: I still had version 2.2.36 on my PC. I had flown ~60 hrs with this version in the BlackSquare Duke without a single CTD, so I reverted to 2.2.36, and tried the problem flight plan. No CTD. So, I'm back to using 2.2.36 indefinitely. That's fine with me. Also, during my testing I had absolutely nothing else running at all, and it still CTDed. I didn't have any third party apps running.

Thanks for the replies! Totally forgot to mention: I was talking about the Turbine Duke!

@Hawkeye I am on 2020.

For some reason this has also been the item I missed most often on the checklists. For evening flights, I made it a habit to keep the overhead dome light on as a reminder, until I have switched back to normal (also lights up the handles a bit extra).

Missed this update. Looking forward to them.

I did a reinstall of the Turbine Duke and now zoom works fine.

That's what I'm here for! It wouldn't be any fun for me if I didn't get to see my users learning and becoming better virtual pilots

Incredible the amount of detail you put into these aircraft, Nick. They never cease to amaze.

Integration with navigraph charts would be incredible in the EFB, or having the possibility to use the new MSFS2024 EFB in the 3D cockpit.

Using both seems redundant. As far as my case goes, I added _IsDown to my up and down events, and they work swimmingly. I've no idea why the difference; maybe the regular ones work better with the Rotorbreak command I see so often in flight sim peripheral channels. Supposed to imitate a mouse click I believe, but I've never used it.

Here is a fix, upgrading the GNS530 to the 2024 version: https://www.avsim.com/forums/topic/673298-how-to-import-a-flightplan-in-msfs2024/#findComment-5494400

Nick, I'm sure that you've been heads-down on the Starship for a good while now, but I was reminded of this issue yesterday when I pulled into the ramp at Nashville yesterday. I selected external power and went to play with the avionics after I shut everything down, and found myself eating through the battery instead of being connected to the power cart. Fortunately, it gave me an opportunity to play around with hot starts and vapor lock (and watch it all on the tablet as I went through the hot start checklist!), and I could always just click "recharge battery," but having the power cart would still be nice. Have you had a chance to look at this for the next round of aircraft updates?

No need to apologize, I’m sure you are very busy these days, with the upcoming release of the Starship (looking forward to it!). I suspected it was something like the situation you describe, that caused this. It was obviously not a problem, but I can also understand why someone with your attention to detail wanted to fix this. And somehow found the time to do so. Do you ever sleep? All the best!

Ok, thanks for clarifying

Here's a little sneak peek. I got the dynamic reg numbers hidden with the method you suggested - although MSFS 2024 still tries to put a tail reg on the aircraft unless I go into the in-game "Identification" menu and remove the reg number. Although this might look like a fictitious paint it's actually real - although there only seems to be one reference photo and apparently the aircraft has since been repainted! [image: b4tRohu.jpeg] [image: K1Dm109.jpeg]

@SebAvi Yep that's the current plan.

That's exactly correct. The yellow band would allow you to fly the aircraft faster in smooth air, but in a turboprop aircraft, there is no such band, meaning that VNO and VNE are the same speed. Unfortunately, I have been unable to locate the logic behind this regulatory decision, but there are several accident reports of structural failure in turboprop conversions flown beyond VNO in turbulent conditions.