Hello, in MSFS with AIRAC 2410, if near VHHH and with Navigraph installed, I get CTDs, and a few other users on a couple of Discord servers have reported similar issues. At first, we suspected the cause was FSLTL, the traffic injector, but I did some testing with a clean community folder and without the scenery installed, and it only CTDs with FSLTL and Navigraph installed; there is no crash if Navigraph is uninstalled. This issue happened for me with both rev.1 and rev.3, and another user reported it happening with rev.2.
Could this be an issue with the Navigraph data? I talked to a FSLTL member and they said, “We query for the same data the same way for all airports, and we don’t query differently if Navigraph is installed.” Other users have also reported the CTDs stopping after uninstalling Navigraph.
Hi,
I´m sorry, but I can´t really answer this because I don´t have FSLTL; therefore, I can´t test it. Strangely, this happens only at VHHH, which is very uncommon.
But anyway, I can´t really answer this due to the missing contact to FSLTL, the missing add-on, and the very general “near VHHH” area.
What I can say is that I have just flown a little bit in the VHHH area (stock scenery) and have no CTD (approx. 15 min). It’s difficult to say, but it looks more like a combination of something. Again, I can´t really test this, so I can´t really help you. I´m sorry.
Hi, by “near VHHH” I just meant that it happens when there are AI aircraft injected by FSLTL at VHHH. The developer’s exact words were: “in sim, if near VHHH and with Navigraph installed, the sim crashes if a SimConnect-connected app queries for data. There is no crash if Navigraph is uninstalled”.
I have flown at a few other airports with no issues thus far, and a few other users have reported the same issue at VHHH hence why I specified the airport. I have not had the issue when FSLTL is not running, which is why I assume it’s something to do with how the AI aircraft are being injected and the interaction with the navdata. I have not had this issue before 2410. I’ve reinstalled 2410 to no avail either.
Hi again,
After a night session, it seems we have identified the issue. I can´t say if it´s working with FSLTL because I can´t test it, but it was an issue with a time-out in SimConnect due to a wrong internal reference on these airports:
5AR8
EDDT
WAMI
WAVE
WAVG
WAYE
WIPY
ZSQD
I´m currently building a new revision, and we will upload it soon in the hope that the CTDs are gone with FSLTL now. Any feedback about it is highly welcome. Thank you for your patience and your pre-analysis—the SimConnect reference was in the right direction. This bug has existed nearly since day one in our data, so sadly, this is not a new one - but the truth.
I keep you informed here when revision four is uploaded and ready.