AVCS4 Immersive Voice Control Radios for VoiceAttack

Sniper 0

@Sniper-0 the sound folder is also empty, no sounds… Always displaying initializing failed, part of c/voice attack/… beepLoud.mp3 not found

SemlerPDX

@Sniper-0 There could be two reasons why you see that error. First one is that the database was offline when you tried. I was asleep 5 hours ago, but we are currently overhauling our website, not sure if it was actually offline, but I assume it was. If that was the case, you should simply try again now, as I can see the VG website is online and doing fine.

Second possible reason is your VoiceAttack (and subsequently my profile) cannot retrieve the config files from the secure VG website because they do not have proper permissions set. If that was the case, you should ensure you are running VoiceAttack as Admin (see pic in my last post above) - check the box “Run VoiceAttack as an Administrator” and restart VoiceAttack. Also make sure that VoiceAttack has permissions to access the internet and is not locked behind a firewall rule blocking internet access.

On the note regarding sounds folder:
Under the VoiceAttack programs folder, there should be an Apps, Sounds, and Plugin Samples folder by default. Inside the Sounds folder should be an folder “AVCS” and within that folder should be three sound files:
AVCS_Feedback_RIGHT.wav
AVCS_Feedback_LEFT.wav
AVCS_Feedback_CENTER.wav

If these files are not present, you may have an issue with VoiceAttack, and the manner in which you imported my profile package(s). You will want to start over by deleting the AVCS CORE (and/or AVCS4 BMS) profile(s) from VoiceAttack, and re-import them properly.

Make sure you have restarted VoiceAttack after checking that box to run as Admin above before taking these next steps!

On the VoiceAttack main menu, select the second profile management button and select “Import Profile”. Point this to my AVCS CORE package you downloaded (ending in .vax - with a big “IMPORT THIS” label in the name).

Once done, switch to this profile. It will initialize itself, and retrieve the config files from the secure VG website. Repeat this process to import the AVCS4 BMS profile. You can import both at once or one at a time, so long as AVCS CORE is the first profile you switch to within VoiceAttack so it can perform first time initialization, including getting the latest config files from online as stated.

Let me know if this fixes it, otherwise, we could troubleshoot further.

Sniper 0

@SemlerPDX Alright sir. Let me give it a try

Atlas

@SemlerPDX not sure if you can assist with this but I’m not sure what to do…

As I’m doing more flights with VR, I like setting VA to listen via my G2’s mic instead of my headset mic.

However, I need that to listen to Realtek USB2.0 so that it listens to the G2.

Whatever I do, the setting doesn’t seem to stick so whenever I start up VR and BMS, I need to set up VA to listen to the G2 instead of the default headset mic.

Any idea how to make this work or even if it’s possible? If I start up VA with the G2 not turned on, that Realtek USB2.0 option is not even available on that drop-down selection.

SemlerPDX

@Atlas That gets into some of the technical troubleshooting of the VA program itself. On that level, Pfeil is the best source of information. You should head over to the VA Discord and post up that same info - I’m certain that Pfeil (or others) will know how to handle that - wish I could help, but I’d just be fumbling around taking shots in the dark.

Atlas

@SemlerPDX Thanks for pointing me in the right direction!

SemlerPDX

AVCS4 Falcon BMS Radio Menus for VoiceAttack has been updated for the new menu commands added in 4.37.2 (U2)

This is a major profile update, and a new profile download/import is required. Options will be presented to copy over old user save file and to delete the old config files and AVCS4 profile version. Thank you all for your support and feedback over the years! Any issues, let me know!

Check out the updated command reference in the link below, or just say, “Open the Command Reference” anytime to view the new radio menus graphic and commands list!

https://veterans-gaming.com/semlerpdx-avcs/profiles/commref/bms42.html/

DOWNLOAD:
https://veterans-gaming.com/files/file/35-avcs4-voice-control-radios-for-falcon-bms/

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

Special thanks for the coffees!

SemlerPDX

Small oopsie - if you already updated AVCS4 BMS radios, please restart VoiceAttack and switch to it again, and apply the patch update… I forgot they changed phrases like “Request Vectors For Instrument Approach” to just “Request Instrument Approach” for each of these types of calls. I’ve updated the configs just now, and these new additions will be added when users install the patch update (v1.42.1) following the automated pop-ups. My bad

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)

