UOAF Advanced VoiceAttack Profile - Including Ownship Callsigns
-
Hi All!
I’m pleased to present the UOAF Advanced VoiceAttack Profile Pack for BMS 4.34.
This profile has been in process for a while now and draws from the work of several people at UOAF, as well as utilizing Easy’s python script for batch profile generation. A big thanks to those who helped get this ready for distribution.
This is a pack of 22 profiles, one for each possible F-16 flight callsign (Hornet callsigns will require additional profiles). Each profile allows the user to use live radio calls to activate in-game comms menus with the goal of providing seamless use of radios without needing to touch the keyboard. This is particularly applicable to multiplayer environments, but works just as well in single player.
Multiple variations of radio calls and callsigns can be used with no editing required.
Examples:
For Ground - request taxi, you can say…
“Ground, Viper 1 four-ship F-16, request taxi”
“Ground, Viper 2-1, request taxi”
“Ground, Viper 2, request taxi”For Approach - request instrument approach, you can say…
“Approach, Falcon 1 two-ship F-16, request ILS approach”
“Approach, Falcon 2, request instrument approach”
“Approach, Falcon 3-1, request TACAN approach”Please note, there are three “Chief” commands in the place of some of the ground commands:
Install/Remove chocks
Install/remove EPU Safety Pin
Recharge JFSFor more information on features and how to use the profile, please see the two follow-up posts below.
I would strongly recommend taking a look through the profile to see all of the commands and variants. We tried to account for many variations for the various commands, but at the end of the day, it still has limitations.
The only thing we were not able to include to our satisfaction was airbase names. VA will not allow wildcards in suffix/prefix structures, and there are too many airbases to be able to include them all as variants, so it was decided that omitting them entirely would be the better solution. If someone has an idea on how to properly implement airbase names, please feel free to share.
Note: For these profiles, you can leave VA set to “Always Listen”, or you can use PTT and only use it for UHF/VHF radio calls. See the readme.txt for recommended settings.
Change Log:
v1.1 - Bug fixes, minor additional phraseology added
v1.0 - Initial Release -
Special thankyou to Easy as well. I learned from his profile and profile generation python script!
Here are some extra poweruser tips:
A “.vax” is just a bunch of profiles zipped up and renamed to “.vax”
Importing the .vax adds 1 profile per callsign.Say you want to change the wording of a command in all 22 profiles -
- edit just the Viper profile, then export it
- delete all the profiles from VA
However, there is no quick way to delete all 22 profiles from within the UI……
Here is the trick:
Navigate to%AppData%\VoiceAttack ```delete VoiceAttack.dat All profiles are cleared from VA! Now, to create your new set of profiles: 1. place new Viper profile in the same folder as the "CallsignCopyPaste_vax.py" python script. 2. run the script. 3. it generates the new .vax 4. import the vax. Finally, If VA won't let you edit something in a profile because the command contains a "duplicate", just open in Notepad++ and do it manually ;)
-
Some additional explanation picked up on the UOAF discord from Gasman:
And similar to how you send a radio message in real life, the first part of the message:
identify who you are talking to,
then say your callsign,
then say your request- Tower, Viper 1 ready for departure
- Approach, Viper 1 request unrestricted approach
- Ground, Viper 1, request taxi
The flight commands are more abbreviated:
- 2 rejoin
- element, kick out
- Flight, weapons free
- you can also refer to 2 as Viper 2
- Viper 2, ops check
- Viper flight, go trail
to learn exactly what all the commands are, hit the edit button on the right
to see
These are examples of flight command suffixes (this section covers all commands to AI wingmen - flight, 2, & element). Anything that ends with a semicolon is an optional word. If two words/phrases are separated by a semicolon you can use either
example, “say position” command:
[say;] [your;] [position; posit]“say” and “your” are optional, followed by either “position” or “posit” produces the following command variations:
- 2 say position
- 2 say posit
- 2 your position
- 2 your posit
- 2 say your position
- 2 say your posit
- 2 position
- 2 posit
same with “3”, “element”, and “flight”
The prefixes all work the same way, they are under the ‘Callsigns’ category
If I want to call the Element, I can say- cobra 3,
- cobra element,
- 3,
- element,
put a prefix and a suffix together, you have a valid command:
- Cobra 3, say your position
you’ll notice that saying your own callsign is always optional. You can just say “AWACS” if you don’t know if they are “sentry”, “magic” or whatever (at least in my version). Lots of words have semicolons after them, they are optional, so that simple commands should work. Usually if you say exactly what’s in the in-game menu it should work. also, [1…4] means any of a series of all numbers from 1 to 4: 1, 2, 3, or 4
-
Thanks for sharing and documenting! Looks exactly like the thing I should’ve done but didn’t find the time for.
-
Nice !
Where did you take all the BMS callsigns from (folder and file) regarding pilots, AWACS and tankers?
Not the MC ones. -
\Falcon BMS 4.34\Docs\05 Other Documentation\Radiomap.xls
-
Thanks so much for sharing the UOAF profile!
It works well me for me (a complete idiot wrt Voice Attack) in that my commands are invariably recognized in VA, but quite often missed/ ignored in game. Can anyone give advice on the optimal settings in the VA Options page- Recognized Speech Delay and Unrecognized Speech Delay etc? As a novice, I don’t find the VA Help Manual very helpful.
-
The only changes recommended to the settings are included in the Readme. Delay is not on that list, as I’ve left it at default and have no issues.
What do you mean, ignored in game? Are you sure you made the right call?
If the tower isn’t recognizing your calls, it could be because you used the wrong call.
When you’re ready to taxi and say “tower, Goblin 1 request taxi”, VA will recognize the command, but nothing will happen in game because “request taxi” is not a tower command. You need to say “Ground, Goblin 1, request taxi.” -
Thanks for your reply starfuryth. I meant when I test the commands in the VA screen, VA hears them very well, but in BMS I often get ignored. The issue is definitely with ATC and I don’t think its a radio frequency problem. By contrast my wing-man and AWACS coms work very well in BMS.
It may indeed be that I’m not using “approach”/ “tower”/ “ground” correctly, but, if I look at the UOAF profile, the suffix for all ATC commands is “Tower”.
So I should be saying, for example, “Approach request radar approach” as opposed to “Tower request radar approach”. Or perhaps there are other parameters ( bearing /range from runway etc.) that I’m misusing and are causing the problem.
-
All of the ATC comms use the Tower prefix group, but there are different prefixes within that group. As I said, VA will still recognize a command to the wrong ATC authority, it just won’t do anything. Check in notepad to see outputs for different calls.
Ground will be what you use while you’re on UHF 2. Request taxi, ground abort, etc.
Tower will be your realty for departure, takeoff clearance, etc. On UHF 4
Departure will be for reporting airborne on UHF 4.
Approach will be for requesting approach clearance on UHF 4.Full ATC flow would look something like this:
Ground, request taxi.
Ground, say QNH.
Tower, holding short, ready for departure.
Departure, airborne.
Approach, request unrestricted approach.
Tower, request landing.
Tower, on final.
Ground, request taxi back to ramp. -
Thank you for your patience Starfuryth. Looking forward to trying it out.
-
The only thing we were not able to include to our satisfaction was airbase names. VA will not allow wildcards in suffix/prefix structures, and there are too many airbases to be able to include them all as variants, so it was decided that omitting them entirely would be the better solution. If someone has an idea on how to properly implement airbase names, please feel free to share.
There is a way, but not through the UI. You can write custom plugins for VA that enable a wide range of functionality. There’s a VA plugin for DCS called VAICOM which introduces complex PTT functionality (you have to use PTT for the radio that is actually tuned to recipient, you can assign different PTT buttons for different aircraft) and employs full list of callsigns and airbase names, with the ability to actually specify the recipient by callsign. They do that using direct 2 way communication with DCS, skipping the menus.
-
A couple of years ago I printed out the BMS 4.33 Voice Attack Spoken Commands. I have no idea how I did it.
How do I find the List of Voice Attack Commands for 4.34 so that I can print it? Or, is that really needed? Have the commands changed that much from 4.33?
-
There is a way, but not through the UI. You can write custom plugins for VA that enable a wide range of functionality. There’s a VA plugin for DCS called VAICOM which introduces complex PTT functionality (you have to use PTT for the radio that is actually tuned to recipient, you can assign different PTT buttons for different aircraft) and employs full list of callsigns and airbase names, with the ability to actually specify the recipient by callsign. They do that using direct 2 way communication with DCS, skipping the menus.
I’m aware of VAICOM, but that’s DCS, not BMS. It’s also well beyond my ability to design, unfortunately. But if someone else would like to figure out how to do it for BMS, I’d be happy to incorporate it
-
A couple of years ago I printed out the BMS 4.33 Voice Attack Spoken Commands. I have no idea how I did it.
How do I find the List of Voice Attack Commands for 4.34 so that I can print it? Or, is that really needed? Have the commands changed that much from 4.33?
If you’re asking for a list for this specific profile, there isn’t one, partially due to the incredible number of variations in phrases (upwards of 87k variants, iirc).
If you’re asking for a list of basic phrases unique to BMS, please start a new thread.
-
Thanks starfuryth, I did figure out how to print out the commands.
New issue!
When I say “Tower Request Overhead Approach” Voice Attack recognizes it as a derived command, but in the game I don’t get anything. When I say, “Request Landing” it works in the game, but not “Tower Request Overhead Approach.” I have the same problem with other commands as well such as “Tower Request Unrestricted Approach.” So some commands work in the game, and some don’t, even though they are all recognized by Voice Attack.
Any ideas?
-
That’s because you’re addressing the incorrect ATC entity. Approach clearances are granted by ATC Approach, not ATC Tower.
The VA profile recognizes the command, and also recognizes that it’s not a valid command in the game.You need to be saying:
“Approach, Falcon1, request unrestricted approach”Once approach pushes you to tower frequency, you can then switch freqs and use the commands:
Tower, Falcon1, request landing
Tower, Falcon1-1, on finalOnce tower pushes you back to ground, you can switch to ground freq and use:
Ground, Falcon1-1, request taxi back to ramp -
Stunning stuff thanks!
-
Thanks very much! These profiles are great and work very reliably for me, even before I tweaked the VoiceAttack settings as per the README.
-
Ok I am a total rookie on using VA. I downloaded the profile and try to use it with my Warthog but nothing happens. But I am new to VA. I need setup help. I am using a Thrustmaster Warthog.
1. I go into settings and go into Joystick Options and Enable Joystick 1 and Enable POV Switches.
2. Under POV 1 switches what do I select? Also which POV the one on the side of the Throttle or in front? For now I am using the POV on the side for UHF up and VHF down.
3. Hotkeys is set for Push listen Left Alt +F2 do I have to make any changes here? I really don’t understand how this works.
4. Joystick Button Recognition what should I set to? Toggle listening start / stop, VoiceAttack listens while buttons are down or other?
I am using version 1.83 and I am using Alternative Launcher to setup my HOTAS