CTD with duke
-
For the past month, i have had CTDs with the duke. It hasn't done this since i first bought it in August 2024.
I can do short flights with the duke without issue (less than 1 hour) but long cross country flights (more than 1 hour) is where the CTDs happen. I can do long cross country flights in every other aircraft without issue.
I have attached information about my last flight with the duke below.
GRAND DUKE
XBOX SERIES S - MSFS2020
Live Weather
Live time
PG - OFF
ROLLING CACHE - OFFPMS50 GTN 750 + GTN 650 VERSION 2.2.30e
CYSK - CCQ3
TEXEX AGLOL H5070 LEXEN OVIXI AVIXO HETHN IRBIK XUKTI
CTD 20nm out from LEXEN
Cruise Altitude: FL230
45% POWER
I would like to know why it is CTDing and how it can be fixed so i can continue to enjoy the duke.
-
Sorry that's happening to you. Nothing is more infuriating than a CTD at the end of a flight. Luckily, I can't recall a single reported case of CTD's with the Dukes that wasn't a one-time thing, or wasn't eventually attributed to something else. The method that I have chosen for programming my aircraft makes them delightfully resistant to CTD's, unlike aircraft that use a lot of WASM instruments.
From what I've seen in my own coding, I always suspect the GPS unit in the case of CTD's, because the simulator's native flight planning system seems to be one of its least stable aspects. For the sake of testing, I would recommend using another GPS unit on a couple flights to see if the CTD can be attributed to the GTN 750/650.
Feel free to report back here, but I might also recommend contacting Just Flight support. They have a knowledgebase for general simulator issues, while I specialize in the aircraft specific knowledge. They will also have access to an XBOX for testing, if that's needed. Please let me know what you discover!
-
Sorry that's happening to you. Nothing is more infuriating than a CTD at the end of a flight. Luckily, I can't recall a single reported case of CTD's with the Dukes that wasn't a one-time thing, or wasn't eventually attributed to something else. The method that I have chosen for programming my aircraft makes them delightfully resistant to CTD's, unlike aircraft that use a lot of WASM instruments.
From what I've seen in my own coding, I always suspect the GPS unit in the case of CTD's, because the simulator's native flight planning system seems to be one of its least stable aspects. For the sake of testing, I would recommend using another GPS unit on a couple flights to see if the CTD can be attributed to the GTN 750/650.
Feel free to report back here, but I might also recommend contacting Just Flight support. They have a knowledgebase for general simulator issues, while I specialize in the aircraft specific knowledge. They will also have access to an XBOX for testing, if that's needed. Please let me know what you discover!
@Black-Square I will email just flight support tonight and will do some test flights with the GNS series GPS installed on monday and will report back.
Thank you!
-
I have been unable to conduct a full test flight as i have been having issues with my internet..
I was in contact with JF support, and it seems they dont know what the issue could be either and i havent heard back from them in 2 days.
I do believe it is a GPS issue. Perhaps an outdated GPS?
-
I suggest checking in with Just Flight Support as well, because CTD's are very rare in my aircraft by the nature of the pipeline I've chosen to program them. With the Dukes specifically, the likelihood that a CTD would come from a GPS addon and not my code is extremely high.
I suspect this problem is related to an outdated GPS or improperly implemented addon packages in your Community Folder. Make sure all GPS addons are up-to-date, even if you're not using them at the present moment in the aircraft. I'm happy to help, so please stay in touch if you want to troubleshoot more!
-
I've just had a CTD with the turbine Duke too:
-
MSFS 2020 running on Windows 10
-
Flight was supposed to be about 190 NM (just over 1 hour)
-
No GPS configured in the aircraft, only the legacy King/Bendix stack, only using VOR nav
I haven't done more tests yet, but I certainly will. I did have a few other apps running in the background, including skyvector, so I will first run a test without anything else running on the PC.
I purchased both Dukes a while ago but started flying them just now. I really enjoy flying them - I love the super detailed implementation, the great graphics, the extraordinary sound modeling, and the great flight model.
-
-
I've just had a CTD with the turbine Duke too:
-
MSFS 2020 running on Windows 10
-
Flight was supposed to be about 190 NM (just over 1 hour)
-
No GPS configured in the aircraft, only the legacy King/Bendix stack, only using VOR nav
I haven't done more tests yet, but I certainly will. I did have a few other apps running in the background, including skyvector, so I will first run a test without anything else running on the PC.
I purchased both Dukes a while ago but started flying them just now. I really enjoy flying them - I love the super detailed implementation, the great graphics, the extraordinary sound modeling, and the great flight model.
@andyw248 said in CTD with duke:
I've just had a CTD with the turbine Duke too:
-
MSFS 2020 running on Windows 10
-
Flight was supposed to be about 190 NM (just over 1 hour)
-
No GPS configured in the aircraft, only the legacy King/Bendix stack, only using VOR nav
I haven't done more tests yet, but I certainly will. I did have a few other apps running in the background, including skyvector, so I will first run a test without anything else running on the PC.
I purchased both Dukes a while ago but started flying them just now. I really enjoy flying them - I love the super detailed implementation, the great graphics, the extraordinary sound modeling, and the great flight model.
Every once in awhile I get a CTD with the Turbine Duke. A few weeks ago I had a rash of them, and I updated the PMS GTN 750, which seems to have cured most of them. I had another one yesterday on about 1 1/2 hour flight. I fly multiple flights a day, and the Duke seems to be the only aircraft that causes CDTs.
-
-
Nick, I have done a few flights with the duke (piston) using the PMS50 only difference is im importing flight plans using simbrief. I have not suffered any CTDs using this method.
However, i attempted to use the TBM850 with the PMS50 750 and WT GNS530W, using the world map to plan the flight and i got a CTD after nearly 2 hours.
This leads me to believe that the default flight planner in 2020 and the PMS50 are not getting along to put it simply. Why, i dont know as this method of flight planning worked fine before. Could be the sim, or an outdated GPS as i detailed below.
Looking at the pms50 system status page, the version installed is 2.2.30e in the duke and 2.2.40e in the tbm
According to the PMS50 website, the current version is 2.2.48. It is impossible to update the GTN gps on xbox without the aircraft developer issuing an update with the latest version included.I am using MSFS2020 SU15.
-
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.
