CTDs with Duke when just touching down on long flights since SU5
-
Did you try other destination airports? Did you also try loading directly at the destination? It may be an issue with that specific airport, so I would start by checking there first
-
Tried the same flight again and it went fine. Both the failure and sucess on runway rnav z 19. Then tried same flight and landed on ILS 01 runway and it ctd again. I'm lost it happened with the grand duke and regular duke. Don't have any failure with PMDG 736. Never had the problem before su5.
-
Tried the same flight again and it went fine. Both the failure and sucess on runway rnav z 19. Then tried same flight and landed on ILS 01 runway and it ctd again. I'm lost it happened with the grand duke and regular duke. Don't have any failure with PMDG 736. Never had the problem before su5.
@bill721 is it a custom airport scenery? It could be a scenery issue, not an airplane issue.
-
It isn't a custom airport. I really don't know what the issue might be. I've been trying to figure it out. It happens at different airports at different times. I saw that there is going to be a MSFS 2024 update to help correct some of the issues SU5 is causing. I hope it helps. It fails just as you are touching down on the runway. I wonder if it has to do with the enhanced runway effects the Duke has?
-
-
Hi, I'm WafflingSnow on the MSFS forums. I had this happen twice. I flew from KMDT to KACK, and there was a CTD on landing. I used BeyondATC on that one. The next day I flew from KACK, did a tour of NYC up the Hudson, and returned to KACK for a CTD on touchdown. Yesterday, I deleted the cache file and updated my Nvidia drivers. I took off from KACK, remained in pattern, landed no problem. Then, I took a flight from KACK to KORF with BeyondATC and landed no problem. So, deleting the cache and updating drivers worked for me, at least so far.
