Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FSLTL - live traffic finally released

Featured Replies

11 hours ago, Cpt_Piett said:

Yeah, the model matching with default live is all over the place. Also there's a lot of generic models. The AI logic is way better though. I've been switching back and forth. With the injector I don't get much traffic, and no approaches. 

This is Dublin with real-time online and FSLTL models: 

gulf air dont fly to dublin.  got to love vatsim.

Edited by Ray Proudfoot
Embedded image removed

 
 
 
 
 
  913456
  • Replies 1.3k
  • Views 226.1k
  • Created
  • Last Reply
47 minutes ago, Piotr007 said:

No, I mean something different. I do not mean runway stacking when taking off and those stupid non takeoff bug from certain rwys. I mean real stacking one on top of another at EHAM when flying away from it or flying to it from a diff dest airport.

There is a nasty bug in MSFS causing AI to get bugged at certain airports. This causes the immense lag and fps drops to below 15 all people seem to talk about at times.

This bug causes airplanes to load one on top of another at center of the airport. Sprite/model stacking cause heavy hits on CPU no matter what. A sidenote on this as well is that there are not airplanes at the gate when this happens, as all of these are piled up at the center of the airport.

Restarting FSLTL does not work to cure this. The models are stuck until you restart the same flight.

 

Never seen that, Have you reported it?:

AMD Ryzen 7 5800x3d, MSI X570 Pro, 32 gb DDR4 3600 ram, Gigabyte 6800 16gb GPU, 1x 2tb Samsung  NvMe , 1x 2tb Sabrent NvME, 1x Crucial 4tb Nvme M2 Drive

A comment from a FSLTL representative over at the official forums: 

Quote

Just to keep everyone in the loop on what we are seeing with FSLTL - and under investigation with Asobo. It would appear that when an aircraft is on approach it will now always pick the first STAR alphabetically for the airport in use - we have tested this on a number of airports and it always seems to hold true. We believe the same is also happening for SIDS on departure - first one alphabetically. In SU10 aircraft where basically vectored without procedures from the final waypoint or to the first waypoint in the plan respectively.

This basically leads to weird arrival and departure patterns when those first alphabetically items don’t align with an aircraft arrival or departure direction.

Hopefully we can find a way forward with Asobo that allows us to deal with this before SU11 launch either by way of a fix from Asobo or a workaround we can implement.

So to that end you can happily use SU11 with FSLTL - but arrival patterns and departures will look strange!

As for myself I'm mostly using real-time online traffic in the beta. Someone asked how the logic is improved:

  • AI can spawn anywhere, not just at gates/stands. I.e. don't get the same rushing to the active runways as all AI depart simultaneously 
  • I've yet to see spinning AI on taxiways. I know others report this. 
  • Vacating runways seems more efficient, at least in some places

One of the drawbacks is that the model matching is very bad leading to lots of generic models and airliners that are simply wrong for the location (e.g. Gulf Air in Dublin as someone pointed to). 

7950X3D | RTX 4090 | 64GB DDR5

45 minutes ago, Car147 said:

Never seen that, Have you reported it?:

I have reported it to Asobo. FSLTL FAQ check that last issue on their site. Stacking AI is Asobo issue. They have to solve this.

My worries are their capabilities on this matter though. AI is wrecked since release.

I9 12900K @ 5.1ghz P-cores/ 4.0 ghz E-cores fixed HT off / Corsair iCue H150i Capellix Cooler/ MSI Z690 CARBON WiFi / 32GB Corsair DDR5 RAM @ 5200 mhz XMP on / 12GB MSI 4090 RTX Ventus 3 / 7,5 total TB SSD (2+2+2+1+0,5 all NVMe)/ PSU 850W Corsair / 27" (1080P)

1 hour ago, kiek said:

No program can beat PSXseeconTraffic in model matching 😉

Come back with ADB-S option like before and for sure a lot of people here will use PSX

41 minutes ago, motishow said:

Come back with ADB-S option like before and for sure a lot of people here will use PSX

So you agree that PSXseeconTraffic is the best.

Just testing some more with real-time online traffic using both FSLTL and AIG models. And I used Corsten's method for preventing generic models. I'm also using the injector with parked at 5 (I think max is 10). This is Dubai Intl:

