AVCS4 Immersive Voice Control Radios for VoiceAttack
-
I’m trying to figure out how AVCS4 BMS for VA works. I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup. Core and AVCS4 BMS initialize ok. Alternative All-Humans Mode is OFF, Audio Feedback is On, Default keyboard QWERTY, UHF/VHF PTT mode is ON. I didn’t touch anything else in CORE/AVCS4 BMS profiles. Now I enter 3D and fly around Kunsan, I set UHF to 292.650 Kunsan’s ARR Approach frequency, push and hold my UHF button (UHF is highlighted) and request different approaches starting with: APPROACH Request (any) or APPROACH Declare Emergency…. Nothing happens. I check VAC recognizes commands Ok(green). What am I missing?
Do I need to add key strokes in the profile perhaps (not sure but I don’t think so)?Thanks.
Try turning PTT mode off. See if it all works well. PTT Mode (optional) is merely a helper to prevent recognizing commands during normal speech, but in reality, I rarely find AVCS4 BMS firing off commands when I am just talking to someone and not issuing commands to VoiceAttack.
You don’t need to add anything to the profile to work, but please do understand these profiles are a public beta test, and while so many things function exactly as designed, there are a number of minor issues and quirks that are still being worked out, as well as major systems like PTT Mode which are getting replaced/improved for the next version (ETA is right out the window, lost a week due to a blizzard here in Portland; spotty internet and occasional blackouts make work not worth the effort until this passes).
I have many ideas and many working proof of concepts for so many of the issues you all have reported, and I really appreciate the feedback! There’s only so much I can test myself, I have a modern gaming PC and a 2015 laptop and that’s it - not to mention human factors I could never test for. All these post really help - I’ll keep you all posted and reply when I have made some progress.
Cheers!
Amazdeus75 is correct that when PTT mode is on and set up correctly for a Push and a Release command, releasing this button too fast on a slower computer can cause the command to assume the PTT button is not held. This is also something I am working on improving, possibly using a key listener instead of the current method which sets a boolean variable to ‘true’ when a PTT key/button is depressed, and back to ‘false’ when released.
-
Amazdeus75 is correct that when PTT mode is on and set up correctly for a Push and a Release command, releasing this button too fast on a slower computer can cause the command to assume the PTT button is not held. This is also something I am working on improving, possibly using a key listener instead of the current method which sets a boolean variable to ‘true’ when a PTT key/button is depressed, and back to ‘false’ when released.
Yes, they mentioned that in this thread, I held PTT UHV/VHF buttons much longer but to no avail.
I’ll try vanila CORE/AVCS4 BMS profiles with a notepad first and see if that works.
Thanks!
-
Do I really nead to stop Nahimic app in the services? AV gives warning about it.
Thanks.
-
I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup.
Is that right?
Thanks.
-
I opened Notepad and saw AVCS4 Falcon BMS Rdios (v1.3.92b) profile printed my commands at last!
Why when I say:‘approach declare emergency’ all works good, keystrokes are sent, but when I say:‘tower declare emergency’ there are 2 red warnings: Key down by variable [~slection_key] not set. No keys pressed. and Rlease by variable [~selection_key] not set. No keys released. ? Keys not assigned perhaps? How to fix this?
Thanks.
-
Why when I say:‘approach declare emergency’ all works good, keystrokes are sent, but when I say:‘tower declare emergency’ there are 2 red warnings: Key down by variable [~slection_key] not set. No keys pressed. and Rlease by variable [~selection_key] not set. No keys released. ? Keys not assigned perhaps? How to fix this?
Thanks.
Same happens btw with ‘Tower say again’, ‘Tower abort’ - the communication is reconginzed (green) but gives red squares and no keystrokes are sent?
Thanks.
-
Do I really nead to stop Nahimic app in the services? AV gives warning about it.
Thanks.
This should not be an issue. I get that warning too, it’s related to an audio driver. Don’t worry about it.
(re. “I imported both core and AVCS4 bms profiles to VAC, AVCS CORE (v0.92b) is set as Global Profile in General Options (v1.8.7) and AVCS4 Falcon BMS Radios (v1.3.92b) is set to Load Profile on Startup.”)
Is that right?
Thanks.
Yes - that is just fine. Fastest way is to set BMS as a preferred profile in AVCS CORE, and set AVCS CORE to be the startup profile, but we’re talking about a difference of maybe 1 or 2 seconds faster load time, so don’t worry about it.
You also don’t need to set AVCS CORE to a Global Profile, but it won’t hurt anything. AVCS4 BMS physically includes the necessary commands from CORE so that users do not need to set CORE as a global profile or include it into BMS profile. AVCS CORE is designed to be able to function as a Global Profile in the event someone wanted to use it for other games, such as with the (optional) included AVCS CORE Template Profile in this beta, so there will be no issues however you set it up. If there are, please report them.
I opened Notepad and saw AVCS4 Falcon BMS Rdios (v1.3.92b) profile printed my commands at last!
Why when I say:‘approach declare emergency’ all works good, keystrokes are sent, but when I say:‘tower declare emergency’ there are 2 red warnings: Key down by variable [~slection_key] not set. No keys pressed. and Rlease by variable [~selection_key] not set. No keys released. ? Keys not assigned perhaps? How to fix this?
Thanks.
This may be an actual issue, like the “Check My Six” vs. “Clear My Six” bug we found earlier. I will look into this and reply back here by tomorrow. If this is a missing key, I can just patch it out and push out another live update (patch) while I continue to work on the next download full version update. Thanks!
-
This may be an actual issue, like the “Check My Six” vs. “Clear My Six” bug we found earlier. I will look into this and reply back here by tomorrow. If this is a missing key, I can just patch it out and push out another live update (patch) while I continue to work on the next download full version update. Thanks!
Please patch ‘Tower say again’, ‘Tower abort’ as well.
I like very much now how your profile recognizes my voice commands (on the notepad). I’d really like to learn how manipulate your Core and BMS Radios to a reasonable extent. Therefore I’d like to ask more questions about your package if you don’t mind:
-
How to set BMS as a preferred profile in AVCS CORE? )) Then (I’m using a batch file launcher) I’d like VA load up BMS by default - I guess I’ll remove AVCS CORE from Global Profiles menu in VA Options but leave AVCS4 Falcon BMS in Load Profile on Startup there, is that correct?
-
If I wanted to add a couple of my own simple cockpit switchology voice commands to your BMS how would I do that?
These are enough for now. I’ll try and go flying with your voice profile and see how it works in flight.
Many thanks!
-
-
Another note: it’s strange, but your Core doesn’t recognize my ‘yess’ well for some reason, could you add say ‘affirmative’, ‘positive’, ‘go on’ to the yes confirmation?
Thanks.
-
If I may ask more: Generally I’d like VA to stay idle (not listening) until I press and hold PTT button, in this case either COMM1 or COMM2 joystick buttons. Both of these buttons should turn on listening and recognition for BMS specific voice commands and any other custom ones added.
Thanks.
-
Do I need to set UHF/VHF transmit buttons anywhere in the profile or VA Options if I want AVCS4 Falcon profile use UHF/VHF PTT Mode?
I turned UHF/VHF PTT Mode On and now the profile doesn’t execute COMMS commands even though it hears and recognizes them (green).
Thanks.
-
Do I need to set UHF/VHF transmit buttons anywhere in the profile or VA Options if I want AVCS4 Falcon profile use UHF/VHF PTT Mode?
I turned UHF/VHF PTT Mode On and now the profile doesn’t execute COMMS commands even though it hears and recognizes them (green).
Thanks.
I’ve figured that out. I had to change buttons assignments in AVCS4 Falcon profile options, and modifty settings there to my actual UHF/VHF buttons.
This AVCS4 is amazing I’m very impressed how it picks up my voice commands in BMS, much better than when I’m trying to give some core commands.
Thank you very much.
PS: in my case I don’t even have to hold COMMS switches any much longer after my communication, your profile works with VA very fast
-
Hi All. Sorry for the question maybe stupid… It is possible to use Voice attack even in multi? Many thanks. Gundam
-
Hi Gundam
of course you can, you just have to set human pilots in AVCS4 BMS, thereby commands for those Human pilots are not taken into account by VA.
Very efficent -
Please patch ‘Tower say again’, ‘Tower abort’ as well.
I like very much now how your profile recognizes my voice commands (on the notepad). I’d really like to learn how manipulate your Core and BMS Radios to a reasonable extent. Therefore I’d like to ask more questions about your package if you don’t mind:
-
How to set BMS as a preferred profile in AVCS CORE? )) Then (I’m using a batch file launcher) I’d like VA load up BMS by default - I guess I’ll remove AVCS CORE from Global Profiles menu in VA Options but leave AVCS4 Falcon BMS in Load Profile on Startup there, is that correct?
-
If I wanted to add a couple of my own simple cockpit switchology voice commands to your BMS how would I do that?
These are enough for now. I’ll try and go flying with your voice profile and see how it works in flight.
Many thanks!
If you want to set BMS as the ‘preferred profile’, just say, “Set a preferred profile” to bring up that menu.
If you want to add a couple simple voice commands quickly, you can say, “Create a Voice Command” … if it’s just a single keypress, choose “Simple Keypress Voice Command(s)”, but if it’s many keypresses like these radio commands, choose “Advanced Voice Command(s)”
*To edit any of these commands created using my Quick Command Creator, just say, “Edit a Voice Command”.
Of course, you can always create new commands using the VoiceAttack program, just edit the AVCS4 BMS profile and create new commands however you want.
The profile recognizes most any way we can say “yes”, and if you want to add to this list, you can edit the config files through the Advanced CORE Options menu (say, ‘Open Advanced Core Options’) - but you should also make sure that VoiceAttack is recognizing you correctly. You should train your Windows Speech Recognition by running through the training sessions at least three times… refer to the VoiceAttack manual for details (press F1 when VoiceAttack is the top window).
Current “confirmed” responses (expanded from multi-part dynamic set) - edit or add to these in ‘avcs_core_data_1.cfg’ via the CORE Config Editor menu:
yes i do yes please yes it is yes i am yes i'm yes yep i do yep please yep it is yep i am yep i'm yep yup i do yup please yup it is yup i am yup i'm yup yeah i do yeah please yeah it is yeah i am yeah i'm yeah s i do s please s it is s i am s i'm s u.s. i do u.s. please u.s. it is u.s. i am u.s. i'm u.s. guess i do guess please guess it is guess i am guess i'm guess
My internet went out again and I haven’t been able to review the commands you noted as not working for you, not sure if anyone else who’s already familiar with AVCS could confirm that these are not working correctly, or if it’s other issues. I’ll have more time later today and/or tomorrow. Thanks for your patience during these betas!
-
-
I opened Notepad and saw AVCS4 Falcon BMS Rdios (v1.3.92b) profile printed my commands at last!
Why when I say:‘approach declare emergency’ all works good, keystrokes are sent, but when I say:‘tower declare emergency’ there are 2 red warnings: Key down by variable [~slection_key] not set. No keys pressed. and Rlease by variable [~selection_key] not set. No keys released. ? Keys not assigned perhaps? How to fix this?
Thanks.
Please patch ‘Tower say again’, ‘Tower abort’ as well.
I am completely stumped here as to why this typo ever got in, but I’m very glad you found it!
Seems there was an additional ‘AVCS_BMS_’ in the variable names. I’ve patched all three of these and you’ll all get the fix next time you load AVCS4 BMS.
AVCS_BMS_KEY_AVCS_BMS_ATC_TowerDeclareEmergency=6 AVCS_BMS_KEY_AVCS_BMS_ATC_TowerAbort=7 AVCS_BMS_KEY_AVCS_BMS_ATC_TowerSayAgain=8
Thanks again for finding this bug! Cheers!
-
Thanks for the patch!
-
Is the game supposed to repeat your command after you give it through voice command?
-
As you wish.
Look for the check box “Player voice” on the SETUP -> SOUND screen. -
@jc1:
Is the game supposed to repeat your command after you give it through voice command?
Kinda redundant, though, isn’t it? If you need positive feedback for recognition, you could say, ‘Turn on Audio Feedback Mode’ to play a short radio cue sound so you know your command went through and fired an AVCS4 keypress macro.