Opened BeyondATC and it updated to v1.10.3 Experimental!
Awesome. Thanks for the update 
Version 1.10.3 Exp
The headlines are a completely rebuilt connection to the sim that removes one of the most common causes of âBeyondATC says the sim isnât runningâ, AI traffic that now moves in step with the simâs own frame rate for much smoother motion, jetways for AI traffic at the gate on MSFS 2024, and another large round of approach and vectoring fixes. Alongside those are a new country-based region and accent system and a long list of parking, go-around and radio fixes and winter schedules for airports that are heavily impacted by seasonal variation.
e[1;35mâ
Rebuilt Sim Connectione[0m
BeyondATC no longer needs the separate simconnect_ws.exe helper to talk to the sim. That helper relied on a local network port, and when a firewall, antivirus or another app blocked that port you would have the sim running while BeyondATC insisted it wasnât. That can no longer happen. If a port is blocked on your PC, the worst case now is that CPDLC or the traffic map wonât connect, but core ATC will always work.
- Airport loads are dramatically faster, often ten times or more.
- Starting a flight before you are properly in the sim now holds the load with a sensible message until you reach the cockpit, instead of erroring.
e[1;35mâ
Smoother AI Traffice[0m
AI traffic movement is now synchronised with the simâs own frame rate instead of BeyondATCâs, aimed at the uneven, stuttery motion you could see from an external camera, especially on takeoff rolls. This is a big change, so e[1mplease keep an eye on traffic smoothnesse[0m.
- More natural rotation and lift-off on takeoff, with revised takeoff distances and rotation speeds for several aircraft classes based on real world data.
- We suggest you set the BATC frame rate value to be at or above the typical max FPS you get during a flight so that the core BATC application runs at least as fast as your sim. For example my max sim rate is normally 45 fps (pre frame gen), I run BATC at 60 fps.
e[1;35mâ
Jetways For AI Traffic (MSFS 2024 only)e[0m
For the first time in a public build, AI traffic parked at a gate now gets its jetway connected, including arrivals once they reach their stand, so busy terminals finally look the part.
- Works on MSFS 2024 SU6 & SU7, and adapts automatically to the sim version you are running.
- Jetways reconnect if you move away from an airport and come back, this is a sim âfeatureâ that we have to work around.
- Allow around 20 seconds after arriving at a new airport before jetways start connecting.
- A few stands wonât connect where the simâs own jetway data is missing or incomplete for that gate.
- Requires no particular traffic model set or additional software to work
- Low resource impact as it does not insert âghost aircraftâ or any other workaround to get connections
e[1;35mNavigation data problem warninge[0m
BeyondATC now checks the procedure data (SIDs, STARs and approaches) the simulator provides for your departure and arrival airports each time a flight loads. Sometimes, most often after an AIRAC update, MSFS hands over procedures with many waypoint positions missing. When that happens, approaches collapse into a straight line to the runway, which caused wrong vectors, âyouâve flown through the final approach courseâ calls, traffic landing at 90degrees to runway and unexpected missed approaches.
When BeyondATC detects this, a Navigation data problem dialog names the affected airport(s), with three options:
Open help page: step-by-step fix guide on the wiki (clearing the scenery indexes, and a Navigraph navdata reinstall if you use Navigraph)
Cancel flight: return to the main menu so you can fix it first.
Continue anyway: fly on; ATC at that airport may not behave correctly.
Weâve reported the underlying simulator issue to Asobo:
Asobo bug link : https://devsupport.flightsimulator.com/t/facilities-api-returns-wrong-corrupt-navdata-after-airac-updates/18552
e[1;35mâ
Approaches & Vectoringe[0m
Another large pass at vectored arrivals, aimed at the wrong-way intercepts, loops and repeated calls some of you have reported. The final vector before an ILS clearance is now also a single combined call, âX miles from FIX, turn left heading, maintain until established, cleared ILSâ, matching real world phraseology. e[1mPlease redo any vectored departures and arrivals that failed for you on the last build.e[0m
- Fixed aircraft being vectored onto the wrong end of the localizer.
- Fixed repeated vectoring instructions on the same leg, up to nine calls where three should do.
- Fixed flying straight through the localizer without an approach clearance is now caught and recovered cleanly from the charted approach fix.
- Fixed âdescend via the STARâ clearing you to a level thousands of feet above you, plus a stray âclimbâ call, when a STAR had an at-or-below restriction.
- Fixed STAR and SID speed calls such as âreduce speed to 250 knotsâ arriving a mile before the fix. They are now only a warning if you actually miss the constraint.
- Fixed generated visual approaches producing a phantom go-around and an extra dogleg instead of a clean turn to final, reported at KOKC and KLAX.
- Fixed never getting landing clearance on a straight-in visual approach, reported at KPHX.
- Fixed departures on SIDs that double back near the airport, UUEEâs OLMU3H for example, getting a false âoff courseâ call, a âcleared directâ to a fix already behind them, and then no Tower handoff at all.
- More fixes for looping and wandering vectors on departures.
e[1;34mâ
Arrivals & Descentse[0m
- Asking for descent early now properly includes the STAR and runway in the descent clearance, reported at RPLL.
- Fixed your filed STAR being swapped for a worse matching one after a runway change, reported at LPFR.
- Fixed a runway change leaving you flying the old runwayâs STAR legs, reported at CYYZ on the IMEBA9.
- Fixed declaring a go-around above the go-around altitude getting a climb instruction when it should have been a descend.
e[1;34mâ
Regions, Accents & Voicese[0m
Airspace sectors are now mapped to countries, which lets us apply regional rules and accents far more consistently. Accents have been remapped worldwide on top of this, so smaller Scottish airports no longer have English accents and Shannon Oceanic now sounds Irish.
- New accent sets for the Caribbean, Scotland and South Africa, expanded US airline accents, and new fallbacks for Turkish, Vietnamese, Filipino, Northern European, Chinese and African controllers.
- Pilot and controller voices are no longer reused on the same frequency, and airlines keep the same voice as you move between frequencies. When a region runs short, controllers borrow voices from the furthest-away controllers first.
- China: metres versus feet is now decided by the airspace you are in rather than the nearest airport, the metric level table matches the official chart, and you get explicit climb or descend calls when entering or leaving Chinese airspace.
- UK: CAA-specific phraseology where it differs from ICAO, for example when to say âaltitudeâ or âtoâ in an altitude change.
- Canada: fixed remaining cases of QNH being used instead of altimeter.
- FAA: âclimb via SIDâ is now included in PDC clearances.
- Fixed ATIS on COM2 using COM1âs voice.
e[1;34mâ
Radios & Communicationse[0m
- COM1 and COM2 are now fully tuning history. Previously, monitoring COM2 could send a COM1 handoff to the wrong centre, most noticeably around Paris.
- Fixed a departure being handed straight back to the controller it had just left on a shared frequency, reported at EGPF.
- Fixed a newly tuned controller giving you a speed instruction before you had checked in.
- Fixed âaircraft calling for new altitude, say callsignâ being used on every frequency, including Ground, when your callsign readback didnât parse.
- Fixed taxi readbacks rejected when your callsign digits ran into the taxiway name, for example âalpha delta three for quebecâ.
- âSIDâ heard as âsitâ, âsidsâ or âs i dâ is now understood everywhere.
- Fixed ATC reading out internal point names such as âvectors to EXTâ.
- Fixed manila Control handing off to 128.300 in the western sector instead of 119.300.
- Fixed being asked to confirm your squawk or Mode C while still on the ground or just after touchdown.
e[1;34mâ
CPDLCe[0m
- Fixed losing your controller for several minutes after crossing an FIR boundary while a handoff was outstanding.
- Fixed CPDLC replies being silently dropped by clients that address them to âSERVERâ, which could leave you without a controller for over a minute or repeat a clearance by voice that you had already accepted.
e[1;34mâ
Runways & Go-Aroundse[0m
- Crossing departure runways now take turns. Fixed an aircraft being cleared for takeoff while another was cleared or rolling on a crossing runway, reported at KPVU and YMML.
- Fixed AI go-arounds diving to near ground level before climbing away, which could leave the runway falsely marked occupied and block all later traffic.
- Fixed departures lined up and waiting rolling underneath a go-around, EGKK for example.
- Fixed departures lining up at a runway crossing part way down and then taxiing back up the active runway, reported at YSSY and VOCL.
- AI traffic now uses the sceneryâs own runway turnaround bays where they exist, and backtracks are detected properly at many more airports.
- Fixed a taxiing aircraft told to hold for âoncoming trafficâ that was actually a lined-up departure.
- Fixed a false âstop your takeoff rollâ call to a parked aircraft, caused by a single bad airspeed reading from the sim.
e[1;34mâ
Parking & Live Traffice[0m
- Domestic and international is now decided by country mappings, fixing domestic arrivals parking at the international terminal and the other way round.
- Your own parking follows your callsignâs real stand.
- Stands are chosen by how often they are really used, rather than at random from the eligible list.
- Parking overlap checks use each aircraftâs real wingspan, so fewer stands are wrongly blocked and fewer aircraft overlap at tight terminals.
- Live traffic now parks at a sensible gate when the live feed hasnât given one yet.
- Fixed live traffic losing arrivals that had already landed, and live aircraft being blocked from or kicked off gates by a scheduled copy of the same flight.
- Fixed AI aircraft potentially being removed from their gates when BeyondATC checked a stand for you.
- NB: If exact arrival parking matters to you, scheduled traffic is the better choice, as it knows where the real flight parked.
e[1;34mâ
Traffic Data & Liveriese[0m
- Winter schedules for seasonally affected airports (around 100) are now available. Winter runs from the last Sunday in October to the last Sunday in March, as per IATA, so any flight with sim date set in that range would use the updated schedule.
- Fixed enroute traffic dying off and never returning after the sim clock moved by more than 24 hours.
- The MSFS 2024 Community2024 folder is now scanned for traffic and player liveries.
- BravoTG: fixed the ANZ 777-300ER livery list and added several missing 2024 livery variants.
e[1;34mâ
Traffic Mape[0m
- The traffic map now uses map tiles we host ourselves as Carto maps has gone payware.
e[1;34mâ
Aircraft Recognitione[0m
BeyondATC works out your aircraft type from what the sim reports, and far more aircraft are now recognised correctly for VFR use.
- Third-party aircraft: Trislander, Wilga, Tecnam P2012 V2, Taylorcraft BC-12D, DHC-2 Beaver and Zlin Savage Norden, Pietenpol Air Camper (CAMP) plus the Commander 114, which was being misidentified.
- MSFS default aircraft: DC-3, Pilatus PC-6, DG-1001e, F/A-18E, Grumman Goose, LS8, Antonov An-2, A-10, Junkers F13, Ford Trimotor, Dornier Seastar, Aero 45/145, MU-2, Optica and Joby JAS-4.
- Helicopters: AS350, AS365 Dolphin, H145, MH-60, Bell 407, Cabri G2, R66, H225, CH-47 Chinook, Bell 47J, S-64 Aircrane and the Magni M-24 gyro. Note that helicopter procedures are not supported in BeyondATC.
- More specific matching within a family of aircraft, so for example a Cessna 400 is identified as a Cessna 400.
- Fixed the Hughes H-4 Hercules being identified as a C-130, and the CH-47 Chinook and Aero 45 being mistaken for the Storch and Pipistrel Alpha Electro.
- Fixed aircraft not being recognised when the sim reports them in an unusual format, including MSFS 2024 âModel: Variantâ titles and names starting with â$$â such as the AS365 Dolphin.
- Corrected names for the Cessna 350, Rans S-6 Coyote II, Savage and Taylorcraft, Tecnam P2012 performance, and DG glider runway lengths.
e[1;34mâ
Other Fixese[0m
- Caught more cases where ATC could forget about you.
- Fixed a crash when AI traffic requested taxi to a gate at an airport that wasnât loaded.
- Fixed a distance error that affected close-in runway, waypoint and flight plan checks.
- Smoother frame times from reduced memory churn in speech, the toolbar, the taxi map and the traffic map.
e[1;34mâ
Ops Updatese[0m
- CYYC, ENTO, HRYR, KDFW, KHOU, KPSP, LATI, LCLK, LFPG, LGML, LGTS, LICJ, LIMC, LROP, LSZH, OAKB, RJFR, SABE, SACO, VOCL, YBBN, YSWS, ZGHA
- Palm Beach recoded from KPBI to KDJT
- Latest AIRAC pronunciation data, airline codes and callsigns
Loving the gates connecting to ai traffic finally. Now seeing how everything new updated will work. Thank you!!
Agree that the connecting gates have added a lot to the sim, has improved the taxiing experience for sure.
Iâve noticed an improvement in the smoothness of the AI aircraft. However, Iâve also noticed that landing aircraft instantly slam down their nosewheels shortly after touching down on their main landing gear.
Iâm in the normal version, not experimental and noticed a severe FPS drop when AI traffic enabled. It keeps dropping until the sim is unusable. In single digit fps. When I turn off AI traffic or close BATC my FPS recovers to normal. Only today, never before. So Iâve had to disable AI traffic. Anyone else?
Are you using AIG or FSLTL models for traffic?
Just double check default AI hasnât enabled itself.
You have just solved my problem, thank you so much!! Default AI Traffic did indeed get enabled, I have no idea how. I never use it and have never had it switched on. Thanks for the tip, never even occurred to me that might happen.
Nice one. I only know because it happened to me this very morning. 
This also happens to me sometimes when Iâve just updated my drivers. Clearing out the driver cache almost always fixes the problem.