Worth a quick read of this page that explains the limitations/known issues:
https://www.fslivetrafficliveries.com/user-guide/
These are the most interesting parts:
Scope of Injector Input
- The injector reads real-time data of aircraft location/type/departure/destination. NOTE: there is around a 30-second delay in this data.
- You will get a lot more traffic than Asobo live traffic, just be mindful that this may affect performance. However, so far performance does appear good with the latest native models.
- Flights are point to point when not using the FlightPlannerDB option
- Example result: Origin airport to destination airport, linked to MSFS ATC so you will hear them communicate with ATC. ATC will control the take-off and landing of each flight.
- We use SimConnect from Asobo which is still being improved. There are known issues with the API, and you might see crazy flight behavior from some aircraft on occasion.
- Once inserted into the sim, the injector no longer controls the movement of the aircraft - this is purely handled by MSFS. This is why ATC, TCAS, and other components know all details about aircraft.
- Aircraft are actively removed that move out of range (around 200km) from the user’s plane.
- Injector removes aircraft that go around due to MSFS bug that they will then continue to circle forever. They are not removed immediately but after around 60 seconds when some distance away from the airport (to prevent immersion breaking of vanishing aircraft). They will then typically be parked at the destination airport a short time later assuming parking is available.
- If enabled in settings the injector does insert static aircraft at airports based on real-world data collected over several months. The insertion is based on the percentage chance of seeing a livery/model combination at the real airport.
- FSLTL injector tries to keep things moving at airports by culling aircraft that get stuck while taxing, we do this more aggressively than the default Asobo time frame.
Known MSFS AI Limitations & Behaviors
A number of AI limitations and traffic behaviors exist in the sim which affects all AI solutions including FSLTL. These issues require fixes from Asobo which we hope to see in the future. If you wish to upvote the issue, then you can do so via the MSFS forums here.
The known issues are:
- Aircraft spinning on taxiways where path is blocked.
- Wrong runway assignments for given Metar.
- Runway incursions and high go-around - MSFS ATC limitation
- Slow runway exit speeds
- Parking at wrong terminals - limitation of some scenery design, required dev implementation
- Aircraft labels not supported currently
Please also note that when the injector reads real-time data of aircraft location / type / departure / destination, there is around 30-second delay in this data, along with additional delays due to MSFS inputs. Positioning won’t be 100% accurate but will be very close to real-life.