58 minutes ago, JonathanC said:

Are you seeing this on the stable branch?

I changed to the stable, still an issue.  so a reinstall might be the way to go.

i see an other problem with Planes wich BATC did insert in the sim. 
after the last update the injected planes did not give any signal to TCAS.
i can see Planes around me, in really near positions, same altitude, but see them not in TCAS?

this did function last week good, but now? any other such thing?

 

Edited January 26, 20251 yr by Alti

9 hours ago, JonathanC said:

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? 

I think I'm on the stable branch, Jon. I did a KSAN to KBOS flight yesterday and it only happened once!  I should add that I did a full reinstall before the flight.

How is the LLM feature working out? I'm not sure how to switch to the experimental branch

Edited January 26, 20251 yr by El Diablito

On 1/22/2025 at 11:19 AM, V1ROTA7E said:

That's interesting, let us know.

There must be other factors at play besides how rates are set.  When I excluded BATC from RTSS, set BATC at 60fps and sim locked at 60fps it appeared decent with regard to AI traffic animation, but this was only on one test flight--the next flight taxiing AI traffic was stuttering again.  So I kept BATC excluded from RTSS, but went back to 120fps in BATC and kept sim at 60fps-FG and for two flights now this appears to be the best config for this issue but this time still only two test flights.  🤞

Cheers

Edited January 26, 20251 yr by Noel

5 hours ago, Noel said:

There must be other factors at play besides how rates are set.  When I excluded BATC from RTSS, set BATC at 60fps and sim locked at 60fps it appeared decent with regard to AI traffic animation, but this was only on one test flight--the next flight taxiing AI traffic was stuttering again.  So I kept BATC excluded from RTSS, but went back to 120fps in BATC and kept sim at 60fps-FG and for two flights now this appears to be the best config for this issue but this time still only two test flights.  🤞

Cheers

Performance decent at FlyTampa's Sydney (3-10-10-10), FG-FPS RTSS-locked to 62, BATC set to 60. AI moved smoothly. I don't understand the concept of excluding BATC from RTSS though - could you elaborate?

Edited January 26, 20251 yr by Cpt_Piett

48 minutes ago, Cpt_Piett said:

Performance decent at FlyTampa's Sydney (3-10-10-10), FG-FPS RTSS-locked to 62, BATC set to 60. AI moved smoothly. I don't understand the concept of excluding BATC from RTSS though - could you elaborate?

One can enter BATC's executable under RTSS Settings, then change its application detection level to None.  This way RTSS will not be able to rate-lock BATC, but still will MSFS which is subsumed under RTSS Global detection level.  You won't notice BATC has been rate-locked until, for example, you see let's say MSFS at 90fps-FG, and set BATC's lock at 120, at which point BATC will drop down to that and so roughly match MSFS rate at that moment and will fluctuate some.  When you exclude BATC this will not happen it will stick to its own rate lock unless that gets jeopardize by CPU/GPU overload.   So far I've had the best luck with AI traffic stutter with BATC at 120 and isolated from MSFS, and leave my MSFS lock at 60fps-FG.     

And this from a monitor on their Discord:

whakamolenzOP — 1/22/25, 7:57 PM

Yep it’s important that you don’t apply any external frame lock to BATC as it can introduce other impacts to its function.

Edited January 26, 20251 yr by Noel

21 minutes ago, Noel said:

One can enter BATC's executable under RTSS Settings, then change its application detection level to None.  This way RTSS will not be able to rate-lock BATC, but still will MSFS which is subsumed under RTSS Global detection level.  You won't notice BATC has been rate-locked until, for example, you see let's say MSFS at 90fps-FG, and set BATC's lock at 120, at which point BATC will drop down to that and so roughly match MSFS rate at that moment and will fluctuate some.  When you exclude BATC this will not happen it will stick to its own rate lock unless that gets jeopardize by CPU/GPU overload.   So far I've had the best luck with AI traffic stutter with BATC at 120 and isolated from MSFS, and leave my MSFS lock at 60fps-FG. 

This sounds very complicated. So to check that I understand: do you recommend setting the BATC lock to 120 and exclude it from RTSS?

2 hours ago, Cpt_Piett said:

This sounds very complicated. So to check that I understand: do you recommend setting the BATC lock to 120 and exclude it from RTSS?

That's the current approach. I say that because there appear to be other factors beyond sync or rate issues that are coming into play.  And is why I am contemplating FSHud, which I think also has a tidier UI in terms of screen real estate.  But so far that setup has been best and I do not see a significant CPU cost for 120fps setting.  Earlier the thread someone mentioned about 3fps difference.  What your sense of the quality of no-cost voices in each if you will?  I read you can speed up or slow down speech which is useful and BATC does not yet do this.

