7 hours ago, jcomm said:

So, let me see if I did understand:

- You use BATC, but do not enable the traffic component, where the 3d model selection is also set.

- Instead, you start the FSLTL injector, and select from there the 3d models. Do you go with the FSLTL own models or AIG, or a mix?

Is this it?

And if yes, then BATC does not control that traffic?  Is it at least aware of it?

Yep, that's right.  And what's fascinating, not really because I've always used FSLTL, I can't hardly tell.  IOW, I'm not running into traffic or what have you.  I continue to test the stutter and overall performance impact with each update to BATC and one just dropped this morning.

17 hours ago, Bobsk8 said:

I see no performance difference between FSLTL injection and BATC injection, both about the same.

Not here and that of course is going in part to be a function of how the rest of the entire sim is configured.  At the arrival side of a 2h flight it's fairly common to see BATC and its traffic (I'm only set at 2-3 level, similar to you) put up to 33% or even higher.  With FSLTL with similar density it's about half of that.

Today's update didn't improve performance nor stuttering AI traffic.  You won't notice this from a ways away from this traffic but the 738 that just passed in front of me at KORD stuttered 10x in a matter of 15 seconds of taxi.  Performance-wise with roughly equivalent planes the FPS-fg with BATC's traffic was 82.  After killing BATC's traffic and initializing FSLTL FPS-fg was 94.  You're thinking why does that matter?  I depend on high frame rates to deal with FG related aberration while on the ground panning and taxiing so that's part of it but truly, once again, in a doubled blinded test I don't believe most people would notice any issues with FSLTL doing its own management thing after all that's what you did before you used BATC, if you used FSLTL that is.  I certainly appreciate the desirability of having traffic managing ATC that is also managing traffic but the reality is...you hardly notice this if you stop looking for it.  

43 minutes ago, Noel said:

Today's update didn't improve performance nor stuttering AI traffic.  You won't notice this from a ways away from this traffic but the 738 that just passed in front of me at KORD stuttered 10x in a matter of 15 seconds of taxi.  Performance-wise with roughly equivalent planes the FPS-fg with BATC's traffic was 82.  After killing BATC's traffic and initializing FSLTL FPS-fg was 94.  You're thinking why does that matter?  I depend on high frame rates to deal with FG related aberration while on the ground panning and taxiing so that's part of it but truly, once again, in a doubled blinded test I don't believe most people would notice any issues with FSLTL doing its own management thing after all that's what you did before you used BATC, if you used FSLTL that is.  I certainly appreciate the desirability of having traffic managing ATC that is also managing traffic but the reality is...you hardly notice this if you stop looking for it.  

I agree and will surely try it, but when you say:

"I certainly appreciate the desirability of having traffic managing ATC that is also managing traffic but the reality is...you hardly notice this if you stop looking for it.  "

the only problem for me is if the ATC doesn't coordinate that traffic against you, thus giving rise to unwanted scenarios like taxi / lign up and takeoff / final approach, clashes...

Edited February 12, 20251 yr by jcomm

11 minutes ago, jcomm said:

the only problem fo rme is if the ATC doesn't coordinate that traffic with against you, thus giving rise to unwanted scenarios like taxi / lign up and takeoff / final approach, clashes...

Try it my friend I've found more conflict with BATC, believe it or not.  Not alot mind you, but absolutely more.

8 hours ago, Alvega said:

Can you elaborate on the differences you noticed using the different core engines? Did you notice any FPS or GPU usage differences?

Thanks.

OpenGL and DX11 gave me almost identical results, a much smoother AI Aircraft experience. FPS remained at 40/60 FPS and my 3060 runs super cool in any scenario (I'm using the FG and AutoFPS mods)

3 hours ago, Noel said:

Today's update didn't improve performance nor stuttering AI traffic.  You won't notice this from a ways away from this traffic but the 738 that just passed in front of me at KORD stuttered 10x in a matter of 15 seconds of taxi.  Performance-wise with roughly equivalent planes the FPS-fg with BATC's traffic was 82.  After killing BATC's traffic and initializing FSLTL FPS-fg was 94.  You're thinking why does that matter?  I depend on high frame rates to deal with FG related aberration while on the ground panning and taxiing so that's part of it but truly, once again, in a doubled blinded test I don't believe most people would notice any issues with FSLTL doing its own management thing after all that's what you did before you used BATC, if you used FSLTL that is.  I certainly appreciate the desirability of having traffic managing ATC that is also managing traffic but the reality is...you hardly notice this if you stop looking for it.  

I would agree with this, and correct me if I'm wrong, but you also get more consistent AI Aircraft effects like tyre smoke on touchdown and rain mist on takeoff.