7 minutes ago, Noel said:

My sim is totally smooth as it has been, but AI traffic from BATC is not. I'm using DLSS FG and the native rate is set at 30, so 60 FPS-FG.  Someone on their discord said I should move the BATC rate to 30 to match that, and that made the AI traffic worse.  From what I gather BATC's traffic runs outside MSFS so what exactly are you suggesting when you say, "can't be any smoother than the sim"?   Others have said a recent update to BATC brought AI traffic stuttering.  Is that not your experience?

I mean to try DX11 for BATC to see if somehow that makes a diff so will next time up.
 

It's technically impossible that your sim runs at 30 FPS and you inject an object into the sim that runs at e.g. 90 FPS. That's not possible. The limit will always be the sim FPS, because the sim also renders the injected object.

1 hour ago, V1ROTA7E said:

 

You guys need to go into BATC settings and select a higher FPS from the dropdown menu. I’ve got mine set to 90, and traffic moves very smoothly. I had it set to 30, but it looked like you described. Haven’t tried higher values, and I’m not sure if it hurts overall sim performance. 

Ok. Will try that. Thanks. I've set it to 30 indeed, due using VR. Will try 45 and 60 as well. 45 would be 50% HMD VR refresh rate. 

3 minutes ago, Fiorentoni said:

It's technically impossible that your sim runs at 30 FPS and you inject an object into the sim that runs at e.g. 90 FPS. That's not possible. The limit will always be the sim FPS, because the sim also renders the injected object.

Hmmm.....could this mean that the stuttering AI object are asynchronous fps related....?

At my end the sim is running 45 or 30 (VR related Varjo settings with capped FPS at 45 or if not possible 30).

And I have set BATC to 30 and also tried 45, but maybe not long enough tested this one. 

I will play around with all those settings. 

Thanks for the heads up

56 minutes ago, mpo910 said:

Hmmm.....could this mean that the stuttering AI object are asynchronous fps related....?

Okay I see what's been happening hwew, why it's true for some and not for others as well perhaps.

I just started committing to using DLSS FG because I am poorly tolerant of the strobing I get during taxi, and because of the screen judder that happens when I move from my second screen to the main MSFS display.  I've learned that it becomes tolerable if I sacrifice a wee bit (fortunately) of image quality but also this: if I remove my 60fps-fg frame lock and let it run wide open the strobing I see diminishes by a good 60%.   So this has been my habit, to run wide open from gate to initial climb, then from landing to gate.  Otherwise it stays locked at 60 fps-fg.  As well, if the native is rate is pretty decent (say 40+) I can simply make screen #2 the focus at which point FG stops on the main, and strobing disappears.  Anyway, those are easy workarounds.  But...............here's the thing:

I noticed just now at KSMF with a fair amount active traffic on the ground and in the air if I hit the keypress to resume the lock at 60fps-fg the AI traffic stuttering stops.  So really this was a side effect of my practice to not lock the rate during taxi to diminish some of the FG associated graphic anomalies I really don't want to see.  So good news:  if keep BATC fps and sim fps locked at the same value the stuttering diminishes greatly.  Not certain how well this will hold up as it's only been one test but looked very obvious what was happening.  What's not quite clear is simply this:  BATC has its own frame rate lock, while MSFS has a different one.  So why would they be truly in sync?  Something to do w/ clocks perhaps?  

I'll be landing at KEUG in a few so will see if this theory holds up!

Edited January 22, 20251 yr by Noel

1 hour ago, Noel said:

It absolutely eats into frame rate ramping up BATC's frame rate.  I tried this tact to help fix the stuttering AI traffic (never happened in FSLTL) and realized because of the substantial hit on sim frame rate ended up returning to 60fps.  IMPORTANT:  several people (on their Discord) have stated this issue began with the most recent update to BATC which suggests a change made brought this about for some if not most users.  So time to put AI traffic on ignore (i.e., stop focusing on it!) until BATC devs acknowledge and address this.

I'm doing a test right now swapping between 30 and 120. I'm noticing a 3 FPS difference between 30 and 120, but the animation quality is substantially better with 120....regardless of in game FPS. I'm willing to take the 3 FPS loss.

20 minutes ago, V1ROTA7E said:

I'm doing a test right now swapping between 30 and 120. I'm noticing a 3 FPS difference between 30 and 120, but the animation quality is substantially better with 120....regardless of in game FPS. I'm willing to take the 3 FPS loss.

That's drastically different story than I experienced.  Of note, it took a little time for this to manifest but clearly the impact was huge, maybe around 30% hit on frame rate while at the 120fps setting and I remember 90 was intermediate between 60 and 120.  Maybe the cause of this was something else, so I'll try it again since you're seeing something different.  

I just switched to 120 in mid cruise.  After landing it will be interesting to see if the mismatch in sync (120fps in BATC v 60-100 in sim) worsens AI traffic stutters, nor not.  Up in the air now the FPS-FG impact was very small, around 2-4%.  We'll see how that translates in heavy traffic at a busy airport.  KEUG is not that airport!

Woah!  Turns out RTSS' frame lock is locking BATC as well which I just noticed.  That means even with BATC set at 120 it will sync to sim when the frame lock is ON.  It will be interesting to see if unlocked BATC's 120 rate improves AI traffic animation when the sim is unlocked, that will be a new finding.

Edited January 22, 20251 yr by Noel

18 minutes ago, Noel said:

Woah!  Turns out RTSS' frame lock is locking BATC as well which I just noticed.  That means even with BATC set at 120 it will sync to sim when the frame lock is ON.  It will be interesting to see if unlocked BATC's 120 rate improves AI traffic animation when the sim is unlocked, that will be a new finding.

