12 minutes ago, Adamski_NZ said:

Great! I just had mine update to 1.9.14 (experimental). Any ideas as to the changelog? BTW - the survey shows they are listening - and actively working on fixes/updates etc.

It's very big....

🚦 The Big One — Ground Handling 2.0 The entire ground-handling and taxi logic has been rebuilt from the ground up. This targets the long-standing taxi pain points all at once: pushback conflicts, taxi blocking, incorrect runway queues, traffic stuck crossing runways, and traffic stuck taking off. It's passed automated and internal testing across a range of airports — but this is exactly the kind of change that needs real flights to stress-test, so testing and reports are very welcome. We will talk more about this in our next progress update. The new status panel in the taxi map is super helpful if you have issues and are reporting bugs in this space, so include screenshots of it in bug reports!

🧭 Vectors & Pathing - Reworked visual vectors from scratch. - Fixed a major vector pathing bug that could appear to send you to the wrong runway end or away from the airport entirely. - Fixed a major bug in the "runway in sight" code. - Add turn time into vector turn to final timing to prevent overshoot. - Reversed "Looking for Field" / "Field in Sight" so button action 1 triggers Field in Sight by default. - Fixed no-STAR visual approaches using the wrong altitudes, which was generating much longer vectors than expected and missing descent calls. - Fixed the controller sometimes giving descent or vectors after a visual approach had already been approved.

🆕 New Features - Player turnarounds — arrive at your destination, shut down the engines, and BATC will prompt you to load your next plan. Surrounding traffic stays active throughout. - Auto co-pilot voice — turn on in Options and pick if you want Any / Female / Male. Picks a regional voice to match your airline or GA aircraft registration, and falls back to your manual selection if it can't find a match. - Player taxi-path ground arrows — toggleable in-sim arrows along your cleared taxi route. Bind a key or button to turn them on/off while taxiing. - Wake-turbulence hold countdown — while holding short or lined up and waiting, the info box shows the wake category of the aircraft ahead plus a live MM:SS timer counting down to when you'll be cleared. Especially handy under ICAO, where you aren't actually told you're being held for wake. - Close protection — BATC now warns you before closing mid-flight (the X button or Alt-F4) and properly keeps your services and flight alive.

🗺️ Traffic Map — Major Upgrade - New status panel showing the live non-routine status of AI and player aircraft at a glance: waiting, holding, crossing, sequencing and going around. - Click-to-locate callsigns — click any callsign to jump to it on the map. - Show Callsigns - show callsigns of traffic directly in the map - Show extra data — show IAS / GS / ALT on traffic directly in the map. - Dark-mode colour tweaks. - New and updated icons for specific aircraft types — Airbus, ATR and Embraer, thanks to @MarceloNahas. More to come!

🎙️ Co-pilot & Voices - Local voice model consolidated — there's now a 1-to-1 match between every premium voice and a local voice (excluding the guest co-pilot voices). - Updated the local voice model — better flow on short sentences and improved phoneme support. - Added voice-allocation logging so you can see which voice each traffic aircraft and controller is assigned. - Fixed a couple of US premium voices that were deleted by ElevenLabs and had reverted to UK accents. - Fixed "four" being pronounced as "fore". - Fixed radio static occasionally looping after a controller finished speaking. - Latest pronunciation and airline data.

🛬 Arrivals & Approaches - No-STAR FAA descents now speak the runway as "expect…" and no longer reject your voice readback. - ICAO no-STAR descents now voice the arrival runway with the descent (previously it only showed in the info box) — mirrors the FAA fix from 1.9.14e. - High-elevation airports (e.g. KDEN): fixed visual approaches issuing descents below the field's actual elevation — field elevation is now sourced correctly. - High-elevation airports: fixed a missing turn-to-final and Tower handoff caused by a terrain-safety check incorrectly suppressing the normal turn onto final. - Fixed repeated/oscillating altitude calls for both player and traffic. - General improvement to the poor no-STAR arrivals that have been reported.

🛫 Ground & Taxi - Fixed traffic driving over the grass on dog-leg style runway entries (e.g. LGIR). - Fixed taxi path costing at airports with large displaced thresholds, leading to more accurate pathing (e.g. KSAN). - Fixed fatals in the taxi resolver. - Fixed pushback-then-taxi sometimes facing the opposite direction. - Fixed player pushback blockers not always clearing, which was leaving traffic stuck.

