Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

BeyondATC Released (EA)

Featured Replies

6 minutes ago, rutrA said:

Minor Update 1.0.23.EA
- Added Premium Irish Voice Set.

- Added more Premium Swedish Voices.

- Added British Avgeek as Co-pilot.

- Added FlyBy Simulations as Co-pilot.

- Added error handling for program crashes.

- Replaced "line up and cleared for takeoff" with "cleared for takeoff".

- Center handoffs say "radar contact" or "identified" in ICAO.

- Continued work on descents and approaches.

It might seem petty, but the fix from "line up and cleared for takeoff" to just "cleared for takeoff" was my top priority.  I'm now about to purchase!

  • Replies 813
  • Views 150.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Stop being so immature. If you don't understand the meaning of "early access" and you start calling the software 'a piece of' because it's not working perfectly a few hours after it released, don't bu

  • eslader
    eslader

    You guys must have all missed the part where the dev put it to a vote and the majority asked them to release early. Several of us said yes, release early but just be prepared for the dogpile of people

  • G550flyer
    G550flyer

    Greetings all, I just wanted to drop a few things after scrolling through this thread😁. When I'm not slipping the surly bonds, I do my secondary job as a product manager doing software development int

On 5/8/2024 at 1:25 AM, flyinion said:

Just a tip for the issue I mentioned a few pages back about a number of us with VKB devices having issues binding a PTT key to them.  One user in the support thread for it in BATC's Discord figured out it was working after they flashed the latest VKB firmware release from September.  I tried it as well on my Gladiator NXT's and it worked.  Someone with a Gunfighter base also just reported the latest firmware fixed the issue.  So if you're trying to use this with a VKB controller and PTT binding isn't working because it's not recognizing the buttons correctly, check if you need a firmware update.

Well, I tried that with my old Vintage Mamba + Warthog stick. 

Upgrading to the latest firmware and the warthog's buttons aren't working any more. Tried downgrading... and now the entire shebang isn't recognized by the VKB util. Not amused...

Edit: turns out the culprit wasn't even the stick but the STECS throttle lol. All is well, I was able to put it all back in working order.

Edited by iborg1979
update

spacer.png5800X3D, 64GB 3200 RAM, 7900 XT 20GB

1 hour ago, MikeyOnTheFlightDeck said:

It might seem petty, but the fix from "line up and cleared for takeoff" to just "cleared for takeoff" was my top priority.  I'm now about to purchase!

Also glad to see this fixed. A minor thing, but kind of jarring to hear. 

Also, say what you like about the imperfections that the product currently has, but it's impressive to see the rate at which they are putting out updates. They certainly seem to have a solid process for building and pushing updates.

 

On 5/8/2024 at 11:14 PM, Speedbird 217 said:

Pleased to report that the latest update (1.0.21.EA) seems to have improved things significantly regarding descent clearances.
Just flew into EGLL and was correctly cleared along the STAR to the correct altitudes before indirectly being cleared to the FAF altitude when getting ILS clearance. First time this has happened to me after 8 flights, previously it was always just the first STAR altitude and then nothing until much, much later.

Hopefully not just a one off, but this was the first flight gate to gate without any issues. 

I'm not entirely sure if this is different in Europe, but ATC doesn't clear you to every single altitude on the STAR. They will give you a bottom altitude to maintain at the end of the STAR and tell you to descend via the STAR where you're responsible for adhering to the constraints yourself, or an altitude separate from any STAR constraints due to traffic etc.

Virtually all ATC addons do this for some reason, but it's not correct. Incidentally, on my first and only flight with BATC so far I reported ready for descent and it cleared me to descend via the STAR without giving any clearances to the altitude constraints throughout (which is correct).

BTW, as discussed earlier, under ICAO rules an ILS clearance isn't to be understood as a descent clearance to the first fix or the FAF. That should be separate.

Great to see another update - it's coming along nicely and my last few flights the descent clearances have worked perfectly each time.

Me: "Fort Worth Center, you suck."

BATC: "Aircraft calling on frequency, that's inappropriate. Get off the radio." :biggrin:

(Just wasting my premium characters)

Edited by threexgreen

Is there a trial version available?   Can we still use FSLTL with this?  Apologies if these have been asked and answered.

There is no trial version, however plenty of YouTube videos that give a very good idea of how it works and its current limitations. You can still use FSLTL, but and a BIG but, BATC currently has no interaction with any injected traffic. So expect running into other aircraft doing their own thing!

Edited by Dusk

