UOAF Advanced VoiceAttack Profile - Including Ownship Callsigns
-
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 -
Please read the Readme.txt in the download.
The profile is designed to be used in Always Listen mode. There is no need to use PTT assignments in VA. Just make sure to use the settings in the Readme and it will pick up the commands you use.
The only things you need to worry about are COMMS UP/DOWN binds in BMS, which activate your UHF and VHF radio PTT, respectively. You don’t need to use them for VA to work, but you will need them to speak on UHF and VHF during MP sessions, which is the primary purpose of this profile.
-
I noticed an error in all commands including player “[<callsign>] [1…4;] [1…4;]” in them. Other than the fact, that limiting the range for the first digit to 1-4 is wrong (BMS uses 1-9), the “[1…4;] [1…4;]” part is invalid VA syntax - in fact those commands are impossible to edit without removing trailing semicolon from one of them (VA throws error when confirming changes), because they produce duplicate entries - omitting first number and not the latter produces an identical command to keeping the former and selecting the same number in the latter. I’m actually curious how you even managed to create those commands in the first place without VA throwing a fit.</callsign>
-
This post is deleted!