I think I’ll try this, I’ve just been using traffic in the sim. What settings do we have to enable/disable in sim for this? 

The injector 'works' but did not help the performance impact and may have made it worse too early to be sure.  But just landed at KSFO and frames dropped to 27-29 w/ stuttering (on my Gsync display), unlocked.  Stopped FSLTL and within 60 seconds back up to 39-40FPS so that is a wretched 25% or worse impact.  And that is with IFR and VFR counts to 6 maximum.  Not ready for prime time currently.

5 minutes ago, Noel said:

And that is with IFR and VFR counts to 6 maximum.  Not ready for prime time currently.

 Around the Bay area though, it's going to be busy. How many ai were in the bubble (not just what you see)? What about parked aircraft, what is that set to?

  

36 minutes ago, Dave_YVR said:

 Around the Bay area though, it's going to be busy. How many ai were in the bubble (not just what you see)? What about parked aircraft, what is that set to?

  

Doesn't matter Dave--the performance impact is too big.  As I said from stuttering 27-29 to nearly 40 by shutting it down.  If you can't use a limiter to attenuate this--it's not ready for prime time.

I might add I wonder just how much are the parked models over live traffic.  Do we have any sense of this?  I was using Simple Traffic previously and it must have had the same impact as default which was minimal. 

Edited December 2, 20223 yr by Noel

@Noel  If nVidia, what version video drivers are you on? I'm on 526.98. There's a new version out but I'm scared to update as these are the best graphics I've had with MSFS hands down. It was an extremely noticeable difference in FPS and looks from the previous drivers which seemed like the worst msfs nVidia experience I have ever had. Up until now I have always updated to the latest drivers.

The reason I bring this up is it just might just be the graphics drivers you are on.

It's really so hard to nail down exactly what causes what.  Even in your driver example you mention 'an extremely noticeable diff...FPS...' it is so hard to say for sure it wasn't something w/ the prior driver install and any new install would have been responsible for the improvement or what have you.  I've done so much troubleshooting lately I've become aware of just how difficult it is to have certainty.  In general I try to avoid driver changes and right now I also have had best ever performance and stability, and currently am using 526.86.  The only real change here was the new Injector and prior to that it was quite serviceable.  It's too early to be sure, once again!  I don't mind trying the driver you're on who knows I'm doubtful it's an issue as I have fabulous performance w/o FSLTL.

1 hour ago, Ianrivaldosmith said:

I think I’ll try this, I’ve just been using traffic in the sim. What settings do we have to enable/disable in sim for this? 

Just turn off traffic in-sim, and after you have installed FSLTL via the FlyByWire Installer then launch FSLTL a console will popup asking you if you want to modify certain parameters and go from there.

9 minutes ago, Noel said:

Just turn off traffic in-sim, and after you have installed FSLTL via the FlyByWire Installer then launch FSLTL a console will popup asking you if you want to modify certain parameters and go from there.

Does parked ground traffic need to be at 0?

1 hour ago, Noel said:

The injector 'works' but did not help the performance impact and may have made it worse too early to be sure.  But just landed at KSFO and frames dropped to 27-29 w/ stuttering (on my Gsync display), unlocked.  Stopped FSLTL and within 60 seconds back up to 39-40FPS so that is a wretched 25% or worse impact.  And that is with IFR and VFR counts to 6 maximum.  Not ready for prime time currently.

The update was actually working pretty well for me but everything in the sim was a stutter fest.

I really think there is something else wrong with Asobo's sim.

23 minutes ago, Noel said:

console will popup asking you if you want to modify certain parameters and go from there

Or you just type n in the console and then set your settings in-sim using the sliders in the FSLTL menu, accessible from mouse-over on-screen menu after you loaded a flight

51 minutes ago, Ianrivaldosmith said:

Does parked ground traffic need to be at 0?

Any aircraft type traffic needs to be off in-sim as FSLTL will deliver its own and you will have some control over it from within FSLTL's in-sim Phil mentions, or when FSLTL launches its console you can set your initial values.  It's not entirely clear to me how the limits work.

4 hours ago, Noel said:

Doesn't matter Dave--the performance impact is too big. 

 Yes, of course it matters.. Set it up for what you require from your system. Even IFR at 6 with NO VFR and NO parked traffic, at SFO I get over 40 ai in the area. If that is too much of a hit then maybe your settings are too high. For my system, I see maybe a 4-10 fps drop at that setting but that is simply the cost of having good AI. 

I noticed with FSLTL that it loads planes often in batches and I think this can cause stutters. It would help if the injector would pre determine what and when to inject, like 1 plane every 3 secs. And does a internal check also to prevent that planes get injected and shortly after deleted because it injected outside of the set limits, not only once but repeatedly the same plane. Causing double ATC radio transmissions and possibly ATC malfunction also (no controller voices). I have to try the update still yet, maybe things have changed positively.

1 hour ago, Dave_YVR said:

 Yes, of course it matters.. Set it up for what you require from your system. Even IFR at 6 with NO VFR and NO parked traffic, at SFO I get over 40 ai in the area. If that is too much of a hit then maybe your settings are too high. For my system, I see maybe a 4-10 fps drop at that setting but that is simply the cost of having good AI. 

Something's off with it since the new injector is possible.  I see almost no AI and still get substantial impact.  Did not have this issue w/ the more crude option of default w/ ST and of course that is to be expected but for me it's far more objectionable having a stutterfest than seeing the odd pointy nosed simple model which I hardly pay attention to.  You can't ignore stutters they ruin nice landings.  I thought having fine control over numbers I might be able to dial in something useful but again flying into KSFO we're down to a wretched frame rate of 27 so that's off the table.  Again--hardly saw ANY AI traffic and that was the cost.  I'll keep playing with it and hopefully can find some happier medium with it.

14 hours ago, JimBrown said:

Most likely there is an error in the JSON configuration file.

Thanks for the tip!
I already checked that and it was empty. I guess FSLTL also sees that as an error so I will give it a try later this day.