I think the guy upthread who commented about how often he had to switch frequencies along his route when using BATC vs. VATSIM says it all about VATSIM. You hardly ever have to switch frequencies in VATSIM because there’s rarely more than one controller online. BATC is already more realistic in that regard.
3 Likes
Very funny? If I bought it and experienced what you did I’d be fuming. After reading several pages of this thread I will stick to default ATC for a bit longer. You had more issues with BATC in one flight than I did in last 20 flights with default one. I understand it’s early access but the issues reported by some people are startling.
1 Like
Some people just need good glasses to clearly see that it’s an early access and just like to complain 
3 Likes
It’s not good enough for an early access if the approach and landing guidance is so far off.
1 Like
Hi there,
I went ahead and purchased the BATC yesterday… I have a question, how do you guys switch the Simbrief Flight Plans, as I have a couple of plans that I would like to use, Any help is greatly appreciated. TIA
1 Like
If you’re asking what I think you’re asking (if you have several flights saved in SimBrief and you want to “activate” one) then it looks like you have to select it from your list of flights and “Generate” it (the button at the top left). That should make it the active flight plan.
3 Likes
Curious if this vector to approach issue some are having are primarily in Europe ATC areas? I just did a Denver to Tulsa and they vectored me perfectly… Tulsa isn’t a huge airport by any imagination, so was pleasantly surprised.
I have no doubts BATC is going to get the vectoring figured out. I am LOVING this add-on, has brought so much fun back to the sim!
I flown 4 times on pmdg 737-800 using BATC and not once was the approach far off in any way. Everything worked accordingly. I may experience an off approach at one point but so far it has worked as it should.
Still weirdness on approaches without “vias”. Here’s an example from a few minutes ago, in a Fenix A320 FWIW.
Flew into KPDX Portland TMBRS2 Arrival, Runway 28L. Transcript and map below. You can see that instead of turning me on a downwind hdg 102 towards ICEAX, it said to “leave ROAGE at heading 355…” then 330, then report field in sight. It didn’t give me descent instructions, so was stuck at 5000 feet. I had ILS tuned, and was quite a bit too high, but was able to manually descend at like 2000 fpm to get on glideslope and land.
Again, still understand that this a work in progress, but I might start ignoring instructions and doing my own vectoring/descending.
Oh, as an aside, logs and other goodies can be found in C:\Users<username>\AppData\LocalLow\Skirmish Mode Games, Inc\BeyondATC
Transcript:
Jetblue 28, Portland Approach, A30.00 expect the visual approach runway 28L.
Jetblue 28, leave ROAGE heading 355, expect radar vectors for visual approach runway 28L.
Jetblue 28, turn left, heading 330, vectors for the approach.
Jetblue 28, airport is at your 10 o’ clock 16 miles. Report the field in sight.
Jetblue 28, cleared visual approach runway 28L.
Thanks for pointing that out. It is a small link under the big button on Unlimited access; completely missed it.
It is reasonably priced and I now have that.
I think its to do with the STAR. There was a FL070 constraints and the ILS platform altitude was 4000ft. I suspect the way it vectored me was in part to allow me more time to get to platform (I was in an ATR). I had one other set of vectors for an approach to EGBB that had me do a 360. Now that was definately to allow me more time descend. I’ve had plenty of other flights where the vectoring was fine.
The logic involved is probably quite complex with a number of interacting varibale at work.
Given that I have already been using FSHUD for a few months, yesterday I took two flights with BATC.
I also activated FSLTL together and they were two practically perfect flights with the Fenix.
Only problem, to free the GATE occupied by the AI plane I had to deactivate FSLTL one minute before parking.
I also flew with the ATC of the SIM, but software like FSHUD or BATC are a completely different matter.
1 Like
Another update today. The speed and ammount of updates to solve problems is incredible. Hats off to these guys.
5 Likes
Latest update today caused my alpha yoke press to talk button to stop working. Assigns OK but does not work. Assigning a keyboard button works fine.
Anyone else?
1 Like
I noticed when I updated that my mappings had been cleared after the update. Just go into the Options and remap it.
You need to remap your press to talk button assignment. Not that big of deal for me. I expect changes and updates while in this pre-release state. In this case BeyondATC put more mapping features in their tool. I really enjoy this product.
I had the same problem on my flightstick. Re-mapping assigned the button again but still wouldn’t work. Had to assign a keyboard key in the end which worked ok.
1 Like
Does anyone know if there are any change logs? Discord is not playing nice with me lol.
Known issue that they are working on.
1 Like
From Discord:
Minor Update: 1.0.18.EA
Lots of fixes for voice recognition and spoken instructions not being understood.
Added a new option to have BATC prefer virtual airlines if the VA shares the same ICAO code as an IRL airline.
Added option to force Basic Voice Model to use english-based speech. Use this if you were finding it difficult to understand some accents when using the Basic Voice Model.
“Toggle Always on Top” button changed to “Toggle Bring to Front” - when assigned and invoked will cause the application to display itself above all other applications and give it focus. Pressing the button again will send it back below other applications. Useful if you only have one monitor.
Additional fixes with flight plans, routes and TOD calculations.
We are aware of the connect to sim errors and are working on addressing these issues as our top priority.
4 Likes