AVCS4 Immersive Voice Control Radios for VoiceAttack
-
Thank you for the note, Wheelchock! New command variable was to blame, in the comms list command. Cheers!
Just a simple hotfix for the bug found by Wheelchock, the standard “Ready for Departure” command was getting overwritten by the variable for the new “Carrier Ready for Departure” command added for the new U1 update for BMS. As a result, this command will call an Abort by attempting the same input key as the carrier departure. Basically, everyone using this profile does need this hotfix, can’t be avoided.
Anyone can easily fix this themselve inside their own profile, if you already have v1.2, and you don’t want to bother importing this new version for a simple hotfix - just open the command labeled,
“KEYPRESS_Variables →→→((ADJUST AI COMMS LISTS & KEYS USED BY THIS PROFILE HERE))←←←”
and scroll down to the ATC Variables section, under the Carrier Page section, you can change the #7 variable from
“Set Text [KEY_ATC_ReadyForDeparture] to ‘7’” to “Set Text [KEY_ATC_[COLOR=#DBA901]CarrierReadyForDeparture] to ‘7’”, and apply changes.Otherwise, just download this new version…
Download: (Click Here)
Patch Release v1.3 Changelog Jan2020 Fixes/Improvements: -Fixed issue with variable conflict for "Ready for Departure" - was pulling new variable from "Carrier Ready for Departure"
-
I am having trouble setting up the push to talk. I turn it on, and commands are recognized, but nothing happens. If I turn off push to talk mode then commands are recognized and actually followed in game. I saw something about having to set up my joysticks VHF and UHF buttons. I assigned my joystick, but it still doesn’t seem to work. Any help?
EDIT
Nevermind, I figured it out by editing the profile and assigning the button presses there. -
Hello,
I upgraded to 4.34 U1 and for some reason that I can possibly figure out, my Voice Attack commands are not recognized in 3D. I am using AVCS4 exellent VA profile. It is in constant listening mode, VA recognises the spoken commands, the TQS buttons are recognised in game and by VA.
Any help would be greatly appreciated!
Cheers!
-
Hello,
I upgraded to 4.34 U1 and for some reason that I can possibly figure out, my Voice Attack commands are not recognized in 3D. I am using AVCS4 exellent VA profile. It is in constant listening mode, VA recognises the spoken commands, the TQS buttons are recognised in game and by VA.
Any help would be greatly appreciated!
Cheers!
You want to ensure VoiceAttack is run as Administrator - if not already - by clicking the wrench icon on VA for settings, select System / Advanced tab on the top right, and select 'Run VoiceAttack as an Administrator".
If that isn’t the issue, try altering the application focus - in VoiceAttack, open the profile with the ‘Edit Profile’ icon, and at the to left is ‘Options’ button, follow instructions in the last image at the very bottom here: https://imgur.com/a/xuclI0a
You may want to try simply “Active Window” if it is set to Falcon BMS.exe (and not working). Another option is to enter the text Falcon BMS (surrounded by asterisks), but the default entry of Falcon BMS.exe should handle most users. Let me know how it works out, if it still won’t send keypresses to BMS, we can troubleshoot further.
Best wishes and good luck!
-
Make sure you’re using the latest profile - version 1 sent commands to a window with “Falcon BMS” in the title, which would match on web browsers, PDFs, etc. Later versions changed this to “Falcon BMS.exe” so that commands were sent to 3D.
-
You want to ensure VoiceAttack is run as Administrator - if not already - by clicking the wrench icon on VA for settings, select System / Advanced tab on the top right, and select 'Run VoiceAttack as an Administrator".
If that isn’t the issue, try altering the application focus - in VoiceAttack, open the profile with the ‘Edit Profile’ icon, and at the to left is ‘Options’ button, follow instructions in the last image at the very bottom here: https://imgur.com/a/xuclI0a
You may want to try simply “Active Window” if it is set to Falcon BMS.exe (and not working). Another option is to enter the text Falcon BMS (surrounded by asterisks), but the default entry of Falcon BMS.exe should handle most users. Let me know how it works out, if it still won’t send keypresses to BMS, we can troubleshoot further.
Best wishes and good luck!
Hi SemlerPDX, thank you for your reply. I run VA as Administrator, and I double-checked in System / Advanced and the box is ticked. I also tried your other suggestions without any success. I run the latest version of VA and your profile v1.3. VA picks up my voice correctly, the commands are recognized. The TQS VHF/UHF buttons are recognized in BMS. Please see attached screenshot when I load the profile. This is a big mystery!
-
Make sure you’re using the latest profile - version 1 sent commands to a window with “Falcon BMS” in the title, which would match on web browsers, PDFs, etc. Later versions changed this to “Falcon BMS.exe” so that commands were sent to 3D.
Thanks Orffen! Yes, I am using v. 1.3 and the latest version of VA too. Cheers!
-
Audio Feedback Mode is On but I don’t receive any sound feedback following a correctly recognized command.
-
When I use “UOAF Advanced VoiceAttack Profile” it works, but when I load the AVCS4 v1.3 profile it doesn´t work. I am clueless!
-
I receive the following message when I try to install the v.1.3. See attached picture. Could this be a problem or is it normal?
-
@Vikingo – I can’t see your attachments, they are invalid. Please try uploading images of your errors to an image website and just drop the link here - like imgur https://imgur.com/
Happy to help you out, just can’t see where you’re hung up. It’s working for me and a lot of others, just need to find out why it’s not working for you. You seem to have a lot of issues, the Audio Feedback Mode is pretty basic, and the VoiceAttack event log should show any errors when a sound file is unavailable or not set – my question to you would be, can you hear VoiceAttack say anything, either? When the profile is initialized, there are some voice phrases cued. If you can’t hear my profile talk to you at all, then you have sound issues.
If the sound files don’t exist, an error would display, but you can double check them in the VoiceAttack program folder, under Sounds > AVCS4 > should contain AVCS_Feedback_CENTER.wav, AVCS_Feedback_LEFT.wav, and AVCS_Feedback_RIGHT.wav
On the issue of keys not getting to Falcon BMS, you can test the functionality of the profile by setting Profile Options to target “Active Window” instead of “Falcon BMS.exe”, then open up a Notepad, and call a command… a string of letters or numbers should appear. Please test that, and let us know when you reply.
On a final note there, my profile uses the default BMS keyboard bindings where Q-W-E-R-T-Y activate the various radio menus, and the 1-9 and 0 keys are used to select items in the list. If these are changed, or if your keyboard layout differs from QWERTY (such as AZERTY or QWERTZ), you would need to run the “Change Default Keyboard Layout” command and set as appropriate.
One last question, is my profile recognizing your commands? Any recognized command will display in green with exactly what you spoke. If this is not happening, we’d need to troubleshoot other things. Please answer my questions if you can, and provide actual pictures of your errors, and I’ll be glad to help you get up and running like the rest of us! It’s gotta be something simple, and it’s good that we find these edge cases so we can anticipate issues for future versions, too. I don’t mind the odd problem, we’ll find the solution before long. Thanks for your patience!
Cheers!
-
@Vikingo – I can’t see your attachments, they are invalid. Please try uploading images of your errors to an image website and just drop the link here - like imgur https://imgur.com/
Happy to help you out, just can’t see where you’re hung up. It’s working for me and a lot of others, just need to find out why it’s not working for you. You seem to have a lot of issues, the Audio Feedback Mode is pretty basic, and the VoiceAttack event log should show any errors when a sound file is unavailable or not set – my question to you would be, can you hear VoiceAttack say anything, either? When the profile is initialized, there are some voice phrases cued. If you can’t hear my profile talk to you at all, then you have sound issues.
If the sound files don’t exist, an error would display, but you can double check them in the VoiceAttack program folder, under Sounds > AVCS4 > should contain AVCS_Feedback_CENTER.wav, AVCS_Feedback_LEFT.wav, and AVCS_Feedback_RIGHT.wav
On the issue of keys not getting to Falcon BMS, you can test the functionality of the profile by setting Profile Options to target “Active Window” instead of “Falcon BMS.exe”, then open up a Notepad, and call a command… a string of letters or numbers should appear. Please test that, and let us know when you reply.
On a final note there, my profile uses the default BMS keyboard bindings where Q-W-E-R-T-Y activate the various radio menus, and the 1-9 and 0 keys are used to select items in the list. If these are changed, or if your keyboard layout differs from QWERTY (such as AZERTY or QWERTZ), you would need to run the “Change Default Keyboard Layout” command and set as appropriate.
One last question, is my profile recognizing your commands? Any recognized command will display in green with exactly what you spoke. If this is not happening, we’d need to troubleshoot other things. Please answer my questions if you can, and provide actual pictures of your errors, and I’ll be glad to help you get up and running like the rest of us! It’s gotta be something simple, and it’s good that we find these edge cases so we can anticipate issues for future versions, too. I don’t mind the odd problem, we’ll find the solution before long. Thanks for your patience!
Cheers!
@SemlerPDX, many thanks for your extensive error searching support! I put the “UHF/VHF Push-To-Talk Mode” to OFF, and your profile works fine in that mode. Hence, it is my TQS COMMS buttons that don’t work properly. I have them correctly mapped in BMS, that I know, and they work fine with the “UOAF Advanced VoiceAttack Profile”. Still a big mystery to me. I cannot figure that one out. I would love to use the PPT mode with your profile, if possible. Any clues on where I may have it wrongly setup? Note that I use TUSBA, and I just installed it a couple of days ago.
-
@SemlerPDX, many thanks for your extensive error searching support! I put the “UHF/VHF Push-To-Talk Mode” to OFF, and your profile works fine in that mode. Hence, it is my TQS COMMS buttons that don’t work properly. I have them correctly mapped in BMS, that I know, and they work fine with the “UOAF Advanced VoiceAttack Profile”. Still a big mystery to me. I cannot figure that one out. I would love to use the PPT mode with your profile, if possible. Any clues on where I may have it wrongly setup? Note that I use TUSBA, and I just installed it a couple of days ago.
Sure - just open up VoiceAttack Options and setup that controller for VoiceAttack - then you need to edit each of the VHF PTT Push & VHF PTT Release and the UHF PTT Push & UHF PTT Release commands inside my profile (top section, under initialization), and follow instructions inside those commands to set their ‘When I press button:’ to your respective joystick buttons. Lots of info in the AVCS info pics here: https://imgur.com/a/xuclI0a
-
Thank you! I had only assigned the joystick under the Joystick Options and not assigned the UHF and VHF buttons within your profile. Now I understand how it works. Thank you so much for your assistance!
-
You’re welcome! I suppose pics like that one I shared shouldn’t be buried behind a link but more prominent on the main description page - I might make a few better instructional graphics for that PTT system, text instructions are a pain especially for our friends who don’t speak English as their first language. I will include them in the next version when I implement this new Save File System I’m just finishing up for my Elite: Dangerous AVCS4 profile.
Glad you got it working! Cheers!
-
Happy to announce version 1.4 just around the corner. Coming next, I’ve created a save file system to maintain user defined settings (PTT Mode On / Audio Feedback / Keyboard Regional Layout / etc.) between updates, as well as a live update system for minor patches to systems initialization, where a majority of my AVCS4 profile gets it’s operating information.
To put it plainly, in the next and all future versions, a missing variable or typo in one of the commands like INIT_KEYPRESSES can be pushed out almost instantly to any users of AVCS4 when I receive the report (1.3 exists because 1.2 had a simple typo in the new Carrier Ready for Departure command, in the init file only). Imagine one of the text-to-speech item variations had a problem, and was saying a word wrong, I could change that TTS variable on my end, and push it out to all users who would get it almost instantly when loading the profile.
I tried a test of more than 2kb (the entire keypress init without comments is only 7kb) of info and a hundred variable updates and couldn’t increase the profile init time past 1 second, so it’s fast, powerful, and will allow featureless updates without re-downloading new profiles.
Additionally, the 1.4 version will feature an update notification system, too, to let users know of any major updates that require a manual profile update, with minor bug-fix patches being installed silently on profile load.
Never again will a typo require an AVCS4 “download new version”! For every AVCS profile or profile builder module I make for any game (BMS, Elite Dangerous, ARK/ATLAS, the Voice Controlled Profile Builder, etc.), any custom user saved settings will no longer be lost due to profile update/delete, or even complete windows reinstall (save file backup system included).
**ETA - about 3-4 weeks
Happy New Year and see you at Angels 20!**
-
Excellent news! Looking forward to the release.
Sent from my iPhone using Tapatalk
-
This post is deleted! -
Hi SemlerPDX,
first of all a BIG THANK YOU for making this profile public and supporting it!
It’s just so user-friendly and works (with some speech training) so well.Never the less i think i found a small bug. When i was giving the command to “Activate Radar”, it would recognize the command, but would only send “wwww”, the “4” was missing.
So i checked the profile options to see why. It took me some time to figure out how this all workshttps://i.imgur.com/grdsGFy.png
https://i.imgur.com/WJzCgd2.pngSo i fixed variable in the INIT section to match the recognized command –> “ActivateRadar”, now it works.
cheers
Magic -
just wow… man you’re amazing. 1.4 sounds like its going to be great!