Having just returned from holiday, I updated to SU13 yesterday and set up a flight in the Fenix A320 yesterday from KLGA to KDCA. The only add-on I was using was the updated FSLTL. Not sure exactly when, but about half an hour in to the flight I had a CTD - not had one of these for many months. So, thought I would try a different flight, and again with the Fenix A320, I set up a flight from KDCA to KORD, and again used FSLTL. The same thing happened - a CTD after half an hour or so in to the flight.

In checking with this forum, I saw a similar type of thread, in which there was a reply that suggested that FSLTL may be injecting too many objects - which could be the cause of the CTD.

So today, I set up a new flight with the Fenix A320 form KDCA to KORD - but this time WITHOUT FSLTL, and the flight was absolutely fine, and thankfully no CTD - so I assume that I can safely say that FSLTL is the cause of my CTDs - can I?

I recall that there are some settings in FSLTL, which allow you to determine the number of airplanes that are injected - not sure why the parameters may have changed (if indeed this is the cause of my CTDs) from pre SU13 to post SU13. Any thoughts or suggestions - maybe someone could advise me of the changes that I need to make to the settings with reference to the number of airplanes injected.

or - any other thoughts.

 

25 minutes ago, SquadronLeader said:

Having just returned from holiday, I updated to SU13 yesterday and set up a flight in the Fenix A320 yesterday from KLGA to KDCA. The only add-on I was using was the updated FSLTL. Not sure exactly when, but about half an hour in to the flight I had a CTD - not had one of these for many months. So, thought I would try a different flight, and again with the Fenix A320, I set up a flight from KDCA to KORD, and again used FSLTL. The same thing happened - a CTD after half an hour or so in to the flight.

In checking with this forum, I saw a similar type of thread, in which there was a reply that suggested that FSLTL may be injecting too many objects - which could be the cause of the CTD.

So today, I set up a new flight with the Fenix A320 form KDCA to KORD - but this time WITHOUT FSLTL, and the flight was absolutely fine, and thankfully no CTD - so I assume that I can safely say that FSLTL is the cause of my CTDs - can I?

I recall that there are some settings in FSLTL, which allow you to determine the number of airplanes that are injected - not sure why the parameters may have changed (if indeed this is the cause of my CTDs) from pre SU13 to post SU13. Any thoughts or suggestions - maybe someone could advise me of the changes that I need to make to the settings with reference to the number of airplanes injected.

or - any other thoughts.

 

I don't think too many objects cause a CTD, AIG inserts hundreds of aircraft on my potato computer without a problem.
There was another guy yesterday or so that had MSFS crash near KIAD since SU13. Maybe it's a geografical problem?
Also since you say it doesnt crash without FSLTL - there's a possibility that a faulty scenery AFCAD leads to a CTD when a traffic injector tries to inject. I've had that happen with AIG a couple of times (freeware Kuwait, Teterboro). But you say there's no addon you use? This would mean it's the default scenery, but I don't think that's possible.

Have you done all the usual black magic/dances? Clearing rolling cache etc.?

I've been an FSLTL user from day one have yet to have a CTD that I could attribute to FSLTL - even when used at busy airports and/or with dozens of addons. This includes the most recent FSLTL injector updates.

I'd go with the faulty AFCAD theory - or a combination of other addon clashes unrelated to FSLTL itself.

I'be had a few simconnect issues, but I run TrackIR, FSLTL and Littlenavmap and don't know which of these is causing those crashes or even if they all use simconnect.

As far as FSLTL is concerned, it does add load to MSFS and might therefore cause some stutters and loss of FPS, particularly at busy airports but many are using it without any issues alongside dozens - if not hundreds - of other addons.

Been using FSLTL for hundreds of flights, no issues at all. 

Can concur. No issues regarding ctd. Even more, last build 1.6.1 seems to be be better than ever.

I had a random CTD just before St.Johns on a transatlantic flight the other day - KPHL to EIDW. I put it down to a dodgy livery I had just used. When I restarted with a different livery I completed the 6 hour flight with no issues. Completely random but the timing around updates made me think it could be related here. It's the 1st CTD I had in well over 6 months too.

No problems at all with FSLTL as long as i can think..

User since it hits the scene.

cheers 😉

@SquadronLeader Just a note that FSLTL was updated when SU13 came out, so you might want to run the installer and see if there's an update available for the injector.

 

59 minutes ago, Phantoms said:

@SquadronLeader Just a note that FSLTL was updated when SU13 came out, so you might want to run the installer and see if there's an update available for the injector.

 

There was an update after su13 and there has been a further update today.

Im having a crashes with every flight on the fenix now after su 13, originally it seemed to me like it was caused by fsltl because i was able to get in one good flight with it disabled but it happened again without fsltl last night... not sure what is going on.

I was in the beta with no issues but have had several CTD's since su 13 went official.

Same here, 2 CTD today (PC shutdown) after SU13. No FSTL, yes Fenix + PSXT/Real Traffic .

1st ctd approaching Mykonos, 2nd ctd approaching Dublin. Not a great day for my MSFS.

I have conducted two flights in MSFS since updating to SU13, and I have had two CTD's, both an hour to hours into flight. I have another thread with more info on my CTD's. Once was in the Fenix, and one was in the A2A Comanche. Both flights with FSLTL, both flights with Accuseason Advanced. Right now I am conducting a flight without FSLTL to see what happens. 

No crashes with FSLTL for me so far