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!