danster

@SemlerPDX Thank you!!!

Wingedsky

@SemlerPDX Thanks.

Ricky

@SemlerPDX Such a quick update! Thanks!

SemlerPDX

@Todd1215 had noted that the Radio Menus infographic for AVCS4 BMS profile for VoiceAttack is not exactly easy to view or use, especially in VR.

He’s created an amazing Radio Menus guide in PDF, which has the added benefit of being able to be displayed on your kneeboard while in flight. It’s so awesome, I’ll be linking it from my own comm reference soon.

For now, please check out this thread and download the BMS COMMS MENU AID by @Todd1215 here:
https://forum.falcon-bms.com/topic/24794/comms-menu-aid/

Example of the guide:

CriticalMass

Someone spotted a small issue on the FL Discord.

in \CORE\BMS\42\update\avcs_bms_data_1.cfg both AVCS_BMS_ATC_Departure Page and AVCS_BMS_ATC_Common Page have the same page number with other following the Common pages sequence.

AVCS_BMS_ATC_Approach 2 Page=4
AVCS_BMS_KEY_ATC_ApproachDeclareEmergency=5
AVCS_BMS_KEY_ATC_ApproachAbort=6
AVCS_BMS_KEY_ATC_TrafficInSight=7
AVCS_BMS_KEY_ATC_ApproachSayAgain=8
AVCS_BMS_ATC_Departure Page=5
AVCS_BMS_KEY_ATC_ReportAirborne=1
AVCS_BMS_KEY_ATC_Airborne=1
AVCS_BMS_ATC_Common Page=5
AVCS_BMS_KEY_ATC_RequestQnh=1
AVCS_BMS_KEY_ATC_RequestQfe=2
AVCS_BMS_KEY_ATC_TakeoffRunway=3
AVCS_BMS_KEY_ATC_LandingRunway=4
AVCS_BMS_KEY_ATC_RequestWindCheck=5
AVCS_BMS_ATC_Carrier Page=6

SemlerPDX

@CriticalMass Another oopsie - my bad… Thank you so much for the detailed report. I’ve released a patch update, just say, “Re-initialize the Profile” (if it’s already loaded), or start VoiceAttack and switch to the profile and follow the update prompts. (and also thank you very much for the coffee CriticalMass !!!)

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

Atlas

@SemlerPDX Thanks for the update!

I can’t remember if I had set it up under the old profile or if I’m even mis-remembering but is it possible to map 2 PTT buttons? For UHF and VHF. Obviously it doesn’t matter but I would like to be able to use both in the sim but still be able to issue voice commands. Thanks!

SemlerPDX

@Atlas You can set up to 6 total PTT keyboard/mouse/joystick buttons within AVCS

Just say, “Set a Push to Talk button” and follow the prompts.

You can also say, “Edit a Push to Talk button”, for additional access to this control menu.

(if you had AVCS4 BMS in the last update, and you updated this profile, there should have been an option to import your old save file - when you do this, there is no need to re-setup PTT buttons or other settings, of course, as it will just use the ones you had set before)

If you failed to import your old save file, but want to do it now, just say, “Open the Save File Menu”, and choose this option from the menu:

Atlas

@SemlerPDX Thank you sir!

Darxxxide

This profile has been a life saver for me, but I’m having trouble when it comes to the carrier commands (Inbound Mother, Report see you, etc.). I’m in the correct channel, the commands get recognized, and I even see the comm menus pop up and go to the command, but nothing happens. These commands work fine using the keyboard. What am I doing wrong here?

SemlerPDX

@Darxxxide I just checked the code behind these actions, and was expecting to see some typo or human error on my part, but these values seem to line up with the Radio Menu actions:

Anyone else having these issues? I can’t reproduce them…

Darxxxide

@SemlerPDX Thanks for taking a look, I’ll dig into the profile and ensure I didn’t somehow screw something up.

AVCS4 Immersive Voice Control Radios for VoiceAttack

34

10.0k

21.7k

357.5k