A350 Causing CTDs Mid Flight on MSFS 2024

[AthlonHD]

I've met same situation when I take off from RJBB, also CTD at same point shortly after take off.

And finally I found that NONE of the RJBB scenery on sale now is compatible with MSFS2024.

So, some of CTDs also may caused by incompatible scenery s.

[Kolo]

Yesterday, online on FSDT-Server, after 2 hours and in holding ( several holdings were stabil) I got the CDT unfortunatly. Verry sad about it. Never got this with 2024 and Fenix A320.

[Philippe TORNE]

I am also experiencing CTDs using the A350 (version 1.0.7) in combination with FSLTL models. I investigated further and found something interesting I would like to forward to the iniBuilds team here :

- Flying without FSLTL models: No CTD

- Flying with FSLTL models and no traffic display on any ND (TRAFF EFIS switches OFF on both sides, ADS-B OFF in the SURV page) : No CTD

- Flying with FSLTL models and traffic displayed on the ND (either TFC or ID selected on the EFIS) : CTD after a random time (1 to 3 hours)

I tested on many different flights, different sceneries and always the same behavior. So my conclusion is that there is something wrong with the way the A350 processes data from FSLTL during the ND injection process. I hope this report will help solving this annoying issue.

Edited Saturday at 11:53 AM by Philippe TORNE

[Kolo]

I can confirm Philippe. I got the CTD  2 times with use FSLTL Models as Modelset for VATSIM Onlinetraffic.

[Samir-1997]

4 hours ago, Philippe TORNE said:

I am also experiencing CTDs using the A350 (version 1.0.7) in combination with FSLTL models. I investigated further and found something interesting I would like to forward to the iniBuilds team here :

- Flying without FSLTL models: No CTD

- Flying with FSLTL models and no traffic display on any ND (TRAFF EFIS switches OFF on both sides, ADS-B OFF in the SURV page) : No CTD

- Flying with FSLTL models and traffic displayed on the ND (either TFC or ID selected on the EFIS) : CTD after a random time (1 to 3 hours)

I tested on many different flights, different sceneries and always the same behavior. So my conclusion is that there is something wrong with the way the A350 processes data from FSLTL during the ND injection process. I hope this report will help solving this annoying issue.

That’s interesting, I will do a flight today with FSLTL and keep TRAF and ADS-B off and see if that works. I’ll report back soon. 

Edited Saturday at 04:39 PM by Samir-1997

[Samir-1997]

20 hours ago, Samir-1997 said:

That’s interesting, I will do a flight today with FSLTL and keep TRAF and ADS-B off and see if that works. I’ll report back soon. 

I can confirm, I just did a 7 hour flight with FSLTL traffic. I kept TCAS, ADS-B, and TRAFF off. No CTD and no issues. 

Edited 13 hours ago by Samir-1997