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 release Traffic alpha for Supporters

Featured Replies

14 hours ago, Bobsk8 said:

Many times. they don't seem to be interested in anything negative. 

like the offical ms2020 forumns

 
 
 
 
 
  913456
  • Replies 234
  • Views 54.3k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • If i want to read about PSXT or Real Traffic i will seek out those threads. I don’t need or want this discussion being spammed by someone offering or selling a competing product. It happens WAY too of

  • No offense, but by saying this, you've totally discredited yourself for this discussion. Or any discussion.

  • One of the first basics of any ATC program, and I have been using and beta testing them since  RC4 was introduced a couple of decades ago, is the Localizer Intercept angle. That should almost always b

2 hours ago, Langeveldt said:

One thing, it gave me a callsign "Airbus 16", and I'm not sure where to change it.  I thought it would automatically sense my Simbrief callsign of Ryanair 216.  

What was the airline code you put into the simbrief boxes on the site?

For the ATC Callsign box, you would want RYR216

Edited by Tuskin38

5 hours ago, Aglos77 said:

The problem may be that they want to cover a lot instead of focusing on solving the basics first, what good is an AI traffic control if you are not able to do a good vectorization as mentioned above.

One of the first basics of any ATC program, and I have been using and beta testing them since  RC4 was introduced a couple of decades ago, is the Localizer Intercept angle. That should almost always be 30 degrees or less. The way you get that is to be far enough away from the airport, so that an approach to the localizer, will result in = > 30 degree intercept.  Intercept angles of 90 degrees, at the FAF, just doesn't work for an airliner, and will most likely lead to an unstabilized approach. That is what is currently missing in BATC. In the US, anyway, which is where I am currently flying on A PIlots Life.  Approaching the airport on a Star, BATC almost every time, turns the star into a visual approach, with its vectoring that leads to the 90 degree intercept angle. If I ignore the vectoring and continue on the Star, or If I ignore any vector that results in an improper angle, then BATC goes into it's "deaf city" mode and stops communicating. This should have been the first thing they corrected, rather than worrying about AI ground traffic at the airports. 

 

 

 

16 hours ago, RobJC said:

Patience is a virtue. 

That is why it is best not to buy early access products. 😉

3 hours ago, Langeveldt said:

I thought it would automatically sense my Simbrief callsign of Ryanair 216.  

It does. If you put in the correct one in the appropriate Simbrief fields. Maybe it knew you were an imposter, since Ryanair doesn't fly Airbus. 😉

Edited by Farlis

When will we be able to have access to these new features for the poor who have only acquired early access?

 

Thanks a lot

So I bit the bullet and upgraded to supporters edition so I can properly form an opinion. Also seems that the other non traffic bug fixes are not available (yet) for the regular early access, so it’s nice to get some much needed wider fixes at the same time.
 

Impressions from my first flight OMDB-VHHH. The good - brilliant to have some life in the sim and hearing and seeing other aircraft. Departure from Dubai was late at night, so traffic was lighter than during rush hour but had some Air India, Saudi and Air China on frequency for departure. When climbing out there were a couple Emirates inbound and all sounded like it was working properly. Nice to see it correctly used mixed alphanumeric call signs as per real world (Emirates 5 Tango Super). Cruise was relatively quiet as only AI aircraft departing/arriving at Dubai and Hong Kong were injected, heard some more traffic enroute that fit those criteria. Arriving into Hong Kong was around 10am local, very busy and very immersive to hear a flurry of activity around and the assigned accents were diverse and usually fitting for the geography (though most QR/EK flights would probably have expat accents from UK, US, OZ… rather than Middle Eastern). Landed and taxied to the gate without any issue and loads of chatter on frequency with aircraft arriving, departing and pushing back.
 