✈️ Traffic & Liveries - Fixed live traffic disappearing on longer flights. With live (Navigraph) traffic, the sky could gradually empty out as you flew away from your departure airport. Aircraft that first appeared on the ground and then took off are now correctly tracked and injected, so traffic stays populated throughout the flight. - Fixed AI aircraft occasionally locking up a runway via a long-term reservation from a collapsed flight path, which blocked departures and arrivals. - Fixed live-traffic turnarounds deadlocking permanently in pushback with the tug still attached. - Fixed live traffic getting stuck in the pushback state when there's no tug. - Fixed traffic sliders and the main traffic toggle not refreshing live traffic when turned on. - Fixed a speed-control restriction sticking after landing, which could affect aircraft reused for a later flight or aircraft that go around. - Improved callsign-vs-livery resolution for codeshare and regional paints (better brand/callsign matching, across both schedules and live traffic). - Fixed a number of incorrect aircraft-type performance profiles. - Better departure times for live traffic on the taxi map. - Nav lights now come on correctly if departure is near during initial traffic injection. - Fixed GA aircraft sometimes using an airline name when the first 3 characters of the reg mapped to an airline ICAO.

📡 CPDLC - Fixed CPDLC taxi requests not setting the assigned runway (which differed from voice and could lead to the wrong runway in use if the weather changed). - Added a pushback blocker, GSX flow trigger, predictive-blocker clearing and gate-unoccupied handling to CPDLC pushback/taxi requests.

🐞 Other Fixes - Sim Toolbar: fixed jumbled messages when using filters - ATIS: when the correct ATIS isn't given or picked up, the wording changed from "information X current, advise you have X" to just "advise you have X" to reduce confusion. - China (metric): fixed clearances still wording feet ("1800m feet") and QNH being given above the transition altitude. - Fixed a fatal error caused by an FAA no-start-descent with a missing approach name. - Traffic options menu now greys out the whole section when the main traffic toggle is off, and hides Season when live traffic is on. - Navigraph: clearer messaging when your session token expires — no more flood of misleading "token not valid" errors, making it clear that re-login may be required.

🛬 Ops Updates - MKJP, MKJS, YSSY, KDEN

Wow indeed! Thanks for posting :)

23 hours ago, Dialex said:

One of the biggest misconceptions about Early Access is the idea that development should be a steady path toward greater stability, where each update only improves the experience. In reality, that’s not what Early Access means.

Early Access simply means you’re using software that is still actively being developed. The product is not finished, and development is rarely a straight line. It happens in cycles: we build new features, integrate them into existing systems, discover unexpected issues, fix those issues, stabilize the build, and then start the process again.

The challenge is that every new feature interacts with systems that are already in place. Sometimes those interactions create bugs or issues in areas that were previously working perfectly. Nobody wants regressions, and we do everything we can to avoid them, but they are a normal part of developing complex software.

As the project grows, this becomes even more challenging. A larger and more feature-rich application inevitably has more moving parts, more dependencies, and more opportunities for unexpected side effects. Bugs that would have been simple to identify and fix early in development can become significantly more complex as the software evolves, and it sometimes requires to build a new system again with a different philosophy, and it will require more time to refine it and get the same stability again.

If you’ve been following the project over the past two years, you’ve probably seen this cycle several times. There have been periods where stability improved dramatically, followed by updates that introduced new issues. We understand how frustrating that can be, but it is also a natural consequence of active development and this should be totally expected. The alternative would be to stop making substantial changes and deliver less updates, which would defeat the purpose of Early Access in the first place.

This is why Early Access should not be viewed as a guarantee that every update will improve stability. Instead, it should be viewed as participation in an ongoing development process where progress often comes through iteration: building, testing, breaking, fixing, and refining. While the overall goal is always a better and more stable product, the path to getting there is rarely smooth.

Let’s be entirely direct: this explanation feels like a defensive excuse for a project that has lost its focus. We all know software development isn’t a straight line, but after two years of investment, those lines shouldn't be running in circles.

The community's frustration isn't about a few minor bugs; it’s about massive, unmanaged scope creep. Beyond promised a revolutionary AI ATC, but you pivoted into building a highly complex, bloated external traffic injection engine. By taking on the immense burden of simulating entire airport ecosystems instead of polishing the core IFR and VFR experience, you’ve forced your user base to act as alpha testers for a traffic utility.

