From all the preview videos I’ve watched on 2024, the ATC sounds pretty much the same as current. Obviously these are preview builds, but I highly doubt there will any grand surprises. At a minimum, we know 90+ % of traffic will be accurate to real life. There may also be small enhancements to ground and flight behavior. I think I also read that default ATC will feature regional accents. But I think this is where it will end for the time being.
Asobo would be unwise to spend a chunk of time on something that only a niche (of a niche) of the market want and will use properly. This is exactly why 3rd party devs exist in the first place.
If you don’t want to pay another €30 for early traffic access, don’t, wait for it to come to the EA version. It really is that simple, in my mind.
I don t discuss the atc..but the traffic…batc is functionning as msfs atc in many ways, is better at this Time.no doubt..
But if batc traffic injector become obsolete or non functionning ?
And what if an asteroid hits the earth? Your what ifs don’t make any sense.
If you don’t like BATC, which is more than apparent, then go back to chatting with your AI co pilot and stop spreading rumors and false info about a product which you seem to so hate.
So what? Have scenery developers packed up shop after seeing the level of detail that FS24 has on offer? Of course not. Whatever FS2024 has in terms of traffic, I guarantee there will be plenty of room for BATC to improve it.
The devs certainly have the “clogged frequency” issue on the forefront to fix. I’ve suggested to the devs that they do a few things:
Speed up the cadence of the calls…less words. less pauses between words.
Right now, Departure and Approach seem to be on the same frequency, which is unrealistic. They need to load balance and possibly have multiple freqs for Delivery/Ground/Tower/Departure/Approach for super busy airports, as they do IRL.
The frequent visual approaches in the US really clogs things up - it’s a six-part exchange that takes probably 30-40 seconds per plane.
Traffic is quite cool, but definitely not ready for prime time yet.
I’ll amend my comment to say that very busy airports like KDEN or KORD will almost always have separate controllers for Departure and Approach. More generally, BATC needs some “load balancing”.
Well I don’t know what the deal was with my flight yesterday, but today I’m re-flying the Nairobi to Dubai route I tried yesterday, and everything has been working well. I had traffic on the ground, departing and taking off from Nairobi, I’ve had ATC coverage en route, with handoffs to different Radar Control areas en route, and no issues with requesting my scheduled step-climb about 45 minutes into the flight. The STAR into Dubai has some “interesting” doubling-back to it. I’ll be very curious if BATC recognizes that route and has me fly the whole thing, or if it tries to vector me in through some shortcut that will be difficult to fly in a heavy 77W.
This in my opinion is the greater problem. Not just with visual approaches but overall. BATC uses WAAAAAY too many words and transmissions to get done what IRL takes very few of both.
The secondary issue this creates is that (speaking only for me), because BATC’s voice structure is so scripted it tends to become an audio ‘overload’ of the same thing being said the same way, over…and over…and over…and… This is not too different that what MSFS is doing from the ATC perspective.
That being said, this has improved significantly over the last few days. I also assume (hope) that it will improve more over time (splitting freq. for controllers is a MUST!!!) Still, in the current state, it gets somewhat monotonous rather quickly. Particularly on approach.
It’s a fair point and it does make it a little easier to deal with.
However, Premium vs. Basic aside, the general format is still far too repetitive with too many extraneous, unnecessary words added. It really tends to actually break the immersion that it should be adding in it’s current iteration (IMO).
@DrVenkman3876
You don’t need to go on Discord to get the supporters pack for BATC. Just buy the pack from inside the app, allow it to update, then change the version to experimental in the app’s settings, before you press fly within the app.
Yes, I know. I’ve already done that. My post was about reporting the issues I was experiencing on that flight to the developers via their Discord. I’ve since made 3 - 4 flights and had no issue with traffic or ATC comms (aside from one mid-flight crash that I recovered from by restarting BATC in cruise). I am chalking up last weekend’s flight issue to just random gremlins.
I use BeyondATC and FLOW from Parallel42 since few days.
Is someone knows how to “call” BeyondATC program from Flow Toolbar ?
GSX and FS2Crew are already integrated in Flow.
