AVCS4 Immersive Voice Control Radios for VoiceAttack
-
Restarting done nothing. However…
After deciding to start over I was deleting profiles (of which I had inadvertantly loaded many!) all of a sudden my PC “spoke” to me.
I’m not entirely sure its as it all should be yet but I have made some progress!
Think I need to do the training now as saying “set prefered profile” is not recognised at all!
I will keep plugging away. Thanks for all the help.
Regards,
Gary
-
@Gary I am not sure what you are communicating. In the drop-down menu listing all VoiceAttack profiles, you should only see one entry for AVCS CORE and one for AVCS4 BMS.
When you first launch VoiceAttack, and switch to AVCS4 BMS, it should run through initialization which will include switching to the AVCS CORE profile automatically, and then back to the AVCS4 BMS Profile. During initialization, you should see many messages appear and disappear from the VoiceAttack Event Log, looking similar to this:
Once AVCS4 BMS is fully loaded, the text-to-speech will say something along the lines of, “All systems ready” or “All systems are initialized”, and the VoiceAttack Event Log will look something like this:
Can you please confirm that you have arrived at such a screen and heard such a text-to-speech notice stating that everything was initialized successfully?
-
Sorry I was not clearer.
I can now confirm that my screen looks exactly the same as those you posted above
Time for some speech training now I think.
Thanks ever so much for all your help - really appreciated.
I will feedback my results in a few days.
Regards,
Gary
-
Hi, I’d like to report a bug. In the approach menu in 1.42, when I request an instrument approach, and VA verifies that I said “request instrument approach,” the program instead selects request overhead approach. Same thing for requesting an overhead approach, VA will instead send the command for request emergency landing. I downloaded 1.41 instead and it works as intended.
-
@MokaCola said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
Hi, I’d like to report a bug. In the approach menu in 1.42, when I request an instrument approach, and VA verifies that I said “request instrument approach,” the program instead selects request overhead approach. Same thing for requesting an overhead approach, VA will instead send the command for request emergency landing. I downloaded 1.41 instead and it works as intended.
Hello! Sorry to hear you are having issues.
Unfortunately, I am unable to replicate them. When I say, “Request instrument approach”, the AVCS4 BMS profile types out the letters and number “t t t 3” … and when I say, “Request overhead approach”, the profile presses “t t t 5”. These are the correct positions of these radio calls in Falcon BMS 4.37.2 (U2) and for my profile version AVCS4 BMS v1.42.4
I would ask that you verify that your BMS program version is correct, as well as the AVCS4 BMS profile version which is shown in the VoiceAttack Event Log after it has initialized, or just say, “Show the Profile Version” when AVCS4 BMS is active and initialized.
Shown below is my testing, on the right is the configuration file 1 for AVCS4 BMS, the operational values the profile uses for these radio calls to know what keys to press (and how many) and what number to press for the given radio call - as you can see, these are correct and match up with the radio menus in BMS 4.37.2
-
oh yep, it looks like I didn’t update to 37.2, my bad! I’m so used to automatic updates
-
v1.43 Profile Update has been released for BMS 4.37.3 (U3)
A new Combat Management Page has been added for Wingman, Element, and Flight radio menus. You can review the new updated Radio Menus infographic and a table of all commands in AVCS CORE and AVCS4 BMS using the command, “Open the Command Reference”.
All users will need to download the new profile package and import it into VoiceAttack. Pop-up choices will be presented to import your old save file from the last version profile, as well as to clean up these old files (optional).
Any issues, please let me know… Special thanks for the coffees!
DOWNLOAD HERE:
https://veterans-gaming.com/files/file/35-avcs4-voice-control-radios-for-falcon-bms/
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 preceded by who you are talking to Fixes/Improvements: -Added Combat Management 4 Page category in profile to accommodate these new commands
…
Updated the Radio Menus Command Reference graphic displayed when using the voice command, “Show the Command Reference”:
-
Thank you for the timely update. really appreciated
Unfortunately, I screwed up…
The update went great and I deleted the old 1.42 profile. However, I didn’t import the additional commands that I had added.
Would those be lurking about somewhere that I can grab and paste in or ??? -
Thanks for the latest version. Works great!
Question: How can I change the wording “Report on Final” to “On Final”?
-
@b0bl00i said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
Thanks for the latest version. Works great!
Question: How can I change the wording “Report on Final” to “On Final”?
Check out the AVCS Wiki for this profile - you can very easily create alternate phrase commands which call existing commands using my QCC (Quick Command Creator) … just say, “Create a New Voice Command”
https://veterans-gaming.com/wiki/vg-labs-projects/avcs-wiki/avcs4-bms-manual/ -
@Badger Those would be in the save file for the AVCS4 BMS 1.42 folder.
Say, “Open the Save File Menu”, when you have the latest version of AVCS4 BMS v1.43 loaded.
Next, select the option to restore the save file or the option to import Quick Commands from another save file, and follow the prompts. There are plenty of options in this menu for managing these files, and should be sufficient for your needs.
These save files are independent of the profile, and typically persist in the Apps folder unless you told AVCS to delete them. You can find these in the VoiceAttack programs folder under the Apps folder, at the following path, in case you need to or want to work with them manually:
%ProgramFiles(x86)%\VoiceAttack\Apps\AVCS\save_files\bms_save
or if you have the steam version:
%ProgramFiles(x86)%\Steam\steamapps\common\VoiceAttack\Apps\AVCS\save_files\bms_save
-
I love this app, and I havent even begun to create custom commands yet.
I do have one issue though, I’ve just tried to map the push to talk buttons to my VHF/UHF buttons on my throttle. So I’ve enabled push-to-talk and set the buttons (default macros). But still it’s registering my commands without me pushing the buttons.
I’ve disabled the VA push-to-talk obviously.
-
@sepruda
Check the ‘headphone’ icon on the right side - it should be disabled, otherwise the app is listening continously. -
Ok, I think I tried that, but will try it again. Thanks.
-
Actually it should be enabled, which is also what is shown in this video
It is sort of working I found out, but some commands are not stopped by PTT, for example “taxi for departure” here, while “wingman say fuel” is.
-
@sepruda said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
Actually it should be enabled, which is also what is shown in this video
Oops, sorry… I am not using PTT mode. Thanks for clarifying!
-
@sepruda said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
Actually it should be enabled, which is also what is shown in this video
It is sort of working I found out, but some commands are not stopped by PTT, for example “taxi for departure” here, while “wingman say fuel” is.
Just because you see it appear as a recognized command in the VoiceAttack Event Log does not mean that it is not respecting the PTT mode you have set in the “Default (macros only)” mode.
Please test by opening a simple notepad and placing the cursor while you have PTT mode enabled, and DO NOT depress any of your PTT keys or buttons. Say the commands, “Wingman Say Fuel”, and see if it types out any letters/numbers, and then do the same for “Request Taxi for Departure” - please report back if you see any letters/numbers typed by either of these commands while PTT mode is enabled and you are not pressing the PTT key/button.
…
((off topic … thank you very much to “Echo” for the coffees!! ))
-
@SemlerPDX You’re right It’s not registering the commands when the PTT button is not activated, even if VA says it recognises it.
Notepad shows nothing, unless PTT button is pushed, in which case it types the commands. Excellent
-
@SemlerPDX I am still having issues with my wildcard commands unfortunately. I’ve trained my speech model 5 times I think.
When I say “<wildcard> request landing”, it doesn’t recognize it but when I just say “request landing” it recognizes it (though not very well I admit, probability around 55). If I pause after my wildcard briefly, that also works.
-
@sepruda Unfortunately, that is a limitation of voice recognition, and a brief pause between words can help. There are other features of VoiceAttack which can help, but the most simple option is a brief pause - and learning how brief this can actually be for a successful recognition of that particular command that is giving you problems.
For these commands which are troublesome to you, you might try a special option on the command level - first say this command without a wildcard to get it to appear as ‘recognized’ in the VoiceAttack Event Log, then double-click that command … it will open the command editor and the editing screen for this command.
Next, as a test, you can try changing the Recognition style for this command to “Continuous” … for commands which begin with a wildcard, the “Restricted Continuous” would not be appropriate. All commands are set to “Normal” by default, as this option is not always required and may also require individuals to set or test a “Confidence” level override in these commands as well (on a per-command basis). If, for example, your default Confidence level set in the Main VoiceAttack Options Menu under the Recognition tab along the top (or in the profile options of a profile) is set to something like “50”, setting it here to a “65” would override that setting and apply a “65” for this command only. Try first without changing this, and increase/decrease as applicable for additional refinement when using the “Continuous” recognition style.