System 1: AMD Ryzen 9 5950X @ 4.2GHz, 2x16GB DDR4 2600MHz CL18 RAM, EVGA RTX 3090 FTW, Samsung 840 Pro SSD 1TB, Samsung 840 Pro SSD 512GB, Seagate 2TB HDD, Windows 11 Pro 64bit, Thrustmaster Hotas Warthog.

System 2: AMD Ryzen 9 9950X3D @ 5.7GHz, 2 x 32GB DDR5 6000MHz CL30 RAM, ASUS ROG ASTRAL RTX5090 OC, 2 x 4TB Lexar NM790 M.2 PCIe 4.0, Crucial T705 2TB Gen5 M.2, Samsung 840 Pro SSD 1TB, Moza AB9 with Thrustmaster Hotas Warthog Flight Stick, Winwing Orion Rudder Pedals, Thrustmaster Hotas Warthog Throttle Quadrant.

Well, finally managed to register at Revolut, got a virtual CC and was ready to fly with BATC in minutes. Glad to have that problem out of the way...!

First flight in Norway went almost perfect. Norway is a easy country for BATC with its neat and tidy procedures. Only little odd thing was that ATC told me to descent to 2000 ft just a few seconds before it cleared me for the approach at 3600. But nothing I couldn't handle. I didn't even have to do anything special to avoid or prevent problems with BATC...!

1 minute ago, Dusk said:

There is no trail version, however plenty of YouTube videos that give a very good idea of how it works and its current limitations. You can still use FSLTL, but and a BIG but, BATC currently has no interaction with any injected traffic. So expect running into other aircraft doing their own thing!

Thousands of flights, using PF3 ATC and have yet to run into another aircraft???? I just don't have FSLTL launching hundreds of flights around me. I would suspect that using BATC would produce similar results. 

Edited by Bobsk8

 

 

 

Wasn't suggesting it would be common, but was just emphasising the point that it could happen on occasion. 

I also have not had the situation as yet. And you are right limiting the traffic is probably the key. 

Edited by Dusk

System 1: AMD Ryzen 9 5950X @ 4.2GHz, 2x16GB DDR4 2600MHz CL18 RAM, EVGA RTX 3090 FTW, Samsung 840 Pro SSD 1TB, Samsung 840 Pro SSD 512GB, Seagate 2TB HDD, Windows 11 Pro 64bit, Thrustmaster Hotas Warthog.

System 2: AMD Ryzen 9 9950X3D @ 5.7GHz, 2 x 32GB DDR5 6000MHz CL30 RAM, ASUS ROG ASTRAL RTX5090 OC, 2 x 4TB Lexar NM790 M.2 PCIe 4.0, Crucial T705 2TB Gen5 M.2, Samsung 840 Pro SSD 1TB, Moza AB9 with Thrustmaster Hotas Warthog Flight Stick, Winwing Orion Rudder Pedals, Thrustmaster Hotas Warthog Throttle Quadrant.

13 minutes ago, tup61 said:

Well, finally managed to register at Revolut, got a virtual CC and was ready to fly with BATC in minutes. Glad to have that problem out of the way...!

First flight in Norway went almost perfect. Norway is a easy country for BATC with its neat and tidy procedures. Only little odd thing was that ATC told me to descent to 2000 ft just a few seconds before it cleared me for the approach at 3600. But nothing I couldn't handle. I didn't even have to do anything special to avoid or prevent problems with BATC...!

Sounds like it's already come some way since you exited the beta then?

1 hour ago, Speedbird 217 said:

Sounds like it's already come some way since you exited the beta then?

Hm... perhapts... Only did 2 flights yet. Flying in Norway always worked well already (you never get vectored there, which helps, haha!). The second flight was in England and the departure vector was okay (improvement!) and the vectors for final were also nice (though I was cleared for the ILS a bit too late making me overshoot the LOC but I already anticipated that... but of course anticipation shouldn't be needed 😉 ). I also like the new Toggle Bring to Front option and that you can disable odd accents with Basic voices.

All in all it seems better than when I left the beta but I am still reading about a lot of problems on Discord which remind me of beta very much.

Still, it's nice being able to use BATC again because I like the interface and how things work and the phraseology usually is quite realistic.

I am off for a flight in France now: let's see how it goes.

The problem I'm having with BATC is that when using the 'co-pilot responds and changes frequency' option, there is a delay (a minute or more) between the co-pilot responding to an ATC hand-off, and then changing the frequency, and then calling on the new frequency. SI is a greyhound in comparison.

 

Edited by Petraeus

Petraeus

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.