That's interesting, let us know.

I also just learned that FSLTL performs SIGNIFICANTLY better. I was getting ~36 FPS at a gate in Sydney with BATC at 5 with AIG as the primary traffic. Now I'm getting 50 with traffic in this order 1) FSLTL 2) FSTraffic 3) AIG

6 hours ago, V1ROTA7E said:

That's interesting, let us know.

It's not so straightforward, which of course it rarely is in this business!  Here's what I think is happening.  If you set BATC's rate to 120 it will do 120 to the extent you're NOT becoming GPU limited at which point you will see BATC's fps indicator starts dropping and fluctuating.  I thought from one test that keeping the frame lock at my preferred 60FPS-fg reduced traffic stuttering, but that was not the case on the second test scenario, and maybe the above described issue was at play not sure.

I found that for me the smoothest setting is 120 FPS in BATC. I use AutoFPS to keep min. 30 native FPS, RTSS locked to max. 50 native and use LSFG x3 with a Gsync monitor. That way I always get 90-150 FPS on the screen (30-50 native) even at EGLL with BATC traffic at 7.

I tested 30 FPS in BATC (matching with a pretty constant native 30 FPS parked up at EGLL) but that was a stuttery mess, even when I ran a test without any locking or LSFG frame gen, so just native 30 and BATC 30. The other settings also looked stuttery but at 120 it's really nice and smooth. I don't notice any performance impact from 120 over 30, 60 or any other setting.

Even at 120 I still get some "warping", i.e. aircraft that have just landed and are slowing down on the runway suddenly warp forward a bit...but that's not the same as the stuttering I see at lower FPS that looks more glitchy, it's a different effect that seems to be present with all FPS settings. My advice would be to just try all the FPS settings and see what works best for your setup.

No stuttering with traffic for me today, and thats without fiddling with any settings. My FPS setting is set to 60 (which is recommended in the app).

I'm having more serious issues though, so much so that it feels like the app is broken. Constant "Generating Speech" wheel stuck in a loop. Disconnections from the sim. ATC chatter talking over each other, full sentences not being completed beacuse ATC just cuts over the top of them and vice versa. This all happens before the speech wheel gets stuck and I have to reset the app. On a small hop from EIDW to EHAM today I had to reset 7 times and in the end I just let it stick in its continuous loop when on approach just so I could see some planes on the ground.

The latest updates seemed to have messed up my install maybe? Tempted to reinstall unless these are known issues? As yet I've had zero replies in the discord and I've posted my logs.

Edited January 23, 20251 yr by El Diablito

2 hours ago, El Diablito said:

Tempted to reinstall unless these are known issues?

Def reinstall I've done it with no issues.  

Someone on Discord mentioned you can exclude an .exe with RTSS which I've never done.  So I did this and discovered yes, it excludes BATC from the frame lock I use.  From there we went to KDEN and watched a fair amount of landings and taxi.  I tested with BATC at 120fps, and at 60fps, with MSFS locked at 60FPS-fg:  with this one test session 60fps was the best option, so both sim and BATC were running at 60FPS-fg and I saw very little stutter of AI traffic so this is looking hopeful. 
 

7 hours ago, El Diablito said:

No stuttering with traffic for me today, and thats without fiddling with any settings

And because of exactly that....I'm not going conclude anything yet based on one test!  Other factors may be at play.

On 1/22/2025 at 7:00 PM, Noel said:

Turns out RTSS' frame lock is locking BATC as well which I just noticed.  That means even with BATC set at 120 it will sync to sim when the frame lock is ON.

Could you please elaborate on how you noticed this? I’ve set BATC to 60 FPS and locked sim FPS to 62.

On 1/23/2025 at 2:30 AM, Noel said:

If you set BATC's rate to 120 it will do 120 to the extent you're NOT becoming GPU limited at which point you will see BATC's fps indicator starts dropping and fluctuating.

Where do you see BATC’s fps indicator?

Edited January 26, 20251 yr by Cpt_Piett

On 1/23/2025 at 9:46 AM, El Diablito said:

I'm having more serious issues though, so much so that it feels like the app is broken. Constant "Generating Speech" wheel stuck in a loop. Disconnections from the sim. ATC chatter talking over each other, full sentences not being completed beacuse ATC just cuts over the top of them and vice versa. This all happens before the speech wheel gets stuck and I have to reset the app. On a small hop from EIDW to EHAM today I had to reset 7 times and in the end I just let it stick in its continuous loop when on approach just so I could see some planes on the ground.

I’m having similar issues but I’m using the Experimental branch with the LLM so assumed it’s just beta bugginess. 
 

Are you seeing this on the stable branch? 

1 hour ago, Cpt_Piett said:

Could you please elaborate on how you noticed this? I’ve set BATC to 60 FPS and locked sim FPS to 62.

Where do you see BATC’s fps indicator?

If you don't create an exclusion in RTSS for BATC then RTSS limits MSFS & BATC.  You will see the switch to turn on FPS indicator in BATC settings, and it will display in the lower right corner of BATC. 

I'm having the best behavior by locking BATC at 60fps per their recommendation, excluding BATC from RTSS, and using my standard 60FPS.  This gets rid of jerky AI traffic, thankfully.  I was about to bail on BATC and try FSHud because of that.  Now AI traffic is smooth, like it was with FSLTL.  I'm told it's having both at identical fps is the key to that.  Theoretically you could try not excluding BATC from RTSS, then set BATC's internal lock at a value over 60, then set your sim at 62fps.  I think RTSS will then lock both at 62 and you can check that with BATC's indicator of course.  But I'm not sure you'll get the same quality of smooth.