Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Beyond ATC Traffic injection performance issues

Featured Replies

Just now, Noel said:

I almost bought FSHud after failing to get rid of stuttering traffic in BATC but really like the simple BATC interface and with so many others apparently not experiencing this I'm going to stay with it a while longer.  If this continues I'd best give FSHud a shot.  Does it use FSLTL models?  

You can use FSLTL models with the FSLTL injector, or AIG models with FSHud's own AIG injector or with AIG TC. I understand you can also use either of the model types with MSFS in-built live traffic but since I've never done that myself I can't personally confirm it.

Ian Box

  • Replies 194
  • Views 60k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I think we all get the point by now: BATC is a disappointment for you and you like to use words that aren't allowed. I love BATC on my 3.5 year old PC with a 3060Ti so I guess everyone has a different

  • SierraDelta
    SierraDelta

    That is just not true! It was clear from the beginning that BeyondATC offered 2 tier levels: Basic and Supporter. The difference being that Supporters would get access to certain functionality - such

  • I know it's each to their own, but that pretty much defeats the purpose of using ATC as it's not separating you from any of the traffic.

Tangent:  I have a question re when ATC instructs to 'climb via SID' and does not specify a specific altitude (presumably because it's in the SID) exactly what altitude should I aim for?  Is it the altitude I can see in the FMC at where the SID starts?  Or is it the altitude at the end of the SID, at a transition perhaps?  In the flight I'm in now, KBZN>KSFO using BATC's injector it instructed to take off at a certain heading, but it never told me to resume my own nav nor directed me to a waypoint so I had to resume my own navigation.  We're heading due south for 30 miles and I kept waiting for BATC to update this and it never did.  Have had none of that with using FSLTL's injector and I'll guess that is because much less resources are demanded by BATC in that latter context.

And similarly right now, BATC says this, "descend via STLER4 arrival"   So do I look at the altitude step at the beginning of that STAR??

Edited by Noel

Noel

System:  9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL  64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync.

Aircraft used in MSFS 2024:  Fenix A320,  Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.

 

3 minutes ago, ConstVoid said:

You can use FSLTL models with the FSLTL injector

Hmm, really?  And FSHud 'reads' this traffic in its ATC function?

Noel

System:  9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL  64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync.

Aircraft used in MSFS 2024:  Fenix A320,  Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.

 

8 minutes ago, Noel said:

Hmm, really?  And FSHud 'reads' this traffic in its ATC function?

Absolutely. Any AI traffic in MSFS (2020 or 2024) can be intercepted and adopted by FSHud.

One small caveat - with 2024, the default live traffic can't be intercepted unless FSLTL or AIG models are installed, because the default aircraft only exist in the cloud.

Edited by ConstVoid
Extra Info

Ian Box

7 minutes ago, ConstVoid said:

Absolutely. Any AI traffic in MSFS (2020 or 2024) can be intercepted and adopted by FSHud.

One small caveat - with 2024, the default live traffic can't be intercepted unless FSLTL or AIG models are installed, because the default aircraft only exist in the cloud.

I don't use voice but use Auto Respond most often in BATC.  Does FSHud offer this option as well?  Are there premium voice options?  Thanks for this it sounds like of like a no-brainer.  I have had the sense most who've used both prefer FSHud's ATC control.

Edited by Noel

Noel

System:  9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL  64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync.

Aircraft used in MSFS 2024:  Fenix A320,  Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.

 

Yes, voice (which I don't currently use) or Co-pilot responses, with menu selection for initiating interaction with ATC (as opposed to responding).

Ian Box

Just now at KSFO in weather, lovely landing in the 738!  After getting off of Rwy19L and aiming towards the arrival gate from a 150' feet away the wide open rate was 72FPS-fg, and this was with BATC's injector.  There were 6 planes in the vicinity (via LNM), and I saw no parked planes at my gate (this was not BATC's gate, but mine just for convenience).  Unfortunately when I opened Settings and moved the Traffic slider to OFF traffic did not disappear, and this after waiting a full 50 seconds or so.  So I killed BATC and that removed its traffic, and the rate went to 94FPS-fg.  This is a 30% impact, BATC, on frame rate at the arrival airport and that is in line with prior tests.  Not quite as fair comparison but I then turned on FSLTL's injector, and now we see 7 planes in the air after a minute or so and a bunch of planes at my gate area already including some already pushing back.  Rate was now 82FPS-fg but again with much more traffic in play than with the BATC test.  One of planes after PB starting its taxi actually stopped for me as i was threatening to be in its way, then after I proceeded, it commenced.  And once again, BATC's injector is not controlling this, FSLTL is.  So it has some awareness of my plane, or so it appeared.  The 92FPS-fg was in the External view of course, whereas other FPS mentioned is in the VC:

spacer.png

 

Noel

System:  9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL  64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync.

Aircraft used in MSFS 2024:  Fenix A320,  Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.

 

3 hours ago, Noel said:

when ATC instructs to 'climb via SID' and does not specify a specific altitude (presumably because it's in the SID) exactly what altitude should I aim for?  

And similarly right now, BATC says this, "descend via STLER4 arrival"   So do I look at the altitude step at the beginning of that STAR??

 The initial altitude is in the SID unless they assign you something else. 16,000 in the sids off BZN.

As for the STAR, ATC should give you an Altitude limit with the "descend via STLER4 arrival"

Edited by Dave_YVR

i7-13700KF, 32gb DDR4 3200,  RTX 4080, Win 11, MSFS 2024

41 minutes ago, Dave_YVR said:

 The initial altitude is in the SID unless they assign you something else. 16,000 in the sids off BZN.

As for the STAR, ATC should give you an Altitude limit with the "descend via STLER4 arrival"

Thanks for that.  So when you say initial climb, is that the first altitude listed at the start of the SID?

Noel

System:  9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL  64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync.

Aircraft used in MSFS 2024:  Fenix A320,  Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.

 

37 minutes ago, Noel said:

Thanks for that.  So when you say initial climb, is that the first altitude listed at the start of the SID?

I don't know if this is correct, but I always look at the highest altitude in the Sid, and that is what I set in the altitude window.  Many times  the first waypoint in the sid is around 1000 feet, and I don't want to level off there. The FMC follows the altitude constraints  in the waypoints anyway, so you won't be higher than you should be. 

 

 

 

2 minutes ago, Bobsk8 said:

I don't know if this is correct, but I always look at the highest altitude in the Sid, and that is what I set in the altitude window.  Many times  the first waypoint in the sid is around 1000 feet, and I don't want to level off there. The FMC follows the altitude constraints  in the waypoints anyway, so you won't be higher than you should be. 

Ok that is what I guessed at too for the same reasons.  Thanks!

Noel

System:  9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL  64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync.

Aircraft used in MSFS 2024:  Fenix A320,  Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.

 

2 hours ago, Noel said:

So when you say initial climb, is that the first altitude listed at the start of the SID?

No, those are just altitude constraints on the way to the initial altitude. Your initial alt is specified in the SID and if not ATC will assign one. In this case, I'm assuming the BGSKY even though all of the SIDS out of BZN show 16,000 in the text.

 

 

 

 

Edited by Dave_YVR

i7-13700KF, 32gb DDR4 3200,  RTX 4080, Win 11, MSFS 2024

After many flights using the FSLTL injector and the BATC traffic, I see no real performance difference between the two. I like the chatter in BATC, so I am switching back to it's traffic. 

 

 

 

1 hour ago, Bobsk8 said:

After many flights using the FSLTL injector and the BATC traffic, I see no real performance difference between the two. I like the chatter in BATC, so I am switching back to it's traffic. 

Very real here, tested carefully at departure and arrival airports.  Plus, can't stand the stuttery AI traffic BATC generates.  All our systems have their own CPU/GPU ceilings so what might not present as a diff for some will for others.

Noel

System:  9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL  64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync.

Aircraft used in MSFS 2024:  Fenix A320,  Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.

 

6 minutes ago, Noel said:

Very real here, tested carefully at departure and arrival airports.  Plus, can't stand the stuttery AI traffic BATC generates.  All our systems have their own CPU/GPU ceilings so what might not present as a diff for some will for others.

I have never seen any  stuttering in  AI traffic, ever. 

 

 

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.