AVCS4 Immersive Voice Control Radios for VoiceAttack
-
@SemlerPDX Got to let everyone know that your VA profile for BMS Falcon is fantastic. Thanks again for your advice. I searched VA Discord and Pfeil. I found advice that said try deleting your speech recognition file because it might be corrupted and make a new one. Then I did the speech engine training 3 times. However, unlike yours, my Voice Attack Recognition Tab remained unchanged as Default.
These are my results:
The unrecognized command was due to my error in failing to say the word “turn”. It should have been “two turn smoke on”. -
@jc1 That’s excellent news! I would not have thought of that solution.
Remember that if you ever want to make additional recognition options for BMS radio commands, it’s pretty easy using the Quick Command Creator system I designed. The example would be, create a new command in QCC to allow a variant of that command which does not require the word “turn”.
The AVCS Wiki Page for this profile describes this method of creating a new command through QCC with the intent to call an existing command (by name), and therefore providing more natural or inclusive options for the ways we talk to our BMS wingmen, etc.
https://veterans-gaming.com/wiki/…/avcs4-bms-manual/…
Cheers!
-
@SemlerPDX Alright, Semler, tnx for your info
-
@SemlerPDX Am I remembering wrong or was there never a PTT function on this profile? Does it need one? Can I make one anyway?
-
@Atlas Users can set up to 6 total keyboard keys, joystick/controller buttons, or mouse buttons as “Push-to-Talk” in AVCS. Just say, “Set a Push to Talk button”, or, “Edit a Push to Talk button”, and follow the prompts on the pop-up window(s):
Users can also select from two different modes. “Global” mode disables the global listening feature in VoiceAttack unless the PTT key/button is pressed, and the “DEFAULT” mode which only restricts recognition of in-game radio menu commands that fire keypress macros. This way, if users want, they can still use other simple commands like, “Open the Command Reference”, or “Set a Human Pilot”, or maybe other custom user voice commands like “Pause TrackIR”, all without needing to use the push-to-talk button:
It’s also possible to set a “Push to Mute” button. If a user was to, for example, hold down a joystick button, then ask AVCS to set a PTT button, and then release this button when told to “press a PTT button to set”, this PTT button would be a “reverse PTT”, meaning that recognition would persist until this was pressed, at which time it would be disabled (depending on the mode).
-
@SemlerPDX Thanks!
-
@SemlerPDX i’ve noticed that setting a PTT button for BMS profile means PTT for wingmen, while the user is still able to talk to tower, awacs etc. Is it possible to tie and restrict both UHF and VHF commands to separate respective PTT buttons?
Thank you very much for your great engine and profile! -
@depapier said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX i’ve noticed that setting a PTT button for BMS profile means PTT for wingmen, while the user is still able to talk to tower, awacs etc. Is it possible to tie and restrict both UHF and VHF commands to separate respective PTT buttons?
Thank you very much for your great engine and profile!Since users can set up to 6 Push To Talk keys/buttons, there is no way for my PTT system to differentiate which of those correspond to any in-game actions such as UHF or VHF transmit buttons - it is merely an immersive feature that these can be assigned to the same buttons in the sim used for transmitting on UHF and/or VHF radios respectively. On that same level, this system doesn’t even know if you are in your cockpit and if the radios are powered on, or tuned to the correct channel for whatever contact is being initiated. It is only designed to be an immersive voice control layer for interacting with the Radio Menus within typically expected operational states, and it is down to the user to set up as required by the simulator.
When PTT is Enabled, commands for wingman/element/flight AND tower, awacs, etc. are all restricted unless one of the PTT buttons are pressed. If any radio voice commands are issued when the PTT mode is enabled and the PTT button(s) not pressed, the command actions will not go through.
A red message will appear in the VoiceAttack Event Log for wingman/element/flight commands informing users that the command was recognized & PTT mode is on but PTT button press was not detected. This message will not appear for tower, awacs, etc. commands (not for any reason beyond that I didn’t add that reminder message to those commands).
-
Hi @SemlerPDX, I’m just exploring more of the sim and using your voice control profile and while I’m aware of the commands list shown in the first post, I wonder if there’s any way to know what phrase options we have for any given commands? Opening up your profile is a bit too confusing for me to make heads or tails with.
Just to clarify: I’m looking for something like—
(Tanker) Done Refueling - refueling complete, topped up, done refueling, etc…
[command] - [phrases that will execute command]I hope I’m explaining it clearly enough. Thanks!
-
@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