This unnecessary expansion has driven a relentless cycle of exhausting structural rewrites that repeatedly reset the stability clock to zero, trapping us in a loop where a single hotfix breaks taxiway pathing, gate assignments, or ground comms—completely ruining flight immersion.

Claiming the only alternative is to halt updates entirely is a total cop-out, especially since BeyondATC already operates both a standard Early Access version and an Experimental branch. Having this infrastructure means you have the tools to isolate volatile, philosophy-shifting code.

The fact that system-breaking chaos still paralyzes the experience proves the issue isn't the nature of software engineering; it’s a failure of code isolation and a lack of baseline quality control.

Early Access is a partnership built on mutual value, not a blank check for perpetual architectural instability. We want to help build Beyondl, but we need to see actual forward momentum toward a stable product, not a project chasing its own tail.

16 minutes ago, marlon445 said:

Let’s be entirely direct: this explanation feels like a defensive excuse for a project that has lost its focus. We all know software development isn’t a straight line, but after two years of investment, those lines shouldn't be running in circles.

The community's frustration isn't about a few minor bugs; it’s about massive, unmanaged scope creep. Beyond promised a revolutionary AI ATC, but you pivoted into building a highly complex, bloated external traffic injection engine. By taking on the immense burden of simulating entire airport ecosystems instead of polishing the core IFR and VFR experience, you’ve forced your user base to act as alpha testers for a traffic utility.

This unnecessary expansion has driven a relentless cycle of exhausting structural rewrites that repeatedly reset the stability clock to zero, trapping us in a loop where a single hotfix breaks taxiway pathing, gate assignments, or ground comms—completely ruining flight immersion.

Claiming the only alternative is to halt updates entirely is a total cop-out, especially since BeyondATC already operates both a standard Early Access version and an Experimental branch. Having this infrastructure means you have the tools to isolate volatile, philosophy-shifting code.

The fact that system-breaking chaos still paralyzes the experience proves the issue isn't the nature of software engineering; it’s a failure of code isolation and a lack of baseline quality control.

Early Access is a partnership built on mutual value, not a blank check for perpetual architectural instability. We want to help build Beyondl, but we need to see actual forward momentum toward a stable product, not a project chasing its own tail.

Would be nice you avoid all that "community" and "we", because you surely do not talk for everyone, for sure not for me. Its just your opinion.

17 minutes ago, marlon445 said:

The community's frustration isn't about a few minor bugs; it’s about massive, unmanaged scope creep.

I'm not sure what feature, BATC released that would constitute as scope creep.

17 minutes ago, marlon445 said:

Beyond promised a revolutionary AI ATC, but you pivoted into building a highly complex, bloated external traffic injection engine. By taking on the immense burden of simulating entire airport ecosystems instead of polishing the core IFR and VFR experience, you’ve forced your user base to act as alpha testers for a traffic utility.

Traffic and airport runway operations is a fundamental part of the Air Traffic Control process, this is a puzzling statement, what are you talking about?

17 minutes ago, marlon445 said:

This unnecessary expansion has driven a relentless cycle of exhausting structural rewrites

I really would like to see a piece of software that hasn't had several rewrites. It's a fundamental part of being a SWE, the ability to realize you're software as it currently stands is limiting to the vision you've set out. Especially with something like ATC, I mean just look at VoxATC. It's been in development for near 5-6 years at this point, I can guarantee they've had their fair share of rewrites, the only difference is you have the ability to be a part of that due to the early access program.

17 minutes ago, marlon445 said:

that repeatedly reset the stability clock to zero, trapping us in a loop where a single hotfix breaks taxiway pathing, gate assignments, or ground comms—completely ruining flight immersion.

Claiming the only alternative is to halt updates entirely is a total cop-out, especially since BeyondATC already operates both a standard Early Access version and an Experimental branch. Having this infrastructure means you have the tools to isolate volatile, philosophy-shifting code.

The fact that system-breaking chaos still paralyzes the experience proves the issue isn't the nature of software engineering; it’s a failure of code isolation and a lack of baseline quality control.

Considering every area of BATC interconnects with other systems of itself, I really wonder how you would architect a system with code isolation here and minimize regressions. No area in ATC operates in a vacuum.

17 minutes ago, marlon445 said:

Early Access is a partnership built on mutual value, not a blank check for perpetual architectural instability. We want to help build Beyondl, but we need to see actual forward momentum toward a stable product, not a project chasing its own tail.

