I have the latest version of FSLTL but I had not appreciated the new separation option.  It certainly did not jump out at me as something new on the in sim toolbar options.  I was shocked to see an update log shared in this thread which said:

FSLTL Injector 1.6.0:

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.

I have both FSLTL and AIG injectors associated files installed but only run one injector at a time, with the other entirely disabled via MSFS Addon Linker.  Despite having SU13 installed the AIG landing traffic still land half way down the runway.  They are fine with FSLTL.  I assumed the bug still existed in MSFS.  I wonder why AIG does not seem to work?

Like others I was using AI Flow and AI Ground, with the latter I added a higher time value to the takeoff role as some airlines left the ground after a quarter of the runway, which was very unrealistic.

 

New update to AI Ground today on flightsim.to. I won't get a chance to test until later in the weekend but it might include a fix for the "dreaded" EIDW bug.

New for version 2.15:  The user can specify up to two runways for the AI to takeoff from (force taxi out mode).  One airport (ICAO) max active at a time. Rudimentary taxi out service for departing AI will then be provided. The user can also control whether the AI uses the full length of the runway for the takeoff roll or a shortened length (e.g., taking off from KORD taxiway “TT” for 27L and “N5” for 28R).

Posting again the FSLTL dev's warning for those that didn't see it:

Quote

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 'unsurpported'.

 

14 minutes ago, Alvega said:

Posting again the FSLTL dev's warning for those that didn't see it:

 

Yes, as soon as the injector module opens you just toggle the separation option to off and it is saved for every flight.

9 minutes ago, El Diablito said:

Yes, as soon as the injector module opens you just toggle the separation option to off and it is saved for every flight.

I uninstalled AI Ground and AI Flow and I'm just using FSLTL with separation, as the FSLTL devs recommended. Two less mods that I need to keep updating. But if someone thinks they still need them, then they should disable the separation in FSLTL.

Edited October 20, 20232 yr by Alvega

1 hour ago, El Diablito said:

New update to AI Ground today on flightsim.to. I won't get a chance to test until later in the weekend but it might include a fix for the "dreaded" EIDW bug.

New for version 2.15:  The user can specify up to two runways for the AI to takeoff from (force taxi out mode).  One airport (ICAO) max active at a time. Rudimentary taxi out service for departing AI will then be provided. The user can also control whether the AI uses the full length of the runway for the takeoff roll or a shortened length (e.g., taking off from KORD taxiway “TT” for 27L and “N5” for 28R).

Amazing I just may give it another go

1 hour ago, Alvega said:

I'm just using FSLTL with separation

Do you get realistic take off and landing rolls? as opposed to the 5 second take off roll it had previously. Seeing a heavy take off in the same timeframe as an ATR was a bit jarring.

If that's been fixed I could see myself using it rather than have the extra app open when flying.

28 minutes ago, El Diablito said:

Do you get realistic take off and landing rolls? as opposed to the 5 second take off roll it had previously. Seeing a heavy take off in the same timeframe as an ATR was a bit jarring.

If that's been fixed I could see myself using it rather than have the extra app open when flying.

AITakeoffTargetTime=0 to disable AI takeoff target time.

AILandingTargetTime=0 to disable AI landing target time.

If you do want to use the target times, there is an AIHeavyRollOutExtraTime value to add extra time for AI "heavy" rolls. 

14 minutes ago, Clipper Ocean Spray said:

AITakeoffTargetTime=0 to disable AI takeoff target time.

AILandingTargetTime=0 to disable AI landing target time.

If you do want to use the target times, there is an AIHeavyRollOutExtraTime value to add extra time for AI "heavy" rolls. 

I've already tweaked AI Ground to make the rolls more realistic, I'm just wondering does the new FSLTL update improve rolls in the sim on top of the separation because as far as I'm aware it can't do that.

2 hours ago, Alvega said:

Posting again the FSLTL dev's warning for those that didn't see it:

 

It is also possible to leave separation on in FSLTL and turn if off in AIFlow.  In the AIFlow.ini :   

AIArrivalSpacing=0

AITerminalAreaMinSpeed=0  //this is also used to enforce a speed range in the pattern even if AIArrivalSpacing=0, so make sure to turn this off too as it will affect FSLTL's spacing.

AITerminalAreaMaxSpeed=0 //this is also used to enforce a speed range in the pattern even if AIArrivalSpacing=0, so make sure to turn this off too as it will affect FSLTL's spacing.

I would also probably avoid any AIFlow forced landing modes, which shouldn't be that big of an issue because FSLTL separation will minimize go-arounds.

1 hour ago, blueshark747 said:

Amazing I just may give it another go

Same, do we just use default settings with fsltl? Last time I used it, along with aiflow, it kept loosing connection to MSFS 

You can use it without AI Flow 👍

edit: assuming you're using AI ground, pardon me

Edited October 20, 20232 yr by El Diablito

4 minutes ago, Clipper Ocean Spray said:

I would also probably avoid any AIFlow forced landing modes, which shouldn't be that big of an issue because FSLTL separation will minimize go-arounds

I had stopped using AI Flow with FSLTL due to the way it 'stair-steps' aircraft down on final.  Is there a way to smooth that out or prevent it?  I may go back to using these with the new feature of being able to select runways.

Edited October 20, 20232 yr by Flic1

17 minutes ago, Flic1 said:

I had stopped using AI Flow with FSLTL due to the way it 'stair-steps' aircraft down on final.  Is there a way to smooth that out or prevent it?  I may go back to using these with the new feature of being able to select runways.

That's an AIFlow force landing mode, which are default off.  I think with FSLTL separation, there should be less go arounds and thus less need for force landing mode unless you want to use a custom approach (KDCA river visual 19) or something.  Re: stair-stepping, yes, I need to revisit that as I found a better method working on AIGround that can be rolled into AIFlow.

Re: selecting departure runways, that's AIGround and it is in an initial, very rudimentary phase and it doesn't support heavy traffic densities that well.  Sort of like a "plan B" ATM if, for example, MSFS is stuck on making poor departure runway choices at at your dep/arrival airports based on live weather.

Edited October 20, 20232 yr by Clipper Ocean Spray

24 minutes ago, El Diablito said:

You can use it without AI Flow 👍

Yes, definitely so.  🙂  Also, AIFlow (and AIGround) is a suite of packaged utilities that can be individually turned on/off.  For example, if you only like the user aircraft-AI separation feature in AIFlow, everything else can be turned off including AI-AI separation although it takes some digging through AIFlow.ini, which isn't the most user-friendly.