8myZUsO.jpg
vZx4E02.jpg

 

7950X3D | RTX 4090 | 64GB DDR5

What's the consensus? Overall, is the FSLTL FlightAware based traffic injector still better than using default real live traffic in SU 11 BETA, or is default live traffic now preferred? What are the advantages to default live traffic over using the FSLTL injector (in SU11 BETA)?

19 hours ago, kiek said:

So you agree that PSXseeconTraffic is the best.

yes.

 
 
 
 
 
  913456
19 hours ago, kiek said:

So you agree that PSXseeconTraffic is the best.

apart from the PAX/CARGO bit in p3d

 
 
 
 
 
  913456
On 10/17/2022 at 12:45 AM, steve310002 said:

What's the consensus? Overall, is the FSLTL FlightAware based traffic injector still better than using default real live traffic in SU 11 BETA, or is default live traffic now preferred? What are the advantages to default live traffic over using the FSLTL injector (in SU11 BETA)?

FSLTL does not use Flightaware. It uses Flightradar24 data to inject aircraft into the sim, then passes those aircraft and their positioning over to MSFS' ATC. MSFS' default live AI traffic does the same, except uses data from Flightaware. 

You can in fact use the FSLTL models with MSFS' own Flightaware data, and skip the FSLTL injector altogether. MSFS will use FSLTL models as well as AIG or any other third party model provider you may have in your community folder.

However seeing what Flightradar24 brings to the table, I don't see why anyone would chose otherwise. Flightradar24 data really livens up the skies more so that Flightaware- for not costing anything moneywise that is. 

NZXT H7 Flow PC Case. 6X Corsair LL140 RGB Fans. Seasonic GX-1000 Focus Gold Power supply. Asus ROG Strix Z690F. Intel Core i9 14900K @5.7Ghz. NZXT Kraken X63 280mm AIO. 64Gb (2x32) Corsair Dominator DDR5 CAS40 @ XMPII. EVGA 3090ti FTW3 Ultra.  Main Fltsim Storage: Samsung 990 Pro 2Tb NVME.

1 hour ago, vyper883 said:

FSLTL does not use Flightaware. It uses Flightradar24 data to inject aircraft into the sim, then passes those aircraft and their positioning over to MSFS' ATC. MSFS' default live AI traffic does the same, except uses data from Flightaware. 

You can in fact use the FSLTL models with MSFS' own Flightaware data, and skip the FSLTL injector altogether. MSFS will use FSLTL models as well as AIG or any other third party model provider you may have in your community folder.

However seeing what Flightradar24 brings to the table, I don't see why anyone would chose otherwise. Flightradar24 data really livens up the skies more so that Flightaware- for not costing anything moneywise that is. 

Unpopular opinion. I prefer using the FSLTL models with e MSFS Live Traffic because traffic appears active and in place right from the start. Where as the FSLTL injector takes a while to "warm up" after injecting the models to actually get them moving along.

The only downside to that. The generic white models can't be gotten rid of. 

Edited by styckx

ASUS ROG STRIX Z390-E GAMING / i9-9900k @ 4.7 all cores w/ NOCTUA NH-D15S / 2080ti / 32GB G.Skill 3200 RIPJAWS / 1TB Evo SSD / 500GB Evo SSD /  2x 3TB HDD / CORSAIR CRYSTAL 570X / IPSG 850W 80+ PLATINUM / Dual 4k Monitors 

1 hour ago, styckx said:

Where as the FSLTL injector takes a while to "warm up" after injecting the models to actually get them moving along.

Hopefully this is something the good people who brought us FSLTL can improve upon especially with the recent AI traffic updates in SU 11 BETA. I agree that whilst I prefer using the traffic injector, it is frustrating that it takes a while for things 'to get going' at airports and in the skies.

1 hour ago, styckx said:

Unpopular opinion. I prefer using the FSLTL models with e MSFS Live Traffic because traffic appears active and in place right from the start. Where as the FSLTL injector takes a while to "warm up" after injecting the models to actually get them moving along.

Should be fixed for SU11 + FSLTL.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.