Yeah whatever works for you, but it always involves worst case airports and dialing settings back to accommodate a tolerable fps with ai. Ini’s KJFK isn’t bad for me but I remove all unnecessary stuff especially extra gate equipment / clutter (i let gsx do this populate instead). I refuse to turnnoff the nice interiors, people and the amazing train at KJFK as it is so stunning. They did a great job with it.
At KJFK, your TLOD will be an issue with manhattan close by. TLOD is one sacrifice I make to accommodate AI though. ( but definitely not the only one, there’s a lot to be had performance wise out of dialing back shadows for example). There is a great video on fsltl/sim optimisation I posted (probably further up on this thread).
One thing to keep in mind is a lot of airline flights, are also listed as VFR flights. A lot of Air Canada flights, out my way here in Canada, come up as VFR out of Pearson or Ottawa.
No, it means that in addition to the live airliners at a given airport (which are limited to 55), you are getting a further 10 static aircraft that are there for window-dressing purposes only.
Static traffic do nothing but fill the airport out with static aircraft. It is the IFR traffic that drives most of the FPS issues. IFR traffic spawns and arrives at gates too and is also responsible for making the airport look busy. Not saying static doesn’t at all hit perf at all, but it’s not as big a deal as having too much IFR traffic would be. Static aircraft do however jam up gates so they can’t be used by yourself or other AI, so best to keep the value low.
Fidling my graphics i had no clue i had FSLTL on anymore. I play on a laptop with an Nvideo GeForce GTX 1950Ti.
I always make LA or NY benchmarks when testing stuff.
I was wondering why my FPS didnt reach more then 15 above LA and not over 10 (unplayable) at LAX with graphic setting to medium.
Then i saw and disconnected FSLTL and my FPS went straight to 25/26, which is great for LAX with this graphics card. And it was playable.
I know i have a lower end graphics card and playing the sim on a laptop (more a work/travel man then having a rigg at home) but graphic/speedwise it is getting less easy to maintain the same as when MSFS2020 started. LSLTL is great and with some airliners it also does work normal, but losing 15 or more FPS is significant, especially for laptop users.
So I had an occasion where I wasn’t getting any ATC voices. None, nada whatsoever. I got the texts but no voices. Everything in sounds and traffic etc was correctly set. So trying to narrow things down, I decided to move the FSLTL folders out of the community folder and start the sim again and guess what? The voices were working correctly again. Thought something might be amiss in the cfg file so I deleted that whole folder in the appdata folder, moved the FSLTL folders back in the community folder and ran the sim again with the default FSLTL settings. Still no voices. Hmmm? Opened up the FBW installer and it said the injector was up to date. So decided to uninstall the traffic injector in the FBW installer, and then reinstall it again. Run the sim. Gues what? The voices are working again. Somehow the injector files got corrupted (I’m guessing} and the installer thought everything was ok and up to date. Just thought someone might want to know.
So if I start at the gate and start FSLTL, everyone wants to get clearance at the same time. 10 or more planes wanting to leave at the same time. How to stop this?
I’ve been actually not starting it until I’ve pushed back. Don’t want to be number 7 in line for take off. It’s too bad they haven’t fixed it because it really kills the immersion. But hey, it’s freeware. What are ya gonna do lol
This hasn’t been much of a problem for me. I think it’s a combination of having settings low in part to avoid excessive radio chatter/backups, and things tend to naturally smooth out while I’m setting up my flight plan in the FMS.
It’s annoying for sure. No FSLTL setting as far as I can see to limit this (probably governed by in sim AI logic after AI injected by FSLTL though). I often hit ‘reset traffic’ in the in game FSLTL panel to either get an word in to ATC for clearance or to remove 10 stacked aircraft at the departure runway. Which is a bit immersion breaking.
There is a method to limit the AI rush using AIGround (a separate program). From its documentation-
AIGround holds the AI stationary on the tarmac after pushback for a more realistic amount of time
before the AI begins its taxi out.
AI can optionally be released after pushback at a specified rate using the AIDepFlowLimiter. This option
is useful to avoid a “rush” of AI taxiing out when an airport scenery is first loaded.
and
Taxi-Out Rate Limiter
AIDepFlowLimiter Default 0 (Disabled). When set to a number (integers only), the taxi-out rate limiter is
enabled. The integer number of AI will be allowed to taxi-out after pushback every 3 minutes (on
average). For example, AIDepFlowLimiter= 2 means that 2 AI will be allowed to taxi out every 3 minutes
on average. If the user increases the default AIGround monitoring area (see config section below), this
rate will be enforced individually at each monitored airport. Useful to avoid a “rush” of AI taxiing out
when an airport scenery is first loaded.