29 minutes ago, Noel said:

And is why I am contemplating FSHud, which I think also has a tidier UI in terms of screen real estate.

It can also be used on a tablet.

30 minutes ago, Noel said:

What your sense of the quality of no-cost voices in each if you will?

IMO FSHud voice quality is on par with BATC standard voices (but less regional accents).

31 minutes ago, Noel said:

I read you can speed up or slow down speech which is useful and BATC does not yet do this.

Correct.

Here, BATC's traffic injector/manager has a ways to go.  After lots of stuttering traffic I've had better animation just last night and maybe the update that happened yesterday was to credit.  But if I pan while looking at its AI traffic it stutters whereas for some reason FSLTL's injected traffic doesn't.

Recently I decided to run FSLTL's injector and turn traffic off in BATC:  much better experience overall.  Not only do I have double the aircraft with less impact but animation is as it always was super smooth on the ground in the air and during panning.  Fortunately BATC's ATC still instructs me just fine so all of that works.  Of course it's no longer controlling AI traffic but in reality BATC's injector has put other planes directly in front of me during taxi such that we're having a Mexican Standoff necessitating using their traffic map to remove the plane.   What?  That seems odd when it has complete control over traffic and it did not even tell me to hold.  Plus, I find BATC spaces traffic so far apart when setting traffic levels lower where the performance impact is where I want it and that is part of why I see much less traffic using BATC's level 3 than FSLTL at similar plane counts.  BATC has a ways to go I'm afraid, for me at least.

Edited February 6, 20251 yr by Noel

On 2/6/2025 at 6:19 PM, Noel said:

Here, BATC's traffic injector/manager has a ways to go.  After lots of stuttering traffic I've had better animation just last night and maybe the update that happened yesterday was to credit.  But if I pan while looking at its AI traffic it stutters whereas for some reason FSLTL's injected traffic doesn't.

Recently I decided to run FSLTL's injector and turn traffic off in BATC:  much better experience overall.  Not only do I have double the aircraft with less impact but animation is as it always was super smooth on the ground in the air and during panning.  Fortunately BATC's ATC still instructs me just fine so all of that works.  Of course it's no longer controlling AI traffic but in reality BATC's injector has put other planes directly in front of me during taxi such that we're having a Mexican Standoff necessitating using their traffic map to remove the plane.   What?  That seems odd when it has complete control over traffic and it did not even tell me to hold.  Plus, I find BATC spaces traffic so far apart when setting traffic levels lower where the performance impact is where I want it and that is part of why I see much less traffic using BATC's level 3 than FSLTL at similar plane counts.  BATC has a ways to go I'm afraid, for me at least.

I just abandoned this app so much trouble so much headache 50% of my performance is lost and for what? Honestly, they promised, but never delivered such a shame. 

7 hours ago, Aboodyking said:

I just abandoned this app so much trouble so much headache 50% of my performance is lost and for what? Honestly, they promised, but never delivered such a shame. 

You've got a bone to pick with them obviously but seriously, again, try it just using FSLTL's injector along w/ BATC's ATC it's decent for sure, much better than default ATC for certain and bonus by restricting to just yourself you cut down on the number of characters used for premium voices and pick up serious performance.  I'm very happy with this now overall.

10 hours ago, Aboodyking said:

I just abandoned this app so much trouble so much headache 50% of my performance is lost and for what? Honestly, they promised, but never delivered such a shame. 

never delivered?? - you're in a beta program for crying out loud.  Wait till it is actually offered out of beta.

Just did a test and it would appear that BATC and AIG do have an adverse effect on performance... EDDF (Virtual FRA) without traffic 40-42 FPS. With injected traffic  (set at 4) dropped to 24 FPS, shut down BATC back to 40s, I am aware that AIG have a bigger performance hit compared to FSTL or so I am led to believe. Will wait to see what the next updates bring BATC is to good a program and the developers give great support, so in my view a minor hiccup that I have no doubt will be sorted.

 

Regards

19 hours ago, Nicholas Jackson said:

I am aware that AIG have a bigger performance hit compared to FSTL or so I am led to believe.

If you had the same number of AI aircraft around you the difference would be within a couple of FPS. Sometimes better using AIG and sometimes better using FSLTL. The issue is that people think FSLTL is lighter on performance only because it injects a lot less aircraft.