AVCS4 Immersive Voice Control Radios for VoiceAttack
-
Thanks for sharing!
-
I just tried this profile and it looks like only the first keypress is sent to the correct BMS window whenever a command is activated. The mouse cursor appears on the BMS main window but no other menu actions are taken, only when I hit ESC a couple of times the correct initial menu is displayed.
I’ve tried both “Active Window” and “Falcon BMS” as keypress targets, other VAC profiles I’ve been playing around with (latest versions) don’t have this problem.
I’m using display extraction but that shouldn’t be a problem, right?
Thanks for sharing your work & all the best,
Uwe
-
I’m gonna keep trying to look into this, because I don’t have that issue, and have not heard it come up in testing yet (since May). I use display extraction as well.
A few questions come to mind, though I understand you’ve tried several good ideas already:
-We’re talking about keypress targets globally through the Profile Options, right? (just to verify not on the command level – default is Falcon BMS for wildcard name capture)
-Are you running VoiceAttack as Administrator? (this may be required for certain things)
-Are you running any Plugins that may interfere? (disabling any/all plugins for a troubleshoot test would be advised)
-Are the keypresses correct for your setup? (pressing 1-9 to select the radio menu items, and the appropriate QWERTY or alternate keyboard layout)You can test by turning off any focus targets and opening something like Notepad and calling a command. A correct command for ‘Flight Go Spread’ should look like: rrrrr6
Finally, if it is a timing thing, you can adjust the time any keypress is held down as well as the time between any keypresses throughout the profile with the two decimal variables labeled in the KEYPRESS_Variables command. They are at a default of 50 milliseconds, and you can try doubling that for a test to slow down the action of all commands.
//Pause Variables for Macros (default: 0.05 (round to 3 decimal places)) Set decimal [TimeBetweenKeys] value to 0.05 (round to 3 decimal places) Set decimal [TimeKeyIsHeldDown] value to 0.05 (round to 3 decimal places) ```^Change them to 0.10 for that test, should be slow enough for any PC that way… Whatever you test, you should only change one thing and then try it. Instant Action should be fine for some quick testing. If none of this works, post up and we can look deeper. We'll figure it out, trust me. It's something simple, surely. *see reference pics, some are about troubleshooting from the beta, I added one more for this: [https://imgur.com/a/xuclI0a](https://imgur.com/a/xuclI0a)
-
I just tried this profile and it looks like only the first keypress is sent to the correct BMS window whenever a command is activated. The mouse cursor appears on the BMS main window but no other menu actions are taken, only when I hit ESC a couple of times the correct initial menu is displayed.
I’ve tried both “Active Window” and “Falcon BMS” as keypress targets, other VAC profiles I’ve been playing around with (latest versions) don’t have this problem.
I’m using display extraction but that shouldn’t be a problem, right?
Thanks for sharing your work & all the best,
Uwe
display extraction is an issue if your using BMS to do it. This is because the Profile targets Falcon BMS and when you extract using just BMS it creates a separate sub-process for each extraction so the VA profile doesn’t know exactly which one to send it to. I got around this issue by targeting the actual process name Falcon BMS.exe, so no wild cards for the target. You can also just use Yame or some other extraction tool that doesn’t create multiple Falcon BMS windows.
-
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!