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.

SpamPilot

Members
  • Joined

  • Last visited

Everything posted by SpamPilot

  1. I greatly appreciate the time you took to respond. Thank you.I did look into the XML syntax files to see if anything could be customized, but they are for the voice trainer. They don't have anything to do with in-game interaction."after thinking on the matter that the UI choice is to either allow nn retries"Agreed, though that wasn't actually my point. VoxATC is recognizing speech, but only just enough to know if you spoke one of the things it displays in its short list. So it's not much more engaging than a phone tree. When I can fly without a flight plan (or on a diversion), tune in a nearby tower, and spontaneously call "Foofield Tower, Cessna 0000X, ten miles North, inbound for the option, with Bravo", and Foofield Tower responds, then I will be a happy customer. Actually, even if I were limited to simply saying "Foofield Tower, Cessna 0000X", and up pops up a list of a few things I can say to that tower, that would also make me happy, particularly if I can also tune any nearby ATIS/AWOS while enroute.I guess I still haven't warmed up to VoxATC just yet.
  2. VoxATC doesn't seem to handle some phraseology correctly. Is anyone else annoyed by this?Standard phraseology for an initial contact goes like this:1. Who you are talking to2. Who you are3. Where you are4. What you wantSo when I make my first call to request taxi for takeoff to do pattern work, I am expecting to call as follows:"Renton Ground, Cessna 0000X, at parking, taxi for takeoff, closed pattern, with Bravo"This works in real life, but doesn't work with VoxATC. VoxATC wants to hear this:"Renton Ground, Cessna 0000X, request taxi for pattern"That's not standard phraseology. What happened to 3 "Where you are"? Additionally, why can't I say "taxi for takeoff, closed pattern", or "with Bravo"?If I want to go on a local flight, in real life I would request "taxi for takeoff" or "taxi to the active" or "taxi to 33", not "taxi for local" the way VoxATC makes me say it.When VoxATC Ground gives me my taxi instructions, I am supposed to read back:"Taxi to Runway 33 via Alpha, Delta, Kilo, and Bravo altimeter 2991 Cessna 00X"Normally, Ground wouldn't give me an altimeter reading (I earlier told them I had information Bravo). Also, that's a bizarre taxi sequence - the correct sequence is simply "via Alpha" - but that's a subject for a different post.On readback I would simply say "Taxi to 33" instead of "Taxi to Runway 33". But VoxATC can't handle those variations.Merely reading what VoxATC puts up in its window into the microphone (and having it accepted on the second try no matter what I say) is, IMO, a pretty shallow user experience. Surely it wouldn't be *that* hard to parse what actually comes in from the speech recognizer and fit it to one of a few patterns to allow for more flexibility. Or even expose the grammar in XML files so volunteers in the community could improve this.

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.