AVCS4 Immersive Voice Control Radios for VoiceAttack
-
Dear @SemlerPDX sir, you are a hero without cape
Thank you so much for this update.
One small thing did I find - ârequest jfs rechargeâ does not resolve.
Aside from that, everything seems to run smoothly - even on my QUERTZ keyboard
Amazing work, thank you!!! -
Thank you @SemlerPDX ! You are so meticulous in your coding! It is clear that you put a huge amount of time and effort into this labor of love. Well done!
Regards,
Tomcattwo
(VoiceClone) -
@Amadeus75 said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
One small thing did I find - ârequest jfs rechargeâ does not resolve.
oops!! I think that one has gone under the radar since the command was added!
Nice find! Looks like there was a legitimate typo in there, âLâ instead of âJâ (not that this command is easy to use anyway, voice recognition typically hates most single letters and acronyms unless weâre very careful with enunciation!!)
As seems to be obligatory with these things, Iâve released a day-1 patch, no new download required if yâall already got v1.41 - it will apply next time you load AVCS4 BMS - just select âyesâ on this pop-up that appears:
Public Release AVCS4 BMS v1.41.1 Changelog Aug-10-2022 This is a simple Live Update patch fix, no new profile download is required - the following fix applies to this update: Fixes/Improvements: -Fixed ATC Command for "Request JFS Recharge" -- keypress variable had typo of "Lfs" in avcs_bms_data_1.cfg file
-
@SemlerPDX tnx for the heads up. btw: where do I find these commands:
-
@Bikeman Oh thatâs just configuration stuff, located in the VA Apps folder under AVCS (for the specific profile/version, so, BMS/41)⌠these are just variables that are loaded behind the scenes to make all those commands actually function.
Manual editing is not recommended, but this option is available - say, âOpen Advanced Core Optionsâ - selecting the appropriate option in the list (pictured below) it will open each of them one by one before loading their contents:
Of course, the options just below can be used to restore/delete these config files as well. If a profile is loaded and they are missing, they will be replaced. I use âdata_1â for operational variables, âdata_2â for text-to-speech variables, and âdata_3â for voice command phrases.
-
Does anyone else have trouble having these voice commands recognized from the category,
AI COMMS 1 - Miscellaneous
Music Off
Music On
Turn Smoke Off
Turn Smoke
Fence Out
Fence InThis is what I get. None of the commands was recognized. Strange that Music On was not recognized.
-
@jc1 Say, âOpen the Command Referenceâ, to see this graphic reference below:
https://veterans-gaming.com/uploads/monthly_2022_08/RadioMenusReference_FULL_v1_41.png.08a773cc1e5d33f889707539940bb982.pngNote that in the left column, all these commands must start with who you are speaking to - Wingman, Element, or the entire Flight. The column on the right is âanything which ends withâ the command phrase.
As such, âMusic Onâ is not a recognized command, but, for example, âWingman Music Onâ is recognized:
-
@SemlerPDX Thanks, I started to identify who I was speaking to. I also did the Windows Speech Training 3 times. But I have a problem with Fence In and Fence Out, and maybe others as I go along with AVCS4. I got 8% success rate for Fence In. I donât think the problem is with your AVCS4. What do you think makes it so difficult for some commands?
-
@jc1 For general recognition troubleshooting and tips, you should pop over to the VA Discord - Pfeil knows all the tricks and tips, and would best be able to direct you to things you could improve or try to improve your recognition.
The Recognition Options window is pictured below, and not sure what your settings are, but these are mine and I have no issues with these commands. I have a Standard North American Accent, to be candid - Southern American Accents or others such as from parts of Australia, Ireland, or Scotland, etc. may have a more difficult time fine tuning things.You could try lowering the minimum confidence level, increasing the command weight, or checking/unchecking the Adaptive Recognition or Echo Cancellation for testing. Honestly, the best advice I could give would be to pop over to the VA Discord and describe the problem as you have for me: again, Pfeil has all the best tips and knows all the tricks
-
@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â