I think fstl needs to be updated because after doing this, I still have a CTD, but only in a part of Asia around Hong Kong. Anyone else having this problem?
@DutchPilot5987, have you confirmed that the CTD only happens with FSLTL running in that region?
If you temporarily move the FSLTL folders (fsltl-traffic-base and fsltl-traffic-injector) from inside your community folders to another location and then start up FS2020 without running FSLTL and recreate the same flight as closely as possible, then if the CTD still happens, you can rule out FSLTL as the cause.
I’ve been having CTDs around Bangkok, but only when traffic was injected; if I disabled it and left only parked/VFR elements, the crashes stopped.
Don’t know which way to report that since it seems like an issue with MSFS but only when a specific product is interacting in a specific way (and the traffic shipped with the sim doesn’t want to load for whatever reason); the bucket has a consistent number 1211106684061576570, but I can’t figure out the root cause from that
Indeed, if I don’t activate the injector, I no longer have CDTs. But yesterday I switched from DX11 to DX12, and then it worked with the injector activated? But with DX12, I have more stuttering…
Same for me… Can‘t fly around Asia with BATC active. It‘s a shame since I‘ve recently purchased alot of sceneries in asia… BATC told me when I did the BugReport that it has to do with fauly NavData from Msfs… not their issue. But what now?
I haven’t been able to use BATC traffic at all since SU16 without CTD. I fly mostly in Asia-Pacific. The sim does work with BATC if the traffic is ‘airport static’ only….with one major exception being at pay-ware VTBD (Don Mueang in Bangkok) - instant CTD (or baulked load-in of BATC) there regardless of BATC traffic status. I use FSLTL models for BATC. I just tested at a bunch of other pay-ware airports in the region and they seemed OK (again only if NOT using en-route, arriving or departing BATC traffic…static only), those were VTBS, RPLL, VHHH, WSSS, WMKP, VTSP, VTPP.
I have the exact issue after the latest update to MSFS20. I fly in Asia Pacific most of the time and CTDs occur minutes after my aircraft is spawned at the gate. I have tried EA and Experiential version of BATC but without success.
All is run well without without FSLTL injection by BATC.
From BATC Discord Server: “For those on MSFS2020 SU16 - there are significant bugs introduced by Asobo in the release of SU16 that causes the sim to crash when traffic is injected (seems worst flying in Asia). This affects all traffic injectors not just BATC. It is not something we can fix. Only Asobo can resolve these issues. Your only option currently if this is impacting you is not to use traffic on MSFS2020”
I can also confirm. I usually fly around North America and Europe, but I ventured over to BKK and then to NRT. Had a CTD enroute from BKK to NRT, but figured it was a one-off. The second attempt of BKK-NRT was a success, but when I attempted to depart NRT, my sim CTD each time I ran BATC. I even ran FSLTL on its own without BATC and still received a CTD. Guess I’ll have no traffic and no BATC until I’m back in North America. Hopefully this helps someone.
It is possible that the new AIRAC in force today will carry the fix when Asobo pushes it to the sim, otherwise there have been background movements to find a workaround
Apparently it did not fix the Chinese issue yet at least. Not the Navigraph version, not sure about MS. Even better if they can fix the bugs they introduced.
Technically that board is for crashes that happen on the naked sim, without any additions - which this isn’t, as it’s about some add-ons not playing nicely with it, which should be resolved at the dev level.
From FSLTL’s admin:
After testing the sim and Navigraph after the new AIRAC 2509 release, nothing has changed. The following is still true:
Without Navigraph:
Requesting navdata for ZLXY is successful,
Requesting navdata for ZSQD causes the sim to crash (the sim doesn’t have the ZSQD airport),
With Navigraph:
Requesting navdata for ZLXY causes the sim to crash,
Requesting navdata for ZSQD is successful (Navigraph does include the ZSQD airport),
Navigraph is aware of the ZLXY data issue, they are able to reproduce the issue and are looking into it. The sim issue with ZSQD may be due to the airport not being included in the sim. If so, the issue may be more with the sim, and not with the navdata (since there is none). Its possible a change in SU3 has introduced a scenario where the sim crashes when navdata is requested for an airport that doesn’t exist. Not sure. It has been reported to Asobo, with no response so far. And others have reported similar issues with other airports to Asobo as well. As of now, we have no plans to make any temporary changes to the injector to try and workaround this issue, but that may change.