Piston & Turbine Dukes

I almost thought this was a duplicate, because we just had a nearly identical post a day or two ago. Here was my response: "Every time I have seen a similar complaint, the cause has been destroyed engines (usually due to improper starting procedure). Check the engine health bars on the upper right of each engine visualizer page. If they are at 100%, then we can troubleshoot further. A video or screenshots might help at that stage." If that's not the problem, let me know and we will troubleshoot together.

Every time I have seen a similar complaint, the cause has been destroyed engines (usually due to improper starting procedure). Check the engine health bars on the upper right of each engine visualizer page. If they are at 100%, then we can troubleshoot further. A video or screenshots might help at that stage.

Fixed, luckily another user had the same problem and he posted this solution and it worked for me Create directory "Microsoft Flight Simulator" inside directory "C:\Users%USERNAME%|AppData|Roaming" Copy file "UserCfg.opt" from "C:\Users%USERNAME%\AppData\Local|Packages\Microsoft.Limitless_8 wekyb3d8bbwelLocalCache" into newly created directory above (1.) That's it - then you can run installer and after install you can remove

@Gilandred Well, it doesn't seem to have been the case. I made it very clear that I didn't want price protection, especially not a year later, but only that I wanted the option to pay the difference between the Piston and the Bundle at the official price. Nothing else. The rest is just something you made up.

Awesome. Thank you. I will look.

The KX-155's are not GPS units, therefore they represent the "No-GPS" option. There is currently no way to load a sequence of RNAV waypoints into the KNS-80 or KNS-81. I haven't looked into it, but I suspect this would not really be possible, given how the flight planning system works in MSFS, as the waypoints are not defined by radial/distance pairs. In theory, I could create a system that selects appropriate radial/distance pairs based on injected GPS waypoints, but I don't think this would satisfy most users who want to follow realistic RNAV procedures, or actual history charts, as much as possible. Let me know if you have any more questions!

I found a solution to make the installer from Just Flight work with MSFS 2024: Create a folder on your PC Called Microsoft Flight Simulator In the following location C:\users<YourName>\AppData\Roaming\Microsoft Flight Simulator Then copy from your 2024 folder the UserOpt.config into it. That’s all you need to do. Any installer e.g. Just flight will now work and install the planes into your 2024 folder and the DRM will work.

I encountered the same problem during multiple flights. When I start cold and dark on a parking spot fuel flow is showing 0.0 although everything is working fine. If I start on the runway with the engine running fuel flow is displayed without any issues. I investigated a little bit further and found that in cold and dark start the fuel flow is 0.0 when I move the condition levers each on its own with the mouse to start the engine. If I start both engines at the same time with both condition levers bound to my VKB STECS axis I normally use for leaning engine in single engine planes like the DA40 engine starts and fuel flow is showing with correct numbers throughout the rest of the flight. Unfortunately I don't have the option to use two separate axis for each condition lever and it feels a little bit unnatural to do a double turbine start at the same time in parallel.I hope this information helps you to fix this problem for MSFS2024 update. Anything I can do in the meantime to enjoy the turbine with fuel flow information in MSFS 2024 in a normal startup procedure? I love my Turbine Duke in MSFS 2024. Currently I am crossing the Atlantic from Wichita factory to my home field Nuremberg in a realistic transfer. Can't wait for an officialy supported version.

Glad you found the solution! Indeed, that addon has caused us a lot of headaches, but I haven't seen it come up in a while, so I didn't immediately think to recommend looking for it. Let me know if you have any more questions!

@Black-Square All sorted Nick. I dropped my wallet on SPAD and learned how to use it. Took a few days but the clues on these forums and some youtubes later - I have solved all my annoying issues with all of your products and some other 3rd party AC. Should have bought SPAD a long time ago I guess. The answer for this was to add LVAR:bksq_TabletVisible 0 or 1 to display and dismiss it.

@Mustang said in Dirty glass texture in cockpit (MSFS 2024, not Duke specific): love to master them vs jumping into different aircraft and pretending I know how to fly them! We are in the minority, but I always hope that my aircraft cater to the most dedicated masters of the virtual skies Thank you for your comments. Sorry that these small issues are there at all! There are still numerous things in 2024 that we have been asking Asobo to address that I think have a detrimental effect on the experience of my aircraft, but clearly not everyone feels this way.

This is a common problem. When you load in on the ramp just click Esc and then click Restart. Fixes it every time.

@Black-Square Sure, you are welcome. John Hodgson or Mark Allison should have my contact details.

Yeah should do and ITT, I find it more noticeable when in the climb and I turn them off, get a spike you have to watch out for. Cheers James

It's been almost a year since that thread, and I think it's time to revisit it by asking Nick whether he managed to resolve the issue and whether we can expect the mixture system to be fixed in the upcoming MSFS 2024 update. This is actually one of the main bugs affecting the Duke, and I’m really looking forward to it being fixed, as it seriously hurts immersion – just like the non-functional headset muting, incorrect glass surface texturing in MSFS 2024, or the oxygen consumption issue that was mentioned in one of the threads. Another question – before the Duke update for MSFS 2024 is released, can we expect a changelog, or will it rather come as a surprise? And as a community, do we have the option to request specific fixes, understanding of course how busy Nick is with all the tasks? Either way, I’m really hoping this fix makes it in – after more than a year, I’m personally counting on it. Regards, Seb

@szln6z said in CTD with duke: 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).