Working great for me so far, some of these features seem similar to AI Ground and Flow, have you guys teamed up?
On another note, Funchal was a nice surprise, AI actually followed the correct path and turned round on the runway to take off as real life. I’m not sure if this is FSLTL magic or whether Asobo have tweaked something in the sim. Same happened at Leeds Bradford, UK. Usually, they’ll just wide taxi onto the grass.
No we just have been working on aspects of injection that felt would beneficial for all. The way we do separation is a bit different and one of our key things was never to break aircraft away from being ATC controlled. The tech stacks of FSLTL and AI Ground / Flow are very different too.
In case people aren’t on the discord (though you really should be if you use FSLTL ) here was the change log for 1.6.0. We also push a patch today 1.6.1 that just resolved some start up issues a few people had.
Improvements
The injector workaround for the long-landing bug introduced in the sim with SU12 is removed, as this has been fixed in SU13 by Asobo.
Separation config setting: ENABLED by default. (Unless you already have this setting in your config file and it’s already set to ‘No’)
Injector handles an approach queue per airport, and as runways are allocated, runway per airport
Reduces speed of following aircraft to maintain reasonable separation of aircraft on approach
Enforces speed rules to AI on final approach, below 4000 ft, to help with seperation
Aircraft holding for departure will continue to hold if any approaching aircraft are on final within 10km of runway
Aircraft holding will also maintain hold until landing aircraft begin braking for runway exit, reducing the chances of aircraft taking off while arriving aircraft are still on the runway
Departing aircraft entering the runway will use higher taxi speeds for runway lineup, speeding up departure significantly
Egress Optimizations: As part of the Separation Control feature, we’ve added egress speed optimizations to assist aircraft in exiting the runway in a timely fashion. You may notice aircraft speed change abruptly as they leave the runway with this turned on.
NOTE: This feature is turned on/off with the Separation Control setting.
The SID/STAR options in the injector console window will now be visible to everyone (ENABLED by default for new installs; existing installs keep previous setting)
VFR: improvements to prevent aircraft that are no longer in FR24 from staying in the sim
AIG Model Fallback: We’ve changed the AIG models the injector might use for fallback, if installed. Previously, the injector would not use FAIB-based AIG models as they used older MDL formats. Now, the injector will only ignore individual models that use the MDL format, instead of a blanket exclude on FAIB-based models.
Matching rules: Will now look for registration matches with AIG liveries in certain scenarios. If the injector is already falling back to AIG models/liveries, the injector will look for a registration match before selecting a matching livery at random
Injector Console Window: To make it easier to find your FSLTL injector log file, the path to the log file will be shown in red text at the top of the injector console window when starting the injector
Injector Log File: rollover will now occur once injector log file has reached 10mb in size (5mb previously)
FSHud Integration Changes:
At the request of FSHud developers, the number of additional parked aircraft has been increased
PLEASE NOTE: For this change to take effect, you will need to delete your current injector config file that is used for FSHud. Once removed, a new FSHud-specific injector config file will automatically be created the next time you start the FSLTL injector with FSHud running.
config file name = “fsltl-trafficinjector-fshud-config.json”
path to the configuration folder is shown near the top of the injector console window.
Bug Fixes
Fixed livery processing issue when atc_id attribute was listed last in a [fltsim] section of aircraft.cfg Known Issues (Approach Separation and Departure Handling):
Aircraft being forced on hold may taxi over the top of each other
Go-arounds are still possible, including when the runway is clear and during runway incursions
Aircraft approach speeds can get unrealistically slow while the injector attempts to create separation
IMPORTANT The separation option is NOT to be used in conjunction with AI Ground / AI Flow / AI Separation. If you want/need to keep using those tools, turn OFF the separation option in the FSLTL injector. They will conflict with each other and lead to less than optimal results. We consider that combination as ‘unsupported’. (edited)
Since i upgraded traffic lands then either stops and sit here or travels very slowly , one plane took 10 mins to exit runway. Now the only thing that has changed is SU13 and my upgrade to 1.6.0 i turned separation off, that was indeed causing planes to stop on runway turning it off planes kept going but were very slow . Tried at 3 different airports with same result. Also an issue i noticed last week unrelated was at JFK fps with FSltl running was around 30 with render latency of around 20 but periodically fps would plummet to 7 and render latency would climb to 200 then it would go back to previous state turning fsltl off stopped it no idea what was causing that.
we had one report of this in testing and no one else could reproduce it.
If you need support - as noted above - come to the discord and raise a support request. Otherwise keeping separation control off is your option for now.
AI Offline (I use 50% for GAmod) in SU13 has improved a bit with cruise altitudes. GA traffic no longer hang low and skim over buildings and powerlines.
Tried the AIGround program with FSLTL separation off and got weird results with GA taxing. @01:25 in the video
Rest of the video is with AI Ground off and these FSLTL settings.
Does the SIDs/STARs feature still depend on Navigraph post SU13?
Exactly what type of traffic should we be seeing with VFR enabled?
Only thing I’ve ever seen with it enabled are those parked LearJet 25 static models.
That’s why I never enable the VFR beta mode with FSLTL.
I have noticed, at least in Canada, that FR24 will have a departure airport listed but no destination airport for most of the GA aircraft. It will automatically assign the departure, even if there is no flight plan. So, will these show up as VFR traffic?
Just had a quick look on FR24 and note quite a lot of traffic has no destination (some no origin either). They’re obviously not IFR but as they are squawking code “C” (altitude info) they’ll be displayed although FR24 does not actually report IFR/VFR status.
Not actually seen anything which could be “VFR” whilst in-sim but I’m currently on a world tour and as most of it is currently during the hours of UTC night time (with the sim time “adjusted” to be daylight) FR24 isn’t reporting much anyway.
This is with FSLTL enabled, including VFR traffic, and Little Navmap set to display traffic from the sim.
This is the most I ever get from these settings with FSLTL only.( All default MSFS ai off)
They never budge, and no GA traffic in air within the entire max 150km range.
So yea I’ll def stick with my 100 IFR FSLTL + 30% Offline GA Traffic GAmod combo for now.
If you want to see any GA traffic at all through the Caribbean Islands and outside the US especially.
First flight since I installed the upgrade. Found that FSLTL wouldn’t populate the airport. The progress stopped at “Loading X number of aircraft”. Typically this is where all the parked and flying aircraft are detailed. Also found that framerates (using the PMDG 737) are horrible on takeoff and landing. No idea if this is related to an FSLTL issue but figured I’d inquire as well. Any thoughts on what is going on?
I found a couple of things were either not working or a bit iffy after SU13, FSLTL being one of them. Sometimes failed to populate even though it appeared to have started normally, just closed then restarted and it worked. But a couple of days and flights later seems okay now although I did see a small update but don’t know if it was anything to do with SU13.
Just installed the latest FSTL patch but now I’m seeing aircraft parked that just don’t belong to the region. For example I’m seeing an Alaska Airlines, Air Lingus and Corsica Airline with types Embraer 195 and ATR 72-600 at King Shaka International Airport, Durban, South Africa which is certainly not correct. Can anyone else confirm this?