AVCS4 Immersive Voice Control Radios for VoiceAttack
-
*Originally, this was designed for Falcon BMS version 4.34 - since then, it has always been and will continue to be updated to work with the latest version of Falcon BMS. Pro tip: never include a game version in URL’s or graphics
Profile for VoiceAttack
by =VG= SemlerPDXDescription: These commands use VoiceAttack to translate the in-game on-screen radio menus from AWACS through Tanker into natural and intelligent voice command phrases that will fire keypress macros to help keep hands on the throttle and stick, and maintain immersion. As an additional option, these commands can be locked behind a push-to-talk mode bound to your UHF/VHF transmit buttons in-game, allowing any other VoiceAttack command unrestricted access if needed, while still restricting these BMS radio command macros. Finally, this single advanced control profile is extremely easy to edit or integrate into other profiles.
At VETERANS-GAMING, we fly with friends or AI Pilots, or a mix of both on our 24/7 Public Korean Campaign in Falcon BMS. We may go out with an AI wingman only to have a friend take their place mid-flight. For this reason and others, I created this VoiceAttack profile based around restricting when the computer can execute keypress macros that match voice phrases, having to first check if that pilot was set to a human pilot and therefore disregard commands for that pilot.
Thanks to user requests during the beta, there is now an optional mode to reverse the Human Pilots system, to assume all pilots are humans unless told otherwise, and also a system to choose a different keyboard layout than QWERTY. I have also added an optional Audio Feedback Mode to play a short radio cue sound when a command is successfully recognized.
Included is a single profile that handles every callsign and radio command variation in Falcon BMS, with voice commands to add any custom callsigns to the single profile, or edit the list. The focus of this profile is only on the in-game Radio Menus, and creating an immersive interaction layer through VoiceAttack that is easy to manage and update, or integrate into other Voice Control systems for Falcon BMS. The Quick Command Creator system allows creating new simple keypress commands or multi-keypress macros with simple pop-up input boxes guiding users through the process - a great way to add new commands on the fly, or new command phrases to call existing commands.
My goal was an intuitive system, so there is no user manual - only a few infographics and quick reference pic of all the radio commands - say, “Open the Command Reference”, anytime to view available voice commands and the reference pic, including those from AVCS CORE. I intend to release information pages for profile customization and configuration in the VG Wiki on our website, and these will be available through a patch update later for new voice commands or additional options in the Help Menu once complete.
Say goodbye to the keyboard, and enjoy the immersion! Cheers!
Features:
Push-To-Talk mode disabled by default. Say, “Turn On Push To Talk Mode” to enableDownload: (Click Here)
NOTE: DON’T USE THE VA OPTION “Allow Command Segment Info for Composite Commands” w/ AVCS4, and disable before importing AVCS4 if this setting is enabled!
Commands Reference:
Replace the word “Human” with “Computer” when All-Humans Mode is ON
Normally, this profile assumes all pilots are Computers, use All-Humans Mode to invert thisSay, ‘Open the Command Reference’, anytime to view available voice commands, including those from AVCS CORE
Public Release AVCS4 BMS v1.43 Changelog October-25-2023 This is a Major Profile Update, and requires downloading and importing the latest AVCS4 BMS Radios (v1.43) profile for VoiceAttack: New Commands: -Combat Management 4 Page commands "Current Altitude Attack" -Combat Management 4 Page commands "High Attack" -Combat Management 4 Page commands "Low Attack" -Combat Management 4 Page commands "Dive Attack" -Combat Management 4 Page commands "Pop Up Attack" -Combat Management 4 Page commands "Free Attack" Note: This is a new page for Wingman, Element, and Flight; these must be preceeded by who you are talking to Fixes/Improvements: -Added Combat Management 4 Page category in profile to accommodate these new commands
Patch Update AVCS4 BMS v1.42.2 Changelog March-6-2023 This is a simple Live Update patch fix, no new profile download is required - the following fix applies to this update: NOTE: Just (another) small oversight on my part, I had re-edited a file and forgot to re-apply these changes. Huge thanks to CriticalMass for pointing out exactly where the problem lies. I honestly had changed this and noted it in my changelog when I did, but then I didn't re-apply it to the matching database file ..oops Fixes/Improvements: -(FIXED) Moved remaining pages "Common", "Carrier", and "Contingencies" to incremented pages after Departure Page
Patch Update AVCS4 BMS v1.42.1 Changelog March-5-2023 This is a simple Live Update patch fix, no new profile download is required - the following fix applies to this update: NOTE: Just a small oversight on my part, I had forgotten to add these options to the config Fixes/Improvements: -Old Approach command phrases including "Vectors For" ... have been augmented -Can now say, "Request Instrument Approach" OR "Request Vectors For Instrument Approach" (for example)
Public Release AVCS4 BMS v1.42 Changelog March-5-2023 This is a Major Profile Update, and requires downloading and importing the latest AVCS4 BMS Radios (v1.42) profile for VoiceAttack: New Commands: -Approach 1 Page commands "Request Visual Approach Heavy" -Approach 1 Page commands "Request Instrument Approach Heavy" -Approach 1 Page commands "Request Unrestricted Approach Heavy" -Approach 2 Page commands added "Approach Declare Emergency" formerly on Approach 1 page -Approach 2 Page commands added "Approach Abort" formerly on Approach 1 page -Approach 2 Page commands added "Traffic In Sight" formerly on Approach 1 page -Approach 2 Page commands added "Approach Say Again" formerly on Approach 1 page Fixes/Improvements: -Added ATC Page 4 as "Approach 2 Page" to accommodate approach commands "Heavy" on ATC Page 3 -Moved Departure Page commands to ATC Page 5, formerly on ATC Page 4 -Moved remaining pages "Common", "Carrier", and "Contingencies" to incremented pages after Departure Page -Fixed ATC Commands starting with "Request" and missing option for "Requesting" -- added variants in avcs_bms_data_3.cfg file
Public Release AVCS4 BMS v1.41 Changelog Aug-9-2022 This is a Major Profile Update, and requires downloading and importing the latest AVCS4 BMS Radios (v1.41) profile for VoiceAttack: New Commands: -JTAC Radio Menu Page command "JTAC Say Again" -Combat Management 1 Page commands "Weapons Free AA/AG" -Combat Management 2 Page commands added "Go Shooter/Cover" formerly on Combat Management 1 page Fixes/Improvements: -Minimum VoiceAttack program version requirement updated to 1.10.3 -New JTAC Radio Commands introduced in BMS 4.36.0 will now function properly for users of non-QWERTY style keyboards -Former "Weapons Free" command will function same as "Weapons Free AA" -Added two ways to call the new Weapons Free for AA/Ground: "Air Weapons Free" or "Weapons Free Air", format accepted for either -NOTE: New "Say Again" and "Check In/Out" commands under JTAC Menu must be preceeded by the word "JTAC"
Public Release AVCS4 BMS v1.40 Changelog May-11-2021 This is a Major Profile Update, and requires downloading and importing the latest AVCS4 BMS Radios (v1.40) and AVCS CORE (v1.0) profiles: New Commands: -"Open the Command Reference" (or variations - open up-to-date command reference page online, or last updated reference file locally if offline) -"Set a Computer Name" (or variations - set a 'Computer' Assistant name for AVCS PTT mode, say before any command to wake listening temporarily) -"Set a Push to Talk Button" (or variations - set up to 6 total keyboard, mouse, or joystick buttons through automated script - just press when asked) Fixes/Improvements: -Improved PTT (Push to Talk) Mode with voice controlled automated key/button detection during "Set" command -Added PTT Modes (chosen during "Set" command) for game/QCC commands only (default), or toggle VoiceAttack Global Listening Mode -Added PTT Mode 'Wake' by 'Computer' Assistant Name - set a name to say before any existing command to temporarily wake Global Listening Mode -Added Profile Misc. Commands to QCC, allows new commands or macros to be added via Live Update Patch Fix to CORE or AVCS4 profiles between major updates if needed -Added requirement to Include AVCS CORE Profile Commands through AVCS4 BMS Profile Options, instructions provided during first-time init -Fixed International Decimals - All Decimal Variables finally compatible for international users via cultural identification fix during init -Fixed Issue where user was asked to set Keyboard type more than once during first few profile uses, even when already saved to file and loaded properly
Patch Release v1.3 Changelog Jan2020 Fixes/Improvements: -Fixed issue with variable conflict for "Ready for Departure" - was pulling new variable from "Carrier Ready for Departure"
Patch Release v1.2 Changelog Dec2019 New Commands: -"Carrier Ready for Departure" : for ATC Page 6, new 7th item added for 4.34 (U1) update Fixes/Improvements: -Added additional recognition words for turning on/off Audio Feedback Mode - "feedback" can now be recognized as "feed back" -Added Null Check on Audio Feedback Stereo Output Channel setting, if saved setting lost, will force user input on profile load -Updated minimum VoiceAttack version to latest release (v1.8.3) for compatibility
Patch Release v1.1 Changelog Nov2019 Fixes/Improvements: -Changed common Send To default from *Falcon BMS* to "Falcon BMS.exe" to avoid conflict with open PDF's, etc. with Falcon BMS in name -Fixed Human/Computer Pilots Registry system - last minute addition of a mode check was to blame, has been removed for now
Final Release v1.0 Changelog Oct2019 New Commands: -Turn On/Off Audio Feedback Mode : Provides sound feedback upon successful recognition of a command (per user request) -Added a non-functional command to help recognize many variations of "Yes" words for the voice confirmations in profile Fixes/Improvements: -New Variable Pause between any keypress/release for adjustment of the time any key is held down, in keypress_variable command. Default is 50ms -New Audio Feedback Mode has custom SFX included, and gives user option of stereo left, right, or center playback for easier distinction -New Speech notification on startup for Audio Feedback Mode (if enabled) -Speech notifications on startup for PTT mode and All-Humans mode (if enabled) have been greatly shortened. -Fixed issues with being able to set Humans in Computer Pilots mode and vice versa
Beta v0.99 Changelog Jul2019 New Commands: -Change Default Keyboard Layout allows choices between QWERTY, QWERTZ, & AZERTY (per user request) -Turn On/Off All-Humans Mode : Reverse mode assumes all pilots are humans, add Computer Pilots individually as needed (per user request) -Copy of all Add/Remove Human Pilots commands for Computer Pilots & All-Humans Mode Fixes/Improvements: -Can state an entire callsign plus flight & wing numbers when asked for Callsign (per user request to speed up the voice system interaction of adding/removing human pilots) -VoiceAttack log entries displays profile information on startup (current keyboard layout, push-to-talk mode on/off state, All-Humans mode on/off state) (per user request) -Speech notifications on startup for PTT mode and All-Humans mode if they are enabled (see above) -Forced profile initialization if not initialized on any command use (per bug report: on first download/import of profile, trying to use any command fails until voiceattack restarted)
(more that one user has been a bit confused by my AVCS4 PTT Mode in the past, I’m glad to report that now you can just, “Set a Push to Talk Button”, or “Edit Push to Talk Buttons” - you can even set the PTT mode to ‘Global’ in AVCS4 BMS v1.40!)
-
Looks promising. I need to try that out
Thank you for your efforts and for the community ! -
me too
-
This is amazing, thank you for sharing this!
-
Very Performing Profile. I Have used it since 0.98 version. Thanks so much for sharing
Windblow
-
This has been my VA profile for months, since 0.98 as well. IMO it is the most flexible I’ve found to date. Great work!!!
-
Thanks for sharing!
-
I just tried this profile and it looks like only the first keypress is sent to the correct BMS window whenever a command is activated. The mouse cursor appears on the BMS main window but no other menu actions are taken, only when I hit ESC a couple of times the correct initial menu is displayed.
I’ve tried both “Active Window” and “Falcon BMS” as keypress targets, other VAC profiles I’ve been playing around with (latest versions) don’t have this problem.
I’m using display extraction but that shouldn’t be a problem, right?
Thanks for sharing your work & all the best,
Uwe
-
I’m gonna keep trying to look into this, because I don’t have that issue, and have not heard it come up in testing yet (since May). I use display extraction as well.
A few questions come to mind, though I understand you’ve tried several good ideas already:
-We’re talking about keypress targets globally through the Profile Options, right? (just to verify not on the command level – default is Falcon BMS for wildcard name capture)
-Are you running VoiceAttack as Administrator? (this may be required for certain things)
-Are you running any Plugins that may interfere? (disabling any/all plugins for a troubleshoot test would be advised)
-Are the keypresses correct for your setup? (pressing 1-9 to select the radio menu items, and the appropriate QWERTY or alternate keyboard layout)You can test by turning off any focus targets and opening something like Notepad and calling a command. A correct command for ‘Flight Go Spread’ should look like: rrrrr6
Finally, if it is a timing thing, you can adjust the time any keypress is held down as well as the time between any keypresses throughout the profile with the two decimal variables labeled in the KEYPRESS_Variables command. They are at a default of 50 milliseconds, and you can try doubling that for a test to slow down the action of all commands.
//Pause Variables for Macros (default: 0.05 (round to 3 decimal places)) Set decimal [TimeBetweenKeys] value to 0.05 (round to 3 decimal places) Set decimal [TimeKeyIsHeldDown] value to 0.05 (round to 3 decimal places) ```^Change them to 0.10 for that test, should be slow enough for any PC that way… Whatever you test, you should only change one thing and then try it. Instant Action should be fine for some quick testing. If none of this works, post up and we can look deeper. We'll figure it out, trust me. It's something simple, surely. *see reference pics, some are about troubleshooting from the beta, I added one more for this: [https://imgur.com/a/xuclI0a](https://imgur.com/a/xuclI0a)
-
I just tried this profile and it looks like only the first keypress is sent to the correct BMS window whenever a command is activated. The mouse cursor appears on the BMS main window but no other menu actions are taken, only when I hit ESC a couple of times the correct initial menu is displayed.
I’ve tried both “Active Window” and “Falcon BMS” as keypress targets, other VAC profiles I’ve been playing around with (latest versions) don’t have this problem.
I’m using display extraction but that shouldn’t be a problem, right?
Thanks for sharing your work & all the best,
Uwe
display extraction is an issue if your using BMS to do it. This is because the Profile targets Falcon BMS and when you extract using just BMS it creates a separate sub-process for each extraction so the VA profile doesn’t know exactly which one to send it to. I got around this issue by targeting the actual process name Falcon BMS.exe, so no wild cards for the target. You can also just use Yame or some other extraction tool that doesn’t create multiple Falcon BMS windows.
-
Thanks all for your suggestions, I’ll give them a go later and report back.
I’ve been a long time YAME user but I’ve been having issues since 4.34 so I had to revert to BMS’ native extraction method for now until the 2.0 branch comes out of beta testing.
All the best,
Uwe
-
Hm, I just tried “select your own target” and entered
Falcon BMS.exe
in the text box, but behaviour in BMS still is the same. When VAC recognizes the first part of a command (say, “wingman”), the mouse cursor appears but all following key input is lost and the comms menu only appears once I re-focus the BMS window by clicking into it. I’m testing this on win7 if this makes any difference.
Thanks again & all the best, Uwe
EDIT: I’m running BMS in “-window” mode.
-
Hm, I just tried “select your own target” and entered
Falcon BMS.exe
in the text box, but behaviour in BMS still is the same. When VAC recognizes the first part of a command (say, “wingman”), the mouse cursor appears but all following key input is lost and the comms menu only appears once I re-focus the BMS window by clicking into it. I’m testing this on win7 if this makes any difference.
Thanks again & all the best, Uwe
EDIT: I’m running BMS in “-window” mode.
I’m pretty confident its the BMS extraction issue. turn extraction off in BMS. If it works that way the RTT extraction tools work just as a good as BMS extraction if not slightly better.
-
Also changing the key delays and timing didn’t change anything. I wonder though why other VAC profiles I’m using do not exhibit this peculiar behaviour?
Thanks again & all the best,
Uwe
-
Just did a test using the “active window” and notepad++, this doesn’t work either. (see screenshot below)
All the best,
Uwe
EDIT: Using the BMS 4.34 single callsign profile, I can send keypresses to notepad++ just fine.
-
Hi folks, I think I fixed the issue by explicitly disabling the “send to” setting in the “profile options” as the error message indicated (seems it’s not just enough to enter the target in VAC’s main window dropdown).
Now everything apparently works fine. Thanks again for your support & for this excellent profile!
Uwe
-
Hi folks, I think I fixed the issue by explicitly disabling the “send to” setting in the “profile options” as the error message indicated (seems it’s not just enough to enter the target in VAC’s main window dropdown).
Now everything apparently works fine. Thanks again for your support & for this excellent profile!
Uwe
I also had/had this issue, except my voice command was sending it to anything that had “Falcon BMS” in the title, including tabs in Acrobat Reader, my file explorer if the path had “Falcon BMS” in the title - I’ll see later if @hoover’s fix works for me.
-
I’m a little confused about the “All-Human/Computer” aspect. In short, I’m testing as SP and assumed that in “All-Humans Mode is OFF” I could still add a single human player, but it tells me that the mode needs to be ON. But, if I’m in “All-Humans ON” and Remove All, the software explicitly tells me that I can add a single player.
This whole implementation confuses me, I guess because I don’t fully understand the use case.
Thanks in advance for any info.
-
This is a masterpiece. I’ve been testing it for 2 days and it keeps surprising me
I still don’t fully master all functionalities and I don’t quite understand all of it, but I’m getting there.
One particular little issue I have are “wildcards”. The profile works perfectly if I just pronounce the commands exactly as indicated in the Comms menus, but if I try to be creative (e.g. “Falcon 11, Ground, F16 two ships, request taxi for departure”) VA doesn’t recognize the phrase, whereas with “Request taxi for departure”, no problem.
Beats me, but I suppose the issue is on my end. If anyone has ideas… Thanks a lot.Judy
-
This post is deleted!