Which is exactly why BATC has done a survey as-well as built emulators to help fix bugs. Early Access isn't a partnership, it's simply an opportunity to have an open view in the development process, which can often be ugly.

46 minutes ago, marlon445 said:

Let’s be entirely direct: this explanation feels like a defensive excuse for a project that has lost its focus. We all know software development isn’t a straight line, but after two years of investment, those lines shouldn't be running in circles.

The community's frustration isn't about a few minor bugs; it’s about massive, unmanaged scope creep. Beyond promised a revolutionary AI ATC, but you pivoted into building a highly complex, bloated external traffic injection engine. By taking on the immense burden of simulating entire airport ecosystems instead of polishing the core IFR and VFR experience, you’ve forced your user base to act as alpha testers for a traffic utility.

This unnecessary expansion has driven a relentless cycle of exhausting structural rewrites that repeatedly reset the stability clock to zero, trapping us in a loop where a single hotfix breaks taxiway pathing, gate assignments, or ground comms—completely ruining flight immersion.

Claiming the only alternative is to halt updates entirely is a total cop-out, especially since BeyondATC already operates both a standard Early Access version and an Experimental branch. Having this infrastructure means you have the tools to isolate volatile, philosophy-shifting code.

The fact that system-breaking chaos still paralyzes the experience proves the issue isn't the nature of software engineering; it’s a failure of code isolation and a lack of baseline quality control.

Early Access is a partnership built on mutual value, not a blank check for perpetual architectural instability. We want to help build Beyondl, but we need to see actual forward momentum toward a stable product, not a project chasing its own tail.

So you wanted IFR and VFR ATC without any traffic? What's the point in that? I agree BATC has been really lacking but I never understand the desire to have air traffic control, but not any traffic.

Edited 3 hours ago3 hr by Langeveldt

On 6/25/2026 at 9:19 AM, Lucky38i said:

I am curious how voxatc will stack up when it decides to come out

You'll get the opportunity to find out shortly! It is a different approach to BATC, and I think its fair to say it will do some things better, and some things not so better! Whether either app is a better overall experience for any particular use case is up to you. 🤔 But this is a thread about BATC, so it's not appropriate to make comparisons here....

Edited 2 hours ago2 hr by kevinfirth

50 minutes ago, Langeveldt said:

So you wanted IFR and VFR ATC without any traffic? What's the point in that? I agree BATC has been really lacking but I never understand the desire to have air traffic control, but not any traffic.

I prefer traffic myself, but I can envisage a use case where someone wanted to practice RT procedures without having to worry about interference from AI at first.

Just did my first flight with the most recent update, albeit a short one (MUC-STR, 45 minutes block time). Vectoring was the best I've ever experienced. Basically true to life judging by the flight pah of the actual real world flight. Can't say much about ground handling, conflicts etc., yet because there wasn't much to handle, Munich is very efficient anyways and there is hardly any traffic at Stuttgart these days... taxi clearance to the gate was on point, though.

My hope/request for the future: More local copilot voices. I need an Italian first officer with a thick accent for my flights. 😅

BATC is such a gem.

Edited 2 hours ago2 hr by thepilot

People seem to have a very very short memory when it comes to the state of ATC just even 4 years ago. Never mind having to wait over 30 years just to have some resemblance of it.

What FSHud, BATC and SayIntensions have accomplished in a very short while is quite astounding. Not to mention the constant updating by all three.

Frustrating at times. For sure. But at the same time, Microsoft have made how many versions of Flight sim and for how many years and we are still going outside the box and spending a fortune for planes and scenery that we deem worthwhile of our time and energy because the main product is not up to a standard we find acceptable.

So I will applaud them instead of bashing them for their continued effort to make their product better, even if at times there seems to be a regression or lack of progress on certain aspects of their software.

5 hours ago, pete_auau said:

WOW! 100%. They nailed it. It's everything I expressed in the survey.

Now I have to again ask myself, how much longer do I need to wait for the experimental version to be released to us little people?

The survey results video is great. I wish more companies did this. So many send out surveys, but you never hear what comes of it. I'm glad I'm not just shouting into the void about vectoring and descent issues.

Really like the latest experimental update of BATC! Regional voices for the copilot, taxiway markers, and lots of improvements with FR24 integration and general behaviour as well.