Enhanced Live Traffic 3.03 Update released

I really have to thank you for the update[s]

GA trafffic works quite well with FSLTL. A bit too well maybe :sweat_smile:

I was flying around Santa Barbara and had 2 nearly mid air collisions with a Cessna and a Baron
 it is brutal how many GA pilots are buzzing around L.A. on Sundays, and I really should take more care for the collision avoidance feature of the GTN 750 by now.

Again, thanks for your work!

ELT & FSLTL is now highly recommended for us low & slow boys


Impossible to got a better screenshot,as I was zig zagging trough the L.A. Airspace to avoid mid air collisions.

Thank’s for your comment! I can tell you that I had that in real live here in Austria two times this year. So the simulator is really close to the reality! :wink:

Hello. One question, for clarification.
Since both addons (FSTL and ELT) inject AI traffic from the same data source, flightradar24.
What extra contribution adds the use of the two addons simultaneously?
Thank You

The difference lies in the following points:
ELT uses live traffic WITHOUT flight plans and flies approximately the same route (with waypoints all 30 seconds) as the original aircraft.
FSLTL uses the start and destination data and the data from a database to create a flight plan (without database the aircraft flies directly from start to destination) and passes the complete control to the MSFS AI logic. All planes without a flight plan (GA) will not fly so exactly like in ELT.
The combination of the two (ELT and FSLTL) may be of interest to VFR pilots, since in ELT the VFR fliers fly as closely as possible to their original routes. In addition, with ELT you can hide the unwanted other traffic. (So airlines through FSLTL to see for example better landings and VFR traffic (GA and Gliders or all without flight plans) - with ELT.
If you want to see as close to real time traffic as possible, then ELT is recommended. If you prefer to have airliner traffic that flies the route between destinations according to flight plans and you want to have better taxi traffic and landings, then FSLTL is recommended. (The landing in ELT is not as smooth as it is in FSLTL - because there is no flight plan and FR24 does only tell in the data’s, that the plane has already landed and not that it will land shortly)
FSLTL also works with the built-in ATC because of the flight plans.
For ELT I recommend the combination of Live ATC (for the traffic realistically mapped in the MS) and Pilot2ATC for your own air traffic control - here the near traffic is also informed by P2A.
It always depends on what you want exactly.

2 Likes

OK. Thank you very much for the clarification. Your explanation is very interesting.

From what I had read, I thought this was not currently possible. I thought that once the traffic was injected, the simulator’s own AI would take control of the planes.

Since ELT has an option to exclude certain type of traffic.
Is it possible to launch both injectors simultaneously and that each one handles a certain type of traffic?

For example, FSLT for airlines (setting a value of 0 for VFR and Parking)
ELT for VFR traffic, establishing exclusions for Airlines, Ground Traffic and Low, Mid and High traffic.

Is ELT also compatible with Pro ATC/SR?

Yes! You can set VFR traffic to 0 in FSLTL and in ELT for example you exclude all other traffic except GA and Gliders.

It should work like P2A. So it should tell you the close traffic. I don’t know 100% because I don’t use ProATC and I don’t know which information you will get in difference to the original ATC in MSFS.
All I can tell you is, that the traffic will be shown in Garmin. If in TCAS also I don’t know. Would be helpfull if anybody can check that!
PS.: If you exclude the LOW traffic, you would exclude all GA and Gliders under 10.000 ft. So exclude only the HIGH traffic and if you want the MID traffic. But you don’t have to do it if you exclude the Airliners!

1 Like

For example, FSLT for airlines (setting a value of 0 for VFR and Parking)
ELT for VFR traffic, establishing exclusions for Airlines, Ground Traffic and Low, Mid and High traffic.

This is what I did. see the screenshots above.

But with the LOW Traffic you are excluding all aircraft’s from ELT under 10.000 feet. So if you want the GA traffic by ELT you should not exclude a LOW or MID traffic. You should not exclude any traffic others than Airliners (and Ground traffic if you don’t want to see GA traffic on the ground)


How about the option to show Gliders? I mean, the sim doesen’t support them officialy for now.

There’s a lot of freeware at flightsim.to. Would be nice if we can use them.

You can - at the moment with the freeware later on with the official gliders - even with the helicopters. You have to set it in ModelMatching.json file. Use "GLID: (and here the Glider Model or livery)

2 Likes

Oh jeh, Semor and editing ModelMatching files
 I have zero clue what to do to get this right.

Can you give a short example please?

I’ve been looking at the explanation in the manual and there are things that are a bit confusing. I understand the general sense of what you are doing, but there are parts that I don’t know if they have to be changed in the aircraft.cfg file or in the ModelMatching.json file.

Perhaps a redesign of the tutorial including the final files with all the complete changes, and not just the line you show, would be nice.

On the other hand, I have looked at the ModelMatching.json file and I have not seen any reference to any helicopter by default, so I understand that for helicopters to be displayed you have to configure it manually.

It would be really cool to be able to make these changes directly through the program’s interface.
Likewise changes to the Community and AIG folder paths, rather than having to manually edit the files.

1 Like

How about mix of three:

  1. Msfs built in live traffic (real time online) with FSLTL models
  2. Static aircraft injected with FSLTL injector (boths FR’s disabled,only injected aircraft with setting 1-3
  3. GA traffic injected with ELT

This should be winner with SU11 beta atm.

Here is my ModelMatching.json file (You will find it in the Cofig folder of ELT:
{
“Default Aircraft”: “Airbus A320 Neo”,
“C208”: “Cessna Grand Caravan”,
“GA8”: “Cessna Grand Caravan”,
“Cessna 208B Grand Caravan”: “Cessna Grand Caravan”,
“Cessna 208B Grand Caravan Default”: “Cessna 208B Grand Caravan EX”,
“Airbus A320 Neo”: “Airbus A320 Neo”,
“Airbus A320 Neo Default”: “Airbus A320 Neo Asobo”,
“Embraer E175STD”: “Airbus A320 Neo”,
“Boeing 737-7K2”: “Airbus A320 Neo”,
“Cessna F152”: “Cessna 172P Skyhawk G1000”,
“ECHO”: “Cessna 172P Skyhawk G1000”,
“C172”: “Cessna 172P Skyhawk G1000”,
“C182”: “Cessna 172P Skyhawk G1000”,
“C82S”: “Cessna 172P Skyhawk G1000”,
“C152”: “Cessna 172P Skyhawk G1000”,
“C150”: “Cessna 172P Skyhawk G1000”,
“AutoGyro MTOsport”: “Cessna 172P Skyhawk G1000”,
“Cessna T182T Turbo Skylane”: “Cessna 172P Skyhawk G1000”,
“Cessna 182S Skylane”: “Cessna 172P Skyhawk G1000”,
“Cessna 182T Skylane”: “Cessna 172P Skyhawk G1000”,
“Cessna 182N Skylane”: “Cessna 172P Skyhawk G1000”,
“Cessna 172M Skyhawk”: “Cessna 172P Skyhawk G1000”,
“Cessna 172L Skyhawk”: “Cessna 172P Skyhawk G1000”,
“Cessna 172P Skyhawk”: “Cessna 172P Skyhawk G1000”,
“Cessna 172N Skyhawk”: “Cessna 172P Skyhawk G1000”,
“Cessna 172R Skyhawk”: “Cessna 172P Skyhawk G1000”,
“Cessna 172N Skyhawk II”: “Cessna 172P Skyhawk G1000”,
“Cessna 172 P Skyhawk II”: “Cessna 172P Skyhawk G1000”,
“Cessna 172S Skyhawk SP”: “Cessna 172P Skyhawk G1000”,
“Cessna 172S Skyhawk”: “Cessna 172P Skyhawk G1000”,
“Cessna F172P Skylane”: “Cessna 172P Skyhawk G1000”,
“Cessna F172P Skyhawk”: “Cessna 172P Skyhawk G1000”,
“Cessna 182P Skylane”: “Cessna 172P Skyhawk G1000”,
“Cessna 172P Skyhawk G1000”: “Cessna 172Sp Skyhawk G1000”,
“Cessna 172P Skyhawk G1000 Default”: “Cessna Skyhawk G1000 Asobo”,
“Tecnam P2008 JC”: “Cessna 172P Skyhawk G1000”,
“Tecnam P-92 Echo J”: “Cessna 172P Skyhawk G1000”,
“Ikarus C-42”: “Cessna 172P Skyhawk G1000”,
“Boeing 757-330”: “Boeing 787-10”,
“Boeing 757-232”: “Boeing 787-10”,
“Boeing 757-251”: “Boeing 787-10”,
“Boeing 767-330(ER)”: “Boeing 787-10”,
“Boeing 767-304(ER)”: “Boeing 787-10”,
“Boeing 767-322(ER)”: “Boeing 787-10”,
“Boeing 767-316(ER)(BCF)”: “Boeing 787-10”,
“Boeing 757-256”: “Boeing 787-10”,
“B789”: “Boeing 787-10”,
“Boeing 787-8 Dreamliner”: “Boeing 787-10”,
“Boeing 787-9 Dreamliner”: “Boeing 787-10”,
“Boeing 787-10 Dreamliner”: “Boeing 787-10”,
“Boeing 787-10”: “Boeing 787-10”,
“Boeing 787-10 Default”: “Boeing 787-10 Asobo”,
“Airbus A319-111”: “Airbus A320 Neo”,
“Cessna F150K”: “Cessna Skyhawk G1000 Asobo”,
“Airbus A380-842”: “Boeing 747-8i”,
“Airbus A380-861”: “Boeing 747-8i”,
“Airbus A330-743L Beluga XL”: “Boeing 747-8i”,
“Boeing 747-406F(ER)”: “Boeing 747-8i”,
“Boeing 747-412F(SCD)”: “Boeing 747-8i”,
“Boeing 747-4R7(F)”: “Boeing 747-8i”,
“Boeing 747-8B5(F)”: “Boeing 747-8i”,
“Boeing 747-8KZ(F)”: “Boeing 747-8i”,
“Boeing 747-4B5F(ER)”: “Boeing 747-8i”,
“Boeing 747-867(F)”: “Boeing 747-8i”,
“Boeing 747-830”: “Boeing 747-8i”,
“B744”: “Boeing 747-8i”,
“B748”: “Boeing 747-8i”,
“C5M”: “Boeing 747-8i”,
“Lockheed C-5M Super Galaxy”: “Boeing 747-8i”,
“Boeing 747-8F”: “Boeing 747-8i”,
“Boeing 747-8i”: “Boeing 747-8i”,
“Boeing 747-8i Default”: “Boeing 747-8i Asobo”,
“Cessna F150M”: “Cessna 152”,
“Cessna 152”: “Cessna 152”,
“Cessna 152 Default”: “Cessna 152 Asobo”,
“Cessna CJ4 Citation”: “Cessna CJ4 Citation”,
“Cessna CJ4 Citation Default”: “Cessna CJ4 Citation Asobo”,
“Cessna 525A CitationJet CJ2+”: “Cessna CJ4 Citation”,
“Cessna 525C CitationJet CJ4”: “Cessna CJ4 Citation”,
“Cessna 550 Citation Bravo”: “Cessna CJ4 Citation”,
“Learjet 60XR”: “Cessna CJ4 Citation”,
“Cessna 680A Citation Latitude”: “Cessna CJ4 Citation”,
“Embraer Phenom 300”: “Cessna CJ4 Citation”,
“Embraer Phenom 100”: “Cessna CJ4 Citation”,
“Hawker 750”: “Cessna CJ4 Citation”,
“Bombardier Global 6000”: “Cessna CJ4 Citation”,
“Bombardier Global 5000”: “Cessna CJ4 Citation”,
“Bombardier Challenger 605”: “Cessna CJ4 Citation”,
“Beech 390 Premier I”: “Cessna CJ4 Citation”,
“Pilatus PC-24”: “Cessna CJ4 Citation”,
“Dassault Falcon 2000LX”: “Cessna CJ4 Citation”,
“Dassault Falcon 2000”: “Cessna CJ4 Citation”,
“Learjet 45”: “Cessna CJ4 Citation”,
“Learjet 36A”: “Cessna CJ4 Citation”,
“LJ35”: “Cessna CJ4 Citation”,
“Dassault Falcon 7X”: “Cessna CJ4 Citation”,
“Learjet 40”: “Cessna CJ4 Citation”,
“Learjet 35A”: “Cessna CJ4 Citation”,
“Cessna 560XL Citation Excel”: “Cessna CJ4 Citation”,
“Nextant 400XT”: “Cessna CJ4 Citation”,
“Gulfstream G450”: “Cessna CJ4 Citation”,
“Gulfstream GV-SP G-550”: “Cessna CJ4 Citation”,
“Raytheon Hawker 850XP”: “Cessna CJ4 Citation”,
“Hawker Beechcraft 1000”: “Cessna CJ4 Citation”,
“Cessba 650 Citation VI”: “Cessna CJ4 Citation”,
“Cessna 525B CitationJet CJ3+”: “Cessna CJ4 Citation”,
“Cessna 525 CitationJet CJ1”: “Cessna CJ4 Citation”,
“Cessna 525B CitationJet CJ3”: “Cessna CJ4 Citation”,
“Cessna 650 Citation III”: “Cessna CJ4 Citation”,
“Cessna 510 Citation Mustang”: “Cessna CJ4 Citation”,
“Cessna 560XLS Citation Excel”: “Cessna CJ4 Citation”,
“Gulfstream G650ER”: “Cessna CJ4 Citation”,
“Gulfstream G650”: “Cessna CJ4 Citation”,
“Gulfstream GIV-X (G450)”: “Cessna CJ4 Citation”,
“Pilatus PC-12/47E”: “TBM 930”,
“PC12”: “TBM 930”,
“Piper PA-46-M600”: “TBM 930”,
“Piper PA-46-M500”: “TBM 930”,
“Piper PA-46-500TP”: “TBM 930”,
“Beech B200 Super King Air”: “TBM 930”,
“TBM 930”: “TBM 930”,
“TBM 930 Default”: “TBM 930 Asobo”,
“Beech F33A Bonanza”: “Bonanza G36”,
“AA5”: “Bonanza G36”,
“Socata TB-20 Trinidad”: “Bonanza G36”,
“Piper PA-28-140”: “Bonanza G36”,
“Piper PA-28-181”: “Bonanza G36”,
“Piper PA-28-161”: “Bonanza G36”,
“Piper PA28-161 Cherokee Warrior II”: “Bonanza G36”,
“Piper PA-28R-200 Cherokee Arrow”: “Bonanza G36”,
“Piper PA-28-181 Archer II”: “Bonanza G36”,
“Piper PA-28RT-201T”: “Bonanza G36”,
“Mooney M-20K”: “Bonanza G36”,
“Cessna 337B”: “Bonanza G36”,
“BE35”: “Bonanza G36”,
“Beech G36 Bonanza”: “Bonanza G36”,
“Bonanza G36”: “Bonanza G36”,
“Bonanza G36 Default”: “Bonanza G36 Asobo”,
“EC35”: “Airbus H135”,
“EC30”: “Airbus H135”,
“EC75”: “Airbus H135”,
“EC45”: “Airbus H135”,
“BK17”: “Airbus H135”,
“B407”: “Airbus H135”,
“H269”: “Airbus H135”,
“H500”: “Airbus H135”,
“R44”: “Airbus H135”,
“S76”: “Airbus H135”,
“S92”: “Airbus H135”,
“G2CA”: “Airbus H135”,
“A169”: “Airbus H135”,
“A109”: “Airbus H135”,
“A139”: “Airbus H135”,
“AS32”: “Airbus H135”,
“AS65”: “Airbus H135”,
“R66”: “Airbus H135”,
“Airbus H145”: “Airbus H135”,
“Airbus H135”: “Airbus H135”,
“Airbus Helicopter H135”: “Airbus H135”,
“Airbus H135 Default”: “Airbus H135”,
“BE9L”: “Beechcraft King Air 350i”,
“P68”: “Beechcraft King Air 350i”,
“Diamond DA42 Twin Star”: “Beechcraft King Air 350i”,
“Beech 90 King Air”: “Beechcraft King Air 350i”,
“Beechcraft King Air 350i”: “Beechcraft King Air 350i”,
“Beechcraft King Air 350i Default”: “Beechcraft King Air 350i Asobo”,
“CRJ-1000EL”: “CRJ700ER”,
“CRJX”: “CRJ700ER”,
“CRJ7”: “CRJ700ER”,
“CRJ9”: “CRJ700ER”,
“CRJ700ER”: “CRJ700ER”,
“CRJ700ER Default”: “CRJ550ER Privat D-ALKI”,
“Piper PA-18-150”: “Savage Cub”,
“Savage Cub”: “Savage Cub”,
“Savage Cub Default”: “Asobo Savage Cub”,
“Diamond DA40”: “DA40-NG”,
“DA42”: “DA40-NG”,
“TL30”: “DA40-NG”,
“WT9”: “DA40-NG”,
“DIMO”: “DA40-NG”,
“A210”: “DA40-NG”,
“DV20”: “DA40-NG”,
“SR22”: “DA40-NG”,
“DA40-NG”: “DA40-NG”,
“DA40-NG Default”: “DA40-NG Asobo”,
“GLID”: “Discus-2b”,
“DUOD”: “Discus-2b”,
“VENT”: “Discus-2b”,
“ARCP”: “Discus-2b”,
“Airbus A320 Neo PH”: “Discus-2b”,
“Discus-2b”: “Discus-2b”,
“Discus-2b Default”: “Discus-2b”,
“DR40”: “DR400”,
“Robin DR400/140B”: “DR400”,
“DR400”: “DR400”,
“DR400 Default”: “DR400 Asobo”,
“WHK2”: “white-knight-two”,
“A3DC2A”: “white-knight-two”,
“Scaled 348 "White Knight Two"”: “white-knight-two”,
“white-knight-two”: “white-knight-two”,
“white-knight-two Default”: “white-knight-two”,
“VSS Unity”: “spaceship-two”,
“A19B53”: “spaceship-two”,
“spaceship-two”: “spaceship-two”,
“spaceship-two Default”: “spaceship-two”,
“E190”: “Virtualcol Embraer”,
“E195”: “Virtualcol Embraer”,
“E75L”: “Virtualcol Embraer”,
“Embraer”: “Virtualcol Embraer”,
“Virtualcol Embraer”: “Virtualcol Embraer”,
“Virtualcol Embraer Default”: “Virtualcol Embraer 170 Air France”
}
//How does model matching work? Lets say “Boeing 787-9 Dreamliner” is detected, the modelmatcher will now search for an aircraft with the key: “Boeing 787-9 Dreamliner”, this will return “Boeing 787-10”
//The modelmatcher will now append the livery name, lets say “KLM”, this results in: “Boeing 787-10 KLM”, if this livery is found, it will use this aircraft, if it isn’t, it will fallback to: “Boeing 787-10 Default” (It appends default to the value gotten from the key),
//When getting “Boeing 787-10 Default” it will return “Boeing 787-10 Asobo” and use this aircraft.
//You can also override liveries. If you add “Airbus A320 Neo KLM”: “Airbus A320 Neo KLM PRIDE” It will now override A320 matched planes that have the KLM livery, with the KLM PRIDE livery.

1 Like

Look at my post where I showed my ModelMatching.json file. There you will find Gliders and Helicopters. You don’t have to change the aircraft.cfg files only to look for the given name for that Livery like in the manual described.
Here an example for the Helicopters:
“EC35”: “Airbus H135”,
“EC30”: “Airbus H135”,
“EC75”: “Airbus H135”,
“EC45”: “Airbus H135”,
“BK17”: “Airbus H135”,
“B407”: “Airbus H135”,
“H269”: “Airbus H135”,
“H500”: “Airbus H135”,
“R44”: “Airbus H135”,
“S76”: “Airbus H135”,
“S92”: “Airbus H135”,
“G2CA”: “Airbus H135”,
“A169”: “Airbus H135”,
“A109”: “Airbus H135”,
“A139”: “Airbus H135”,
“AS32”: “Airbus H135”,
“AS65”: “Airbus H135”,
“R66”: “Airbus H135”,
“Airbus H145”: “Airbus H135”,
“Airbus H135”: “Airbus H135”,
“Airbus Helicopter H135”: “Airbus H135”,
“Airbus H135 Default”: “Airbus H135”,

Here for the Gliders:
“Discus-2b”: “Discus-2b”,
“Discus-2b Default”: “Discus-2b”,
“DR40”: “DR400”,
“Robin DR400/140B”: “DR400”,
“DR400”: “DR400”,
“DR400 Default”: “DR400 Asobo”,

2 Likes

Can you elaborate on the P2A comment about near traffic being informed by P2A?

I just tried ELT for the first time and was thrilled to find I could finally get GA traffic at KSQL and KPAO which are usually jam packed with busy patterns from the schools.

Will P2A handle ATC comms with that GA traffic?

Separately, is the recommendation to use FSLTL in conjunction with ELT if people want the model matching and taxiing for IFR aircraft with flight plans filed? I’m struggling to pick apart the use cases for when I want one vs. the other vs. both.

I’d love KSFO, KSJC, and KOAK traffic to be alive and busy like IRL, but my main concern is busy GA airports.

Also, feature request for the future, but even if there was a 1d snapshot or something, I’d LOVE LOVE LOVE the ability to fast forward or rewind based on the time selected in the sim. I often can only fly at night once VFR GA traffic is done for the day, and wish I coudl simply replay the traffic from earlier in the day to keep it busy.

  • You can mix FSLTL with ELT. Exclude Airliners in ELT and set GA traffic in FSLTL to 0. FSLTL wil manage the IFR traffic with the planes with a flight plan - ELT will manage the GA traffic.

  • P2A will warn you for the close traffic if you requested a VFR flight following before. From this moment you will get close traffic warnings. But you will get no close traffic warnings on the ground.

  • My hint - if you want the most realistic ATC feeling then use Live ATC for the normal traffic communication and P2A will give you your close traffic warnings. More realistic is not possible (@ the moment
) :wink:

1 Like

The feature that you want is a bit complicated. ELT is using the live data’s from FR24. They are free. Records from the past are chargeable. So I think that will not happen in the next time
 Sorry!

Hi,i have a question,why even if i removed airline from the list in ELT i steel see them(only ga traffic i activeted)with FSLT.