AVCS4 Immersive Voice Control Radios for VoiceAttack
-
@Atlas I believe that the pic of the actual radio menu commands from in-game are the best reference. If you say, “Open the Command Reference”, and scroll down past the AVCS CORE (included commands) section to the BMS section, you’ll see a number of commands in their raw dynamic format, though others are presented in a simplified format of the key word(s) only. This is because there are upwards of 250,000 dynamic phrase variations at times for just one command, for example, which would be quite difficult and unreadable to format in any other way. On top of that, any commands not directed at our own flight are “wildcard” style, meaning they activate if any command “ends with” those keywords.
TLDNR; There are about 4 million derived command variations, or ways to speak individual commands, and so the best way to interact with this profile is on a conceptual basis: I’ll have covered the “standard” wording for everything, so you could assume “done refueling” would work, but not likely more relaxed variations such as “topped up”. Try it - if it doesn’t work, add it.
Just say a command, and if VoiceAttack doesn’t recognize that particular variation (and you’ve tried it more than just once to be sure), you can easily add this using the QCC - my “Quick Command Creator” system that uses pop-up windows to guide users through simple or advanced macro command creation - and following my example of adding a new command variant with the action to call an existing command (by name) as described in the AVCS Wiki link below:
https://veterans-gaming.com/wiki/…/avcs4-bms-manual/#Alternate Phrase Commands
-
@SemlerPDX Thanks but I’ve seen that page (command reference) and it doesn’t give much info aside from what’s from the in-game menus. While I appreciate there can be a lot of command variations, maybe a few examples of each can be useful. Although it does not cover all possibilities, I think it would be a great starting point for someone who is just learning these phrases — maybe some phrases will be remembered better or easier to remember/flow. For example, when issuing the “done refueling” command after tanking, the actual phrase from the pilot is “topped up and ready to go” and after hearing it so many times, sometimes the more natural thing to say is “topped up”
-
@SemlerPDX , is there a command in the latest profile (1.4.1) for “Carrier Report Airborne” (tttttt8)? If so, I couldn’t find it in the profile.
Thanks,
Regards,
Tomcattwo
(VoiceClone) -
@Atlas If it’s too confusing to read the commands which are present through the VoiceAttack profile editor, or if the command reference is too lacking, you can also view the actual command phrase variables themselves in the file at the path below:
"C:\Program Files (x86)\VoiceAttack\Apps\AVCS\CORE\BMS\41\update\avcs_bms_data_3.cfg"
(*assuming your VoiceAttack is installed in that folder, ofc - change as needed)
I will continue to try developing better ways to make this large amount of information digestible, and in a format that doesn’t cause the brain veins to pop. I intend to continue development of documentation and the profile itself in time - hope it’s at least usable in its current form until then.
@Tomcattwo Yes, there is. It is not shown in the examples presented through the VoiceAttack profile editor view, or the command reference - just must have missed that one altogether. The command does exist in the code nonetheless, and will work if that phrase is recognized.
-
@SemlerPDX Thank you sir! That is very helpful! If I add more commands here (as opposed to your QCC), that will work too, right?
-
@SemlerPDX I’ve added a couple of commands via QCC but they do not show up on the .cfg file you pointed out, are they somewhere else? I’d like to know this to be able to check/confirm what I’ve added. Thanks!
I’ve also added “overhead break” and “on overhead break” to the “report overhead break” command and while it is recognized by VA, it’s not executed. Why is this and how can I fix this please? Thank you!
-
@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX I’ve added a couple of commands via QCC but they do not show up on the .cfg file you pointed out, are they somewhere else? I’d like to know this to be able to check/confirm what I’ve added. Thanks!
I’ve also added “overhead break” and “on overhead break” to the “report overhead break” command and while it is recognized by VA, it’s not executed. Why is this and how can I fix this please? Thank you!
I believe the QCC commands are saved here:
..\VoiceAttack\Apps\AVCS\save_files\bms_save\41\save.txt
-
@CriticalMass perfect, thanks!
-
@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX I’ve added a couple of commands via QCC but they do not show up on the .cfg file you pointed out, are they somewhere else? I’d like to know this to be able to check/confirm what I’ve added. Thanks!
I’ve also added “overhead break” and “on overhead break” to the “report overhead break” command and while it is recognized by VA, it’s not executed. Why is this and how can I fix this please? Thank you!
Okay - all QCC commands can be reviewed in the QCC pop-up windows, including verifying the step-by-step actions of a command. These are (as CriticalMass stated) saved to the user save file. Unfortunately, in that file, they will have the ‘phrase’ and the ‘actions’ in separate variables, and not in an easily human-readable format.
If you just say, “Edit a Voice Command”, you can more easily review the various QCC commands you have saved, and their actions lists.
Regarding the ‘overhead’ commands you made: the image is showing that the confidence level of your speech recognition is falling below the default setting of 50. Recognition can be improved by ensuring your Windows Speech Recognition profile has been trained (completely through training, at least 3 times!), and if that is already done, perhaps enunciating a little bit more OR lowering this default Minimum Confidence Level in the VoiceAttack options screen, under the Recognition tab.
-
@SemlerPDX I’ve done that training more than 5 times now and my command is recognised each time I say it, just with a low confidence level. I don’t want to lower the confidence level of the recognition because it may then cause issues later on with other commands getting mixed up. Is there a way to improve confidence level for these phrases?
I’ve also tried this out today and got this COMMAND NOT AVAILABLE error:
-
@SemlerPDX I’ve re-traced the steps to add/edit this voice command and still having this issue
-
@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX I’ve done that training more than 5 times now and my command is recognised each time I say it, just with a low confidence level. I don’t want to lower the confidence level of the recognition because it may then cause issues later on with other commands getting mixed up. Is there a way to improve confidence level for these phrases?
FTR, my good friend from Australia had to run through WSR training a dozen times before he found that “sweet spot”, of course this is due to his regional accent. I don’t want to assume, but if you have any regional accent, it may be helpful to train more. I happen to have a “Standard North American Accent”, and so was able to get by with just 3 training sessions.
Here are options you can try (in no particular order):
-Lower the (global) Min. Confidence Level to 30
-Train your WSR profile more times
-Edit WSR Dictionary, add custom pronunciation for “overhead” and “break”
-Erase this particular QCC command, open the profile, add a New Command following the same concept - to execute another command (by name), and adjust the Min. Confidence Level within this command only (to around 30)Using the final option would be the least desirable. The main benefit of QCC is that users can create new/alternate voice commands for this profile without having to edit the actual profile, and therefore this save file & voice commands can persist between different physical versions of AVCS4 BMS where users must download and import a new profile into VoiceAttack. This would otherwise lose any commands created manually within that AVCS4 BMS profile, and would have to be manually re-created or copied to the newer version of the AVCS4 BMS profile.
You can save and backup your WSR profile, and/or try training a new WSR profile from scratch, it is possible for a WSR profile to become messed up for one reason or another, though rare, and having a backup to restore from can really save time from not having to run through the training again.
Windows Speech Profile Backup Tool (on my Dropbox)
-
@Atlas said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX I’ve re-traced the steps to add/edit this voice command and still having this issue
These commands are not “full commands”, they are part of the prefix/suffix set which are on the left side of the command reference radio menus infographic. All these commands follow a format of “[who] [what to do]”, and you’re having that QCC command try to execute this command only using the “[what to do]” portion and so it has no way to know “who” this is for.
These must be directed at a particular flight member (or the entire flight). They must be preceded by something like “Two”, or “Element”, or “Flight”, for example.
If you want to create a QCC command that is a wildcard for anything that ends with “rejoin formation”, then AVCS4 cannot tell which flight member you are talking to. You could add that to your ‘execute command (by name)’ if you want, but of course, then this alternate syntax wildcard command you’ve created would only ever apply to the Wingman, and never Element leader or the entire flight.
NOW - this profile IS totally customizable for users who want even more realism, so you can absolutely edit those config files to make them work in ways that I had not designed, but the tradeoff is that these would be moved to a “rollback” folder (named “config”) if I put out a patch update. You’d have to repeat this process after any patch updates (or tell AVCS4 BMS to use rollback configs, therefore losing any benefit of that latest patch update).
To accomplish this sort of customization, you would open the #1 config and the #3 config file(s) in something like Notepad++ (run as Admin). See image below - I have searched the #1 config file, the one for keypresses, and added this new phrase variant - this must be done for ALL the rejoins, so, for element & flight as well:
…and of course, in the #3 config (the one for command phrases), you would search for and edit the “Rejoin” command to add another option after the semicolon for “Rejoin Formation” - note that you must leave the original Rejoin, as shown in the pic below:
-
@SemlerPDX Thanks for your help! I don’t want to go too deep or get too complicated so I’ll try the simpler solutions first. Thanks for explaining the [who][what to do] bit as I looked at the commands and did not realise I was missing the [who] bit.
-
@SemlerPDX a while back, I came to you with a problem re: speech recognition and you said I can enter it as a phrase in my speech recognition software so that it gets recognised better. I need to scroll back quite a bit to get that info. Just wondering if you have that info on a page somewhere I can bookmark for easier access?
Just lazy me asking a question for now. Can’t wait to get this sorted this weekend for some flying and learning time next week. Current issue is I can’t talk to #2 as “two, rejoin” is recognised as “to rejoin” and therefore not issued as a command.
Thanks for any help.
-
-
-
@Atlas Thanks for the suggestion! I’ve gone ahead and added that content to the AVCS Wiki page here:
https://veterans-gaming.com/wiki/vg-labs-projects/avcs-wiki/avcs4-bms-manual/The command recognition phrases for wingman are inclusive of the word “to” as shown here:
I’m not sure what could be interfering with these, but you can enable the VoiceAttack event log to show the confidence level of all recognized (and rejected) command phrases. The default confidence level is 50.
If you can take a screenshot of the VoiceAttack event log showing “to rejoin” as unrecognized with proper confidence above your minimum confidence level, we could consider that a problem worth troubleshooting. I cannot reproduce that:
(I culled the “two” from the prefix command for this test, and “to rejoin” worked just fine for me…) -
@SemlerPDX You are a star! Will give this another go on the weekend and will report back!
-
@SemlerPDX Reporting back… added my other screen onto my setup so I could put VA there to monitor what it recognises. Otherwise, absolutely nothing changed… and it works. Rejoin, close up, etc. commands recognised with high confidence. I wonder if it is the mic boom placement that resulted in poor recognition before? But in any case, issue sorted for now, will see if any other gremlins poke their heads out.
Thanks!
-
EDIT: The “Reset” button on the Joystick Options “Test” page solved this problem. I could swear I tried that yesterday, but it didn’t work. Oh well, glad it worked today, and I’m glad VA and AVCS4 are back to fighting strength!
Oh, and I got the idea to try “Reset” again from this thread on the VA forum, to which SemlerPDX recently contributed:
https://forum.voiceattack.com/smf/index.php?topic=4219.0
The original problem:
I’m updating to BMS 4.37, and getting VoiceAttack to work is the last item on my to-do list. Unfortunately, I’m having trouble getting VoiceAttack to “see” any of the buttons on my Winwing F-16 throttle.
I’ve updated VoiceAttack, and I’m using AVCS4 Core 1.11 and AVCS Voice Control Radios 1.41.
I’ve been able to use a voice command to turn on PTT mode in AVCS4. I am hoping to use PTT in the “default” mode, where it only requires a PTT switch be actuated in order to do in-game commands over the virtual radio, like talking to wingmen, talking to ATC, etc…
I can’t set a PTT button, though. When I go into VoiceAttack’s settings (starting with the wrench icon in the lower-right corner of the VoiceAttack window), and then to Joystick Settings, I can Enable my Winwing base + F-16 throttle. But when I click “Test”, and VoiceAttack asks me to press buttons on that device, it does not see any of my button presses.
I was able to use this base+throttle in 4.36 with AVCS4 1.40, in PTT “default” mode, but I can’t get VoiceAttack to “see” this base+throttle any more.
I might be boneheading something, or maybe VoiceAttack has an issue with the Winwing device after the recent Winwing firmware update I did.
Just curious if anyone else is having the same problem…
-
@SemlerPDX When I use VA, my voice attack transmissions are repeated by the sim - both aurally and in text on the screen. I have noticed in some voice attack BMS videos, the sim does not repeat the command. How do you stop the repeat transmissions by the sim when using VA ? thanks.