I prob should try a couple more flights but wow, I tried something in my current flight that solved 3 questions:

1.  How can I get rid of the stuttery AI traffic in BATC?  I've tried so many things, locking BATC's internal FPS to 60, 90, 120, etc along w/ sim at 60FPS-fg, or sim unlocked, all to no avail.  Maybe 5-10% of my encounters with AI traffic in the air or on the ground were decent but the rest were very choppy and stuttery and unacceptable.

2.  How can I minimize artifact, especially strobing/flickering on tarmac, associated with NV Frame Gen?  I've struggled with this because for sure there is benefit in running a low native rate and doubling it, but the artifacts often are impossible to ignore for me so I use various tricks to cope.

3.  Is DLSS4 really the best path performance-wise for how I'm setup?  I've used no FG since I built this machine last spring, far preferring TAA w/ native rate locked at 45 while on the ground.  Adding BATC along with Self Loading Cargo made this no longer sustainable, so I've tried to commit to using Frame Gen.

And here is the stone:

Use BATC for ATC, but don't use their injector, use FSLTL's instead.

This immediately fixed the stuttery AI aircraft.  I remembered prior to BATC I never noticed any stuttering w/ FSLTL alone, so we're fully back to that.  DLSS4 with NVSR + DLAA in-sim has image quality now on a par with TAA as I'm setup w/ added sharpening using AMD FX at 200, GFE Details Filter at max sharp & clarity.  Now, at KDEN in the PMDG 738 at the gate and with engines running hitting 108-115FPS-fg.  Again, that's with BATC, GSX and SLC running.  And that is a major increase over BATC w/ its traffic injector operative and with the same amount of AI traffic.  In fact I got such a bump in headroom GSX PAX caused no issues with dropping rate enough mess up panning during PAX loading which it clearly was doing before this move because I simply did not have the headroom.

What's great is having an unlocked rate that high really softens/nearly eliminates the strobe/flicker I find unacceptable.  When we stopped at Rwy 17L to watch a plane come in and then for me to TO I decided to flip to TAA, instead of NVSR + DLAA:  the unlocked fps went from 104 to 74!  Yikes!  So yeah, NVSR + DLAA using DLSS4 is a huge perf boost with little to no IQ impact.  Ghosting/smearing characters in glass cockpits are not as good as with TAA but they're not bad now.

ATC still works fine to control your aircraft despite not having BATC's injector, but you do lose hearing communication between controllers and other aircraft.  For that we're now back to LiveATC for ambience.  I actually had more trouble with BATC in some ways as a plane would stop in front of me such that I had to use their traffic removal tool to remove it, or just run thru it.

 

Edited February 3, 20251 yr by Noel

1 hour ago, Noel said:

Use BATC for ATC, but don't use their injector, use FSLTL's instead.

I didnt even know that this was a thing! So you can start FSLTL and BATC will use it for traffic instead of its own injector?

This would be a great help to me as I have noticed that BATC is destroying my FPS as of the last update.

Edited February 3, 20251 yr by Vel

7 minutes ago, Vel said:

I didnt even know that this was a thing! So you can start FSLTL and BATC will use it for traffic instead of its own injector?

This would be a great help to me as I have noticed that BATC is destroying my FPS as of the last update.

No, BATC needs to inject traffic to be able to control it. If you run FSLTL you'll be on your own and BATC won't know what traffic is there. It sounds like the OP is happy with his new configuration but for me it defeats the purpose of having ATC with traffic control in the first place.

1 minute ago, Speedbird 217 said:

No, BATC needs to inject traffic to be able to control it. If you run FSLTL you'll be on your own and BATC won't know what traffic is there. It sounds like the OP is happy with his new configuration but for me it defeats the purpose of having ATC with traffic control in the first place.

It's a compromise for sure for me, but yes it's actually more preferred here to have that kind of perf boost and just let the traffic control itself as it were.  After all that is what I was doing previously pre BATC.   Density is low enough to where I don't have conflicts per se but I do appreciate fully what you're saying.  Hopefully this will tie me over until either BATC at a minimum fixes its stuttering AI traffic and hopefully improves the perf cost a bit.  It's possible ATC will be upgraded by MS/A some day as well and I would expect that to have a very low perf cost.

16 minutes ago, Speedbird 217 said:

No, BATC needs to inject traffic to be able to control it. If you run FSLTL you'll be on your own and BATC won't know what traffic is there. It sounds like the OP is happy with his new configuration but for me it defeats the purpose of having ATC with traffic control in the first place.

It's that way, period

On 2/3/2025 at 3:13 PM, Vel said:

I didnt even know that this was a thing! So you can start FSLTL and BATC will use it for traffic instead of its own injector?

This would be a great help to me as I have noticed that BATC is destroying my FPS as of the last update.

You can absolutely use FSLTL's injector and BATC for ATC of your plane.  You will lose having BATC manage traffic but in the end I'd far rather pick up the performance and ultra smooth animation using FSLTL's injector.  In fact I have far more traffic now and far less performance burden.