Hi, title says it all. A fix would be welcomed. Thanks.
Hi,
No, the title says not all … May I ask which sim you´re using? MSFS2020 or MSFS2024?
Thank you,
Richard
Hi Richard, you are right. MSFS 2020. Yesterday I could load a flight from KSFB. With todays update CTD every time I try to. Thanks very much for the quick reply.
Richard, I’ve run more tests and the offending file is APX26210.bgl from latest v2501.
Thanks for your analyzes, let me check it …
Cheers
Richard
You are welcome Richard.
5 posts were merged into an existing topic: About the Staff category
Hi,
I have made now several tests and I can´t reproduce a CTD at KSFB, sorry. I have flown now 20-30 miles around the airport with the C172, no CTD - also in slew mode, no CTD. So, it looks a “unknown” CTD as so many in the MSFS world.
I have also checked the airport-file and also here I can´t see any issue here.
Possible, I have done something wrong or in the wrong way … Can you explain a little bit more in detail that I can possible try to reproduce it?
Thank you very much,
Richard
Weird, I had the exact same issue starting at CYYJ, as soon as I try and select a parking spot from the drop down I get an instant CTD. Aircraft selected (if it makes any odds) was PMDG 737.
Repeated twice after the initial CTD with same results, then removed the Navigraph base data and it was absolutely fine.
G
I can confirm, I can reproduce it at least here at CYYJ …
Checking … thank you!
Cheers
Richard
I have also seen this around KASH. Crash only happens with the 2501 rev.1 navdata added for MSFS 2020. No other addons enabled/installed.
I am experiencing the same issue at KBLI.
Navigraph causing CTDs in the Northeast (kmht). Remove navigraph and it works fine.
I am also experiencing this with KBLI and S50.
I’ve put a repro in place here https://forums.flightsimulator.com/t/ctd-when-starting-world-map-flight-at-s50-with-navigraph-loaded/701142
Not sure what you expect there but ok …
We have identified a small issue (magnetic variation) on some airports in the current cycle 2501 rev. 1 …
We are working on an fix and will release a second revision which should solve this CTDs in some areas.
Thank you
Richard
I expect to be told I filed the bug in the wrong place. Thanks for conforming to my expectations despite the fact that the underlying cause was not clear. Last year there was a CTD where the issue was MSFS improper injestion of nav data but that only got revelaed when Navigraph was loaded. I’m a big believer that the issue should be identified at the closest point of failure.
I appreciate you working on a potential fix.
Thank you Richard. Tested and working like charm. Great week.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.