AVCS4 Immersive Voice Control Radios for VoiceAttack
-
@Badger Yeah, if you had sounds on for start/stop listening, this was probably throwing you off quite a bit and also making you assume you need to wait for the ‘listening on’ sound prompt before issuing a command.
Even if my PTT system has not yet enabled listening halfway through our sentence of some kind which is a voice command, the entire sentence (phrase) will still be evaluated for recognition. This is because that occurs only once we stop speaking, and by then, listening will have been enabled by my PTT system, and therefore the beginning of a command is never cut off. We can start talking immediately after depressing and holding down a PTT button in AVCS without waiting at all.
Another thing I want to double check with you is: Do you have any Push-to-Talk hotkey set in VoiceAttack options? Open it to this screen, and ensure it matches mine in the screenshot below - with Disabled or None as the Recognition Global, Mouse Click, or Joystick Button Recognition options. You should NOT have any of these set if using the PTT system in AVCS4 BMS:
…
EDIT 2: You should also open the AVCS4 BMS Profile, and its own Profile Options and if you have set ANY of these, remove them … none of this is required (or compatible) alongside my own internal PTT system which operates independently of VoiceAttack systems:
-
@SemlerPDX I have adjusted my settings to match what you’ve posted above. I’ll let you know how it works out. As you suspected the sound notifications were a hinderance.
-
@Badger Hi Badger. I’ve been using this profile for a few years. I’ve never used the PPT option, though I key the appropriate mic for transmission. This keeps the muscle memory for MP.
-
@SemlerPDX Everything seems to be in working order now. Thanks for sticking with me.
@Quasi_Stellar My thought was to use PTT UHF for the appropriate radio calls that would normally be made on UHF; AWACS, Tower, Tanker, etc. and VHF for other radio calls such as Request Hot Pit Refuel, and some external views.
-
Don’t know if this is the correct thread, and I admit I haven’t read through it, but I’m having difficulty with the wildcard commands. If I say e.g. "Tower Goblin 1 1 request landing " it doesn’t catch my command, but if I just say “request landing” it does.
Do I need to toggle setting somewhere?
-
@sepruda No, you don’t need to toggle anything anywhere.
I am unable to reproduce your issue, anything I say which ends in ‘request landing’ executes that command:
Have you trained your speech profile in Windows as recommended by VoiceAttack in the Quick Start Guide (at least 3 times completely through the training)?
-
@SemlerPDX I had not I admit. But I haven’t generally had issues with voice attack, and it always registers “Request landing” alone. I tried training it once now, but same result.
-
@sepruda I got a good suggestion from Max some time ago and installed FoxVox. Works great and has a bms profile available. Super easy install.
-
@b0bl00i Thanks! I did read about that, but I already bought a voice attack license, so sticking with that. Anyway it’s purely for immersion, using call names, and AVCS4 works very well for me mostly.
-
@sepruda I also bought Voice Attack but I never understood how to install and get everything running. Gave up after am evening tinkering with it.
-
@sepruda said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX I had not I admit. But I haven’t generally had issues with voice attack, and it always registers “Request landing” alone. I tried training it once now, but same result.
The only thing which will improve recognition for you is speech profile training. I feel you may either need to perform more training sessions, or to start over with a new Windows Speech Profile and begin training from scratch (3 times through completely, again). Once you have done so, you can backup your Windows Speech Profile so that you can restore it anytime, and unless your voice changes or you purchase a new microphone, you won’t ever have to perform the training again.
Alternatively, you could try giving a brief pause in your speech just before you say the “request landing” portion. Again, this shouldn’t be required as wildcards work just fine for me and several hundred other users of AVCS4 BMS Radios, but it has been suggested before and is a valid workaround.
Be sure to check out the Tips & How To page at VoiceAttack, as well as the Quick Start Guide in the VoiceAttack Manual (press F1 while VA is in focus):
http://voiceattack.com/howto.aspx…
@b0bl00i While Foxter and myself often cross promote each other, we don’t do so from within our own personal threads about our projects as we tend to focus on helping our users instead. I very much support anyone making voice control systems as it is my passion, and that includes Foxster. However, this particular forum post is about AVCS4 BMS Radios profile for VoiceAttack, and for helping users with that - it is inappropriate here (and a little embarrassing that I have to state as much) to suggest a different program as a solution to an issue a user is having with my own system(s). This user is having issues with recognition, and both FoxVox and VoiceAttack use the Windows Speech Recognition Engine which works off user created Speech Profiles in Windows - therefore, switching to a different program is not a valid solution to that.
-
@SemlerPDX
Question for VA users. Today I modified my TM TQS so that the UHF and VHF are both PTT.
In BMS, my goal was to have the UHF work with ATC and the only way to talk to my wingman or flight was to use VHF. Example: on the ground and if I push the PTT/VHF, I still communicate with ATC. I see the VHF light up on the ICP, but I would think ATC should not hear me. In the air with a wingman, I can comm with him with both UHF and VHF.I am NOT complaining. I can just continue with this as is. I just wonder if others see this.
Maybe there is a setting in VA that I missed.Semler, Your profile is awesome. Great job.
-
@huffer2 (Thank you for your kind words!) There is no internal systems which discern which PTT button is pressed, or which radio channel is tuned in (as in, which AI comms you could successfully issue orders on). In order to talk to ATC on the VHF channel (regardless of whether this callback is mapped to a PTT button in AVCS4 BMS), you will only need to have ATC tuned in on the VHF radio. You will see either the VHF or UHF highlight on the DED when these are used.
The only function a PTT button has in AVCS4 BMS is to enable listening globally or internally allow Radios commands to execute when recognized when my PTT system is active in either default or Global mode.
-
@SemlerPDX
I had a feeling you would say that. No big deal. I was just hoping it would work like in real life.
In GA, whatever freq I had tuned on Com1, and a different freq on Com2, you could keep comms separate.
BTW, I am so pleased that you showed me how to add simple voice commands to AVCS4. Using voice commands instead of reaching for the keyboard is very helpful. -
Hello everyone
Two days I try to make AVCS4 profile works (with the CORE profile too of course) but no joy! I run as administrator, PTT mode OFF, french keyboard selected (AZERTY). VA recognize my commands (“Request taxi for departure” for instance) (green square), radio set on the right frequency but in game nothing happen.
Have been reading parts of this thread, watched videos, read the manual. I guessed I missed something
Any ideas.
Thanks -
@Thierry If keypresses will not get through to your game, you might try addressing the .exe by name. Load the AVCS4 BMS Profile and open this profile in VoiceAttack using the Edit Profile button (or press ALT+E)
Surround the name with “*” (asterisks) for a wildcard name capture as Focus Target globally. You can also try simply “Falcon BMS.exe”, or “*Falcon BMS.exe”. The default action is set to Active Window which should work for most people, but if that does not work, you might try these direct targeting options.VoiceAttack should be running as Administrator under VoiceAttack Options (the Advanced tab along the top), and you can ensure no plugins are interfering with keypress commands by disabling plugin support for your testing. As a last test for keys not working, you can try increasing the TimeBetweenKeys and TimeKeyIsHeldDown variables … just say, “Open Keypress Timings Menu” command to adjust these timings globally for the entire profile. Test increases from default 0.05 up to as much as 0.10 to slow down keypress commands, whatever works for you.
If these things do not work, please report back and I will try to help further.
-
@SemlerPDX said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@Thierry If keypresses will not get through to your game, you might try addressing the .exe by name. Load the AVCS4 BMS Profile and open this profile in VoiceAttack using the Edit Profile button (or press ALT+E)
Surround the name with “*” (asterisks) for a wildcard name capture as Focus Target globally. You can also try simply “Falcon BMS.exe”, or “*Falcon BMS.exe”. The default action is set to Active Window which should work for most people, but if that does not work, you might try these direct targeting options.VoiceAttack should be running as Administrator under VoiceAttack Options (the Advanced tab along the top), and you can ensure no plugins are interfering with keypress commands by disabling plugin support for your testing. As a last test for keys not working, you can try increasing the TimeBetweenKeys and TimeKeyIsHeldDown variables … just say, “Open Keypress Timings Menu” command to adjust these timings globally for the entire profile. Test increases from default 0.05 up to as much as 0.10 to slow down keypress commands, whatever works for you.
If these things do not work, please report back and I will try to help further.
I have been trying a lot of things (changing keyboard to qwerty, trying diifferent exe name as a target as you mentionned) but It stll does not work. I could not modify the TimeBetweenKeys and TimeKeyIsHeldDown variables as the “Open Keypress Timings Menu” command does not open anything Maybe another way to access to this menu than voice command?
Thanks for your dedication
Thierry -
@Thierry Okay, so that is entirely a new issue - the keypress timings menu is unrelated to Falcon BMS and has no concern for what application is in focus. Please close VoiceAttack, then reload it and switch to AVCS4 BMS profile … wait until it is completely loaded, and then say, “Open the Keypress Timings Menu” - you should see a pop-up window exactly as the screenshot below shows. If your VoiceAttack window does not match mine (showing AVCS4 BMS fully initialized and reporting the state of Audio Feedback, All Humans Mode, and PTT Mode), please report back.
You might also try opening a simple notepad, and then issuing voice commands to verify that a correct string of letters followed by a number are typed out.
I certainly cannot recreate your issue with this menu command not working.
I’d suggest that you should access the integrated debugging system in AVCS. Say, “Create a bug report”, and then when it asks you to issue the command you are having troubles with, say, “Open the Keypress Timings Menu”, then say “Save Report” to save this report … next, follow the prompts to post the report to my website, instructions will direct you to place your cursor into the text body section of the report page, and then say “ready” or “done” to paste this report. You may review the content if you like, otherwise, just press the “SAVE” button to post.
-
@SemlerPDX
Sorry it was all my fault Didnt read the text in the main window with the initialization procedure. It seems to work now. Gonna test all the commands now
One question: is it possible to create commands not related to comms, for instance “gear” to get the gear up or down?
Thanks for your dedication and your great progamm!
Thierry -
@Thierry I use a number of non-com related commands like “visor” because I use VR and can’t see the keyboard. The command must have a related key press.
In this example I use Alt Launcher to allocate V to toggle visor ( or G or any key press to toggle Gear) and then go Voice Attack to create the command.
Works brilliantly.