UOAF Advanced VoiceAttack Profile - Including Ownship Callsigns
-
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! -
Hey, guys, any update available for this awesome VoiceAttack profile??? Thanks!!
-
updated for the new callsign and callsign numbers(1 to 9), still uses the same old commands tho
https://drive.google.com/file/d/1pgxgrssAeJWT8aj8wJ8IMKTB4WJVnXXP/view?usp=share_link
-