While discussing the (imho) low support for button users of BATC someone on the BATC Discord said that he thinks the developer probably thinks that 99% of the BATC users use their voice to communicate with ATC and hence don't care about button control. I, as a button only user, beg to differ. Hence this little poll. (A poll on the BATC Discord would probably give a better result but I can't start a poll there.)

To be fair here, BATC was clealy developed from the very start so that you actually talk to ATC. Button usage is just an afterthought.

I only use the buttons if ATC is not understanding me.

Edited January 11, 20251 yr by Farlis

14 minutes ago, mistolip said:

While discussing the (imho) low support for button users of BATC someone on the BATC Discord said that he thinks the developer probably thinks that 99% of the BATC users use their voice to communicate with ATC and hence don't care about button control. I, as a button only user, beg to differ. Hence this little poll. (A poll on the BATC Discord would probably give a better result but I can't start a poll there.)

Since I haven't got a mic hooked up to my PC, I just have to use the buttons. And I am rather satisfied with BATC so far. 

i have only ever used button for comms in batc, be nice to be able to map more more buttons to select more than the top line.

Don't get me wrong, I love it but...

It's canned and its not like we have a lot of choices, so I just press the button instead of pressing the button and talking.

 

It's just a me thing 😉

Buttons only. Kinda ridic to sit on your rickety office chair talking to your monitor. 

🤣

100% Co-Pilot mode.

I use buttons and auto respond.  Especially when flying an airliner I wouldn't be doing most of the talking to ATC IRL.  Plus with buttons, it's never misunderstands me and I don't have to have my wife giving me weird looks for talking to my computer 😉 

It mostly works great though every once and a while I wish there was a few more options like "hey hurry up and clear the next portion of my descent I'm well above profile"

Edited January 11, 20251 yr by regis9

Buttons and auto respond, simple and it works perfectly. 

 

I use a combination of voice, copilot & the buttons.

Button is always useful for the stuff BATC is incapable of understanding - a good one being "Field in Sight" - which it translates as "Field in site" according to the logs, not sure if that one has been fixed though .. .. ..

 

G

Buttons as I simply don't like to talk to my computer.

Family thinks I'm crazy then. Even more 

1 hour ago, Farlis said:

To be fair here, BATC was clearly developed from the very start so that you actually talk to ATC. Button usage is just an afterthought.

I only use the buttons if ATC is not understanding me.

I as well... mainly because if you respond by button you're eating up credits.  But sometimes on longer cruises I will use auto respond and go do something else. 

Interesting results so far...! I started the poll with voice and ended it woth buttons on purpose because I didn't want to steer the voting and also because, indeed, BATC was developed for voice in the first place. But I certainly didn't expect the button users to be in the majority. But well, only 32 votes for now so... we'll see. No matter what: the dev of BATC really needs to pay attention to the button users, that's for sure!

There needs to be an "other" option.  I use a mix of co-pilot, voice, and buttons as needed.  So, none of the four choices listed are accurate for my usage.

 

I only use the buttons - I think of it as my First Officer is handling the radios!