In Simbrief Airline ICAO code you enter EZY UK then the flight number. If it was British Airways ICAO code BAW then the flight number…BATC will recognise that code and use it.
easyJet UK
EZY
“EASY”
easyJet Europe (Austria-based)
EJU
“ALPINE”
easyJet Switzerland
EZS
"TOPSW
BAW will be speedbird
So inthe ICAO code you enter EZY in the flight number you enter 64JW and BATC will respond Easy 64 juliet Whiskey
Yes, I see what you mean now. The ATC callsign can be different from the flight number, although sometimes they are the same.
For example, the scheduled flight may be EXS465, but the operational ATC callsign could be EXS91UB, which would be spoken as “Channex 91 Uniform Bravo.”
In SimBrief, enter the Airline ICAO code (e.g. EXS/EZY/BAW) and the Flight Number in the Flight Info section.
If the flight uses a different operational callsign, enter that in the ATC Callsign field under Aircraft Info.
BATC should then recognise the ICAO prefix and use the correct spoken telephony name — e.g. EXS = Channex, EZY = Easy, BAW = Speedbird — with the appropriate flight/callsign identifier. Sorry I probably was not clear. Please find arttached a copy of my Simbrief profile for Jet2.
In simbrief you can specify the airline’s call sign e.g easyjet EZY Jet 2 EXS Tui TOM then in the next box type flight number 64JW if you in type EZY in the first box and 64JW BATC will refer to you as Easy 64Juliet Whisky
Appreciate the advice (and pointers to BATC guidance). I was clearly putting the flight number elements in the wrong field and the callsign in the other. I’ll pay better attention to the guidance and give it a go when I get back to the sim this week.
BATC really does provide me with much greater immersion … as do the FBW and GSX addons.
any other users have this issue? I tried a VFR flight today in VR and the BATC toolbar window wouldn’t expand the response choices. They were all bunched together in a single line. Expanding the window taller only increased the upper message area. I have a feeling that I’ve got a mismatch on the basic BATC program and the toolbar addon.
Update: I think I figured it out. There is a new version of the toolbar add on for use in the experimental branch which is the one I’m on. I’m sure the next flight will be fine.
When I’ve been assigned an ILS approach I don’t seem to be cleared by ATC all the way down to the Final Fix altitude. I wondered if when Im cleared for the ILS approach whether this is a license to descend as required - or whether I’m missing something.
A further vectoring rework that should finally settle the circling and oscillation issues, charted missed approaches flown properly on a go-around, a clean-up of the duplicate or missing radio frequencies the sim hands us, a new US VFR flight following flow, and Toolbar Beta 3.1.
And the API label issue on the traffic map is sorted - yay
e[1;35m Vectoring Reworke[0m
Vectoring has been reworked again, aimed squarely at the oscillating, circling and “extra loop” behaviour some of you have been seeing. A re-vector now only happens when it genuinely needs to, rather than every time you drift a little, and the re-vector itself is more accurate when it does fire. ATC will also no longer read out internal vector points that were never meant to be spoken aloud. e[1mWe need as many different vector-style flights as you can throw at thise[0m, so please report anything that still loops or wanders.
e[1;35m Charted Missed Approaches On Go-Arounde[0m
Go-arounds now fly the published missed approach procedure when the approach has one, and fall back to the existing vector path when it doesn’t. The procedure is flown from the missed approach point and every part of it is applied: the climb-to altitude, the rest of the legs, the lot. The vectored path back onto final has also been smoothed out.
e[1;35m Duplicate & Conflicting Radio Frequenciese[0m
Sim scenery hands us duplicate and clashing radio frequencies at a lot of airports, and that has been quietly breaking tuning for you and for the AI. Conflicting frequencies are now properly deduplicated, which clears out a whole family of long-standing problems:
Fixed not being able to tune Center when a ground frequency shares the same number. This hit both IFR and VFR.
Fixed duplicate Clearance and Ground frequencies from the sim leaving you and the traffic unable to tune up or ask for clearance at all.
Fixed the Clearance frequency going missing entirely when it clashes with a Center frequency, YSSY being the obvious one.
Fixed a regression where custom ops data was being ignored for frequencies that conflict with broadcast frequencies from the sim.
e[1;34m Arrivals & Descentse[0m
Fixed arrivals with no STAR whose route runs direct to an initial approach fix. This was breaking the arrival logic outright.
Added a fallback top of descent calculation so very short routes can no longer fail to produce a TOD point at all.
ICAO: asking for descent before the point you were told to expect the STAR now gets you the STAR and runway in the controller’s reply.
Fixed the timing and the wording of the direct-to-airport call. It now says “after WAYPOINT direct AIRPORT”, which is the call you get when your last route waypoint sits a huge distance from the airport and you have no STAR.
Closed an edge case on a visual approach where you would not get handed off to tower.
e[1;34m Traffice[0m
Fixed traffic leaving some runway turnoffs far too early. Exits should now be much closer to reality across the board.
CRJ1 and CRJ2 now fall back to a CRJ7 rather than a business jet when you have no matching model installed.
Fixed a fatal error that could occur if a traffic aircraft was removed mid-transmission.
e[1;34m Toolbar 3.1e[0m
Auto Tune and Auto Respond settings are now remembered.
COM1 and COM2 name layout redesigned to be clearer and more readable.
Fixed showing and hiding the toolbar cutting off the bottom of the panel.
More adjustments to stop options and actions drawing over each other when the toolbar is small.
The BeyondATC library page now shows the correct version.
Added a note that ‘e[1mATC Panel Choice 0e[0m’ is the binding to use to show and hide the toolbar.
e[1;34m VFRe[0m
e[1mNew US flight following flowe[0m. The button is now ‘VFR Request’ rather than ‘Request Flight Following’, with the actual ‘Request Flight Following’ call coming once ATC is ready for you to state your request. This matches the real-world flow far more closely and should be much less confusing for US VFR pilots.
e[1mUSe[0m: Class D fields now respect their parent airspace for the flight following handoff instead of a set range limit, so using FF with a departure controller you will be handed off at the airspace boundary much more reliably.
e[1mUSe[0m: Requesting flight following from outside a controller’s airspace is now rejected.
e[1mAustraliae[0m: asking for a “stop and go” was being heard as a full stop.
e[1mAustraliae[0m: the intention you state on downwind now overrides the previous one when flying multiple circuits.
e[1mGlobale[0m: opposite orbit circuit direction is now respected when the circuit is right hand.
Fixed a chance that asking verbally for circuits would trigger a VFR departure instead.
Added 122.950 and 123.050 as UNICOM frequencies.
Fixed QNH and Altimeter being read together in some VFR scripts.
e[1;34m Traffic Mape[0m
The map now uses vector-based tiles, so it stays sharp at every zoom level, and the tile error some of you were hitting is gone.
Centring on the player now centres in the visible part of the map pane rather than behind the status display.
Town, state and country labels are more transparent so they no longer fight with traffic data.
e[1;34m Weathere[0m
Added an additional fallback METAR source. Airports with no real METAR available now get one generated via met.no, rather than no weather at all.
e[1;34m Voices & Pronunciatione[0m
Premium voice changes for China, Korea and the Philippines.
Latest airline and pronunciation data.
e[1;34m Interfacee[0m
Actions that contain submenus now show a ‘..’ after the action name, so you can tell there is more behind them.
e[1;34m Other Fixese[0m
Canada no longer uses QNH, and now uses the correct altimeter phraseology for the region.
Fixed a crash when broken scenery delivers an empty traffic scenery file.
e[1;34m Roadmape[0m
The roadmap has been brought up to date with where the product actually is and what is planned next. Worth a read.
e[1;34m Ops Updatese[0m
KPDX, NZCH, NZNR, YBTL
We plan to push this build to EA branch in the next 48 hours.
I just want to say big thanks too the BATC team, the last update on Experimental and the current state of VFR gives me the best ever experience on MSFS ever. I play MSFS since the early days, but this dense airspace and traffic feeling is great and I want to give credit to the team.
Best spend MSFS money ever, can’t expect what feeling stage 3 of VFR will give.
I agree VFR is already great, and even though there’s no VFR traffic yet you still get the feeling of flying through busy airspace thanks to all the IFR traffic. The only missing part is VFR traffic landing at smaller airports, flying circuits etc. to make the world feel even more alive.
I also appreciate that you don’t have to plan your VFR flights in Simbrief. You can just quickly put your starting and landing airport directly in MSFS, making short VFR hops fast and easy to set up.
My only wish (with winter and worse weather coming up in the northern hemisphere) would be to load weather files (.wpr files) or custom Metar into BATC instead of relying on real-time weather. It’s going to get harder to actually find VFR weather to fly in by the time Stage 3 rolls out.