Some things that didn’t work so well - I use AIG as the source for the models and they are not yet optimised for animations, sounds and lights so quite a few issues with missing lights or aircraft taxiing with spoilers up etc. I hear this will get addressed later, for now FSLTL is the recommended option to ensure all animations and lights work. There is no proper separation yet, so can still get a bit chaotic and pilots discretion - i.e. no speed instructions, holds, shortcuts. On the ground in Hong Kong I explored via drone mode after parking up at my gate and spotted that there was a complete gridlock on runway 07R (used for departures as in real life). Long queue of aircraft trying to depart with one on the runway but just stuck there and aircraft waiting to cross the runway from both sides, even some facing each other from opposing ends of the same taxiway. I also spotted some aircraft stuck during taxi on the taxiways. Gate assignments were great though as it ignores the sim parking and relies on FR24 data to populate parking assignments. 
 

I used density 10 for the first flight but will try 5 on the next one, as recommended by the devs. For info, the slider manages the time period that’s considered for FR24 departures rather than a more traditional density slider, so 10 just means it injects more traffic that wouldn’t depart in reality for a few hours earlier/later.

FPS performance was superb - I used PSXT in static parking only mode before and I’d say BATC FPS were higher than with statics only from PSXT.

 

So far I like it considering it’s in Alpha and again a lot of promise but we’ll see how quickly this progresses to stabilise and add features. Didn’t get any vectoring so can’t comment on whether the visual approach vectoring that was very broken previously is fixed. 

Edited by Speedbird 217

7 minutes ago, krakosia said:

When will we be able to have access to these new features for the poor who have only acquired early access?

 

Thanks a lot

when the traffic  is stable and without bugs

any performance comparison with fs hud, or fslt injetor? i hope is much better than fshud cause that atc tanks your fps to a slideshow even used more CPU than msfs alone

Edited by michdb8

10 minutes ago, Speedbird 217 said:

Long queue of aircraft trying to depart with one on the runway but just stuck there and aircraft waiting to cross the runway from both sides, even some facing each other from opposing ends of the same taxiway. I also spotted some aircraft stuck during taxi on the taxiways.

Could be due to the airport layout. Anyway, thanks for the feedback, sounds promising. 

7950X3D | RTX 4090 | 64GB DDR5

6 minutes ago, michdb8 said:

any performance comparison with fs hud, or fslt injetor? i hope is much better than fshud cause that atc tanks your fps to a slideshow even used more CPU than msfs alone

FPS were great during my initial test.  I initially used FSLTL and later PSXT with static only parking before this and get higher FPS with BATC than with either of the other options.
 

On a 13900KF and 4090 around 60-80 FPS at all times with traffic slider at 10, both in OMDB and VHHH. Doubled to 120-160 with LSFG and a good 10-20 FPS more than I had with either of the other options previously.

2 hours ago, Speedbird 217 said:

FPS were great during my initial test.  I initially used FSLTL and later PSXT with static only parking before this and get higher FPS with BATC than with either of the other options.
 

On a 13900KF and 4090 around 60-80 FPS at all times with traffic slider at 10, both in OMDB and VHHH. Doubled to 120-160 with LSFG and a good 10-20 FPS more than I had with either of the other options previously.

I agree...not seeing any FPS hits so far.  The program is as others have said still in Alpha, but it is working pretty darn good when everything is working right.  And so far a lot has been working right.  🙂

10 hours ago, Aglos77 said:

The problem may be that they want to cover a lot instead of focusing on solving the basics first, what good is an AI traffic control if you are not able to do a good vectorization as mentioned above.

What good is vectorization for only one aircraft in the sim if it doesn't work as well once the traffic is in? They are doing exactly what you expect - complete the foundation of the tool and then improve/fix/enhance. That's sane development

For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.

3 hours ago, Speedbird 217 said:

FPS were great during my initial test.  I initially used FSLTL and later PSXT with static only parking before this and get higher FPS with BATC than with either of the other options.

I want to emphasize that. That's a game changer for anyone who likes to fly with real life amounts of traffic.

For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.

I will say this. I see enough things working really well to have optimism that the team is talented enough to bring this product home. 

7950X3D | RTX 4090 | 96GB DDR5 | 4K G-Sync | Win11 Pro

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.