AVCS4 Immersive Voice Control Radios for VoiceAttack
-
Thanks all for your suggestions, I’ll give them a go later and report back.
I’ve been a long time YAME user but I’ve been having issues since 4.34 so I had to revert to BMS’ native extraction method for now until the 2.0 branch comes out of beta testing.
All the best,
Uwe
-
Hm, I just tried “select your own target” and entered
Falcon BMS.exe
in the text box, but behaviour in BMS still is the same. When VAC recognizes the first part of a command (say, “wingman”), the mouse cursor appears but all following key input is lost and the comms menu only appears once I re-focus the BMS window by clicking into it. I’m testing this on win7 if this makes any difference.
Thanks again & all the best, Uwe
EDIT: I’m running BMS in “-window” mode.
-
Hm, I just tried “select your own target” and entered
Falcon BMS.exe
in the text box, but behaviour in BMS still is the same. When VAC recognizes the first part of a command (say, “wingman”), the mouse cursor appears but all following key input is lost and the comms menu only appears once I re-focus the BMS window by clicking into it. I’m testing this on win7 if this makes any difference.
Thanks again & all the best, Uwe
EDIT: I’m running BMS in “-window” mode.
I’m pretty confident its the BMS extraction issue. turn extraction off in BMS. If it works that way the RTT extraction tools work just as a good as BMS extraction if not slightly better.
-
Also changing the key delays and timing didn’t change anything. I wonder though why other VAC profiles I’m using do not exhibit this peculiar behaviour?
Thanks again & all the best,
Uwe
-
Just did a test using the “active window” and notepad++, this doesn’t work either. (see screenshot below)
All the best,
Uwe
EDIT: Using the BMS 4.34 single callsign profile, I can send keypresses to notepad++ just fine.
-
Hi folks, I think I fixed the issue by explicitly disabling the “send to” setting in the “profile options” as the error message indicated (seems it’s not just enough to enter the target in VAC’s main window dropdown).
Now everything apparently works fine. Thanks again for your support & for this excellent profile!
Uwe
-
Hi folks, I think I fixed the issue by explicitly disabling the “send to” setting in the “profile options” as the error message indicated (seems it’s not just enough to enter the target in VAC’s main window dropdown).
Now everything apparently works fine. Thanks again for your support & for this excellent profile!
Uwe
I also had/had this issue, except my voice command was sending it to anything that had “Falcon BMS” in the title, including tabs in Acrobat Reader, my file explorer if the path had “Falcon BMS” in the title - I’ll see later if @hoover’s fix works for me.
-
I’m a little confused about the “All-Human/Computer” aspect. In short, I’m testing as SP and assumed that in “All-Humans Mode is OFF” I could still add a single human player, but it tells me that the mode needs to be ON. But, if I’m in “All-Humans ON” and Remove All, the software explicitly tells me that I can add a single player.
This whole implementation confuses me, I guess because I don’t fully understand the use case.
Thanks in advance for any info.
-
This is a masterpiece. I’ve been testing it for 2 days and it keeps surprising me
I still don’t fully master all functionalities and I don’t quite understand all of it, but I’m getting there.
One particular little issue I have are “wildcards”. The profile works perfectly if I just pronounce the commands exactly as indicated in the Comms menus, but if I try to be creative (e.g. “Falcon 11, Ground, F16 two ships, request taxi for departure”) VA doesn’t recognize the phrase, whereas with “Request taxi for departure”, no problem.
Beats me, but I suppose the issue is on my end. If anyone has ideas… Thanks a lot.Judy
-
This post is deleted! -
Just did a test using the “active window” and notepad++, this doesn’t work either. (see screenshot below)
EDIT: Using the BMS 4.34 single callsign profile, I can send keypresses to notepad++ just fine.*Your attachment did not work, try using imgur or something simple to provide screenshot link in future.
What I had meant was to disable Send To all together, not even Active Window… this defaults to the window you are working with, i.e. Notepad – and then you can try a voice command to see what text it types.
Again, if not already done, programs need to be run as Administrator for most non-default functionality, etc.No worries, but I see the acronym VAC used too much to refer to VoiceAttack. VAC = Voice Activated Commands, which is a completely different and much older voice control program. VA = VoiceAttack and this is the term most of us use to differentiate and avoid confusion. Some people still use VAC and BMS includes a profile for it if I’m not mistaken. Just an FYI.
I also had/had this issue, except my voice command was sending it to anything that had “Falcon BMS” in the title, including tabs in Acrobat Reader, my file explorer if the path had “Falcon BMS” in the title - I’ll see later if @hoover’s fix works for me.
This is more of a problem than I had anticipated, and because it is more likely that it could cause issues than help, I have changed the default “Send to:” Target from Falcon BMS with the asterisks for wildcard name capture to direct “Falcon BMS.exe”. If it comes up that a user is having problems with this, they can go down the road of trying the wildcard method, or turning it off altogether (as Hoover did).
This is a masterpiece. I’ve been testing it for 2 days and it keeps surprising me
I still don’t fully master all functionalities and I don’t quite understand all of it, but I’m getting there.
One particular little issue I have are “wildcards”. The profile works perfectly if I just pronounce the commands exactly as indicated in the Comms menus, but if I try to be creative (e.g. “Falcon 11, Ground, F16 two ships, request taxi for departure”) VA doesn’t recognize the phrase, whereas with “Request taxi for departure”, no problem.
Beats me, but I suppose the issue is on my end. If anyone has ideas… Thanks a lot.Judy
The wildcard commands should basically disregard any words or phrases that come before the command as indicated in the Comms menu. I have had issues where I noticed VoiceAttack blending the last words of my “nonsense” part of the phrase with the actual command section that follows. Some tips you can try include adding brief but distinct pause between your first and second parts. But truly, to get an idea of how VoiceAttack is hearing you, you can add the Debug command to fire after every unrecognized command, and this will server to highlight exactly where a sentence has gone haywire.
Refer to the Reference Pics https://imgur.com/a/xuclI0a (link also included with the zip file), see the pic regarding “For debugging command recognition:” – (Open profile to edit, open Options along the top, select Profile Exec tab - see pic for example)
Get that going, do some tests and report back here if you still can’t identify why the wildcard commands won’t fire for you. There may be additional steps we could take to work on this, we’ll see.
-
I’m a little confused about the “All-Human/Computer” aspect. In short, I’m testing as SP and assumed that in “All-Humans Mode is OFF” I could still add a single human player, but it tells me that the mode needs to be ON. But, if I’m in “All-Humans ON” and Remove All, the software explicitly tells me that I can add a single player.
This whole implementation confuses me, I guess because I don’t fully understand the use case.
Thanks in advance for any info.
Okay - this is a MAJOR ISSUE. I looked into the profile, and cannot believe it went unnoticed!!! A last minute check had been added as we discussed the problem with accidentally being able to set a Human pilot while in All Humans Mode (the idea came up that this is essentially trying to remove a computer pilot). This absolutely should have been caught before the file went public, and was part of the DEV build not public. The files got confused at the last minute due to naming. In VA, you need to support a DEV version of your file and Public, if you want to use compressed binaries and not distribute a bunch of debug commands with the public version.
TLDNR; This has prompted me to immediately release a patch. Version 1.1 is now available, and all users should download and use only this version.
Download: (Click Here)
Patch Release v1.1 Changelog Nov2019 Fixes/Improvements: -Changed common Send To default from *Falcon BMS* to "Falcon BMS.exe" to avoid conflict with open PDF's, etc. with Falcon BMS in name -Fixed Human/Computer Pilots Registry system - last minute addition of a mode check was to blame, has been removed for now
-
IS AVCS v1.1 going to be compatible with 4.34.U1? I think there maybe some updates needed. Haven’t tried it yet just thinking ahead. I’m sure your on it SemplerPDX
-
No… it’s great this update has arrived for Xmas, but due to the timing and holidays (and holiday guests, etc.) I have little time to budget for this. First, I need to update my server for the public, then I need to check the radios list (and the changelog). Will be busy with it today. If there is any change, it will take less than a half hour for me to update it thanks to all the radio menus being in the keypress command, just a simple edit to reflect the new radios list (if any), and straight to publish.
-
Yea, it’s great this update has arrived for Xmas, but due to the timing and holidays (and holiday guests, etc.) I have little time to budget for this. First, I need to update my server for the public, then I need to check the radios list (and the changelog). Will be busy with it today. If there is any change, it will take less than a half hour for me to update it thanks to all the radio menus being in the keypress command, just a simple edit to reflect the new radios list (if any), and straight to publish.
I flew a test flight in GroundOps TE using AVCS and all seemed to be ok. I think maybe the only addition would be the ATC crossing command. Great work!
-
I cannot find any ATC crossing command in the radios menus, all i was able to do though was take a jet from taxi and drive it around with the keyboard to see if anything in the menus changed… Would I need to try it on a larger airbase, like Osan?
Looks like the only new addition is the new 7th item on page 6 of ATC for the carrier ‘Ready for Departure’ command. Anyway, will get it up asap. Sent a test version out, should be find. Added a few other checks and updates, but other than that it’s pretty much unchanged from 1.1 and I expect it to work just as well.
I expect to have it released just before or just after Xmas. Again, unless someone needs to use the Ready for Departure command on a carrier, the current version will work just fine for 4.34 U1. Cheers!
-
For the Falcon BMS 4.34 Update 1, I’ve updated this profile to include the new “Ready for Departure” call from the 7th choice on Page 6 of the ATC Radio Menu. I have added that command to the profile, but as it does conflict with the default “Ready for Departure” command, this Carrier specific command will need to be preceded by the word “Carrier” as a forced prefix word (see note in the large Command Reference pic).
Example use: “This is Joker 7-1, Carrier Ready for Departure”
I’ve also added a bit of polish to the Audio Feedback system, allowing it to recognize the word “feedback” as two words, “feed back”, to help us avoid repeating ourselves to get the commands to fire, as well as a null check on the Stereo Audio Feedback output channel, so it can recover if this saved setting is lost. I’ve also updated the minimum version of VoiceAttack, so please be sure to update your VA program.
We’ve tested this version, just minor additions, and everything seems great - but let me know if any issues pop up! Happy New Year!Download: (Click Here) ```
Patch Release v1.2 Changelog Dec2019
New Commands:
-“Carrier Ready for Departure” : for ATC Page 6, new 7th item added for 4.34 (U1) updateFixes/Improvements:
-Added additional recognition words for turning on/off Audio Feedback Mode - “feedback” can now be recognized as “feed back”
-Added Null Check on Audio Feedback Stereo Output Channel setting, if saved setting lost, will force user input on profile load
-Updated minimum VoiceAttack version to latest release (v1.8.3) for compatibility -
I did some further testing of 1.2 and it seems that if I say “Tower Ready for departure” the profile will type tt7 “which is abort” instead of tt1 “Ready For Departure”
I looked at the profile and the command ATC 2 - Tower Page shows when I say:
*Ready For Departure;*Request Landing;*Request Formation Landing;*Report On Final;*Report Overhead Break;*Tower Declare Emergency;*Tower Abort;*Tower Say Again
So it should work as designed but it doesn’t and I’m not sure why. Ready For Departure is the first in the list which should correlate to a 1 and not a 7.
I just checked version 1.1 and this did work. So something has changed with this particular call.
-
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.