Jump to content
  • entries
    3
  • comments
    15
  • views
    352

AVCS4 - How to Control Falcon BMS 4.34 In-Game Radios with Voice Commands

 

AVCS4_BMS_Title_QUARTER.png

Profile for  VoiceAttack v1.7.6
by =VG= SemlerPDX

 

Description:

These commands use VoiceAttack to translate the in-game on-screen radio menus from AWACS through Tanker into natural and intelligent voice command phrases that will fire keypress macros to help keep hands on the throttle and stick, and maintain immersion.  As an additional option, these commands can be locked behind a push-to-talk mode bound to your UHF/VHF transmit buttons in-game, allowing any other VoiceAttack command unrestricted access if needed, while still restricting these BMS radio command macros.  Finally, the profile is extremely easy to edit or integrate into other profiles.

At VETERANS-GAMING, we fly with friends or AI Pilots, or a mix of both on our 24/7 Public Korean Campaign in Falcon BMS.  We may go out with an AI wingman only to have a friend take their place mid-flight.  For this reason and others, I created this VoiceAttack profile based around restricting when the computer can execute keypress macros that match voice phrases, having to first check if that pilot was set to a human pilot and therefore disregard commands for that pilot.

Thanks to user requests during the beta, there is now an optional mode to reverse the Human Pilots system, to assume all pilots are humans unless told otherwise, and also a system to choose a different keyboard layout than QWERTY.

 

Features:

GTB-BMS-Info1c_QUARTER.gifGTB-BMS-Info2c_QUARTER.gifGTB-BMS-Info3c_QUARTER.gif
*Push-To-Talk mode disabled by default.  Say, "Turn On Push To Talk Mode" to enable
**Follow Instructions inside profile to set Push-To-Talk buttons to match BMS UHF/VHF keys

 

Download: (tbd - after beta - almost there as of mid-July 2019, try out the final beta v0.99 below!)

 

Beta_Banner_VG3_468x60.png

*Looking for some testers who already use VoiceAttack, and who are already familiar with Falcon BMS & flying with AI pilots
Beta Test Requirements & Instructions:

spoilerIMG2415905122018.PNG
  • *Must have Falcon BMS 4.34 installed
  • *Must have registered version of VoiceAttack installed
     
  • Launch VoiceAttack and open Options (wrench icon in lower right)
  • -Under last tab on top, System/Advance, check box next to "Use Nested Tokens" as in image 1 below
  • -Unless absolutely required, during testing it's recommended to uncheck "Allow command segment info for composite commands"
     
  • Download and Import the current beta version of this profile here: https://www.dropbox.com/ ... Voice Control Radios 0.99b for Falcon BMS/..
  • *On first import, you should say, "Initialize Profile" - after first time, this is automatic.  Any attempt to use commands before this will trigger auto-initialization.
  • Open the profile - if not already done, group commands by category and consolidate multi-part commands as in image 2 & 3 below
  • Click on the Description tab at the top to help sort commands further (see image 4)
     
  • Read a semicolon ";" as the word "or" and look at long commands as having many options like saying "2;Two;Too;To;Wingman"  (read as "2 -or- Two -or- Too -or- To -or- Wingman")
  • Attempt to follow instructions in Profile Commands and comments to Initialize Profile, Set Push-To-Talk buttons if desired, Set a Human Pilot, Delete Human Pilots, etc.
  • Also, please try the inverse All-Humans mode which assumes all pilots are Humans - Set a Computer Pilot, Delete Computer Pilots, etc. - this is a new system in the July 0.99b Update & should be tested.
  • Launch Falcon BMS 4.34 and fly test flights with AI pilots or mixed with Human pilots and please report any issues when calling commands & any frequently unrecognized words, or any errors/problems

image 1image 2image 3image 4

 

 

Commands Reference:

HumansListCommands_QUARTER.png
*Replace the word "Human" with "Computer" when All-Humans Mode is ON
Normally, this profile assumes all pilots are Computers, use All-Humans Mode to invert this
 

RadioMenusReference_FULL.png
 

 

 

14 hours ago, =VG= SemlerPDX said:

BETA UPDATED TO v0.99 (final beta!)

Please download newest version!  Link updated in the main post above!  You don't have to remove the 0.98 beta profile, but it is recommended to not use both at the same time or variables may get messed up.  Thanks to everyone for helping to finish up final testing!


Per request, to speed up the interaction of adding/removing pilots from the exclusion lists, you can now say the entire Callsign + Flight Number + Wing Number when asked for the callsign. 

Example: 
"Set a Human Pilot"
"say the callsign"
"Cowboy 7 3"
"Cowboy 7 3 - is this correct?"
"Yes"
...
(bypassing the need to individually set Flight Number and then Wing Number!)

This will jump to the confirmation at the end of the command and greatly reduces the time spent interacting with the voice control system configuration.   During my testing, I found there must be a clear separation between the Flight Number and Wing Number when spoken, to avoid "Cowboy 7 3" getting recognized as "Cowboy 73", and your own results may vary.  Please test and let me know.  The old system is still in place, and you can even just say the Callsign + Flight number, and it will notice and skip to the Set Wing Number segment of the script.  The entire idea was to allow a lot of options to recognize how we speak, and the only catch is that we need to enunciate and keep succinct breaks between words for this style of input.  Further beta testing in this final 0.99 phase should help judge if this will work or if it needs adjustment.


Additionally, there are now VoiceAttack command log notifications whenever the profile loads showing the current profile settings, and also voice notifications if either PTT mode or the new All-Humans mode are On. 
 

Here's a copy of the changelog:


Beta v0.99 Changelog Jul2019
New Commands:
 -Change Default Keyboard Layout allows choices between QWERTY, QWERTZ, & AZERTY (per user request)
 -Turn On/Off All-Humans Mode : Reverse mode assumes all pilots are humans, add Computer Pilots individually as needed (per user request)
 -Copy of all Add/Remove Human Pilots commands for Computer Pilots & All-Humans Mode

Fixes/Improvements:
 -Can state an entire callsign plus flight & wing numbers when asked for Callsign (per user request to speed up the voice system interaction of adding/removing human pilots)
 -VoiceAttack log entries displays profile information on startup (current keyboard layout, push-to-talk mode on/off state, All-Humans mode on/off state) (per user request)
 -Speech notifications on startup for PTT mode and All-Humans mode if they are enabled (see above)
 -Forced profile initialization if not initialized on any command use (per bug report: on first download/import of profile, trying to use any command fails until voiceattack restarted)

 

 



12 Comments


Recommended Comments

14 hours ago, =VG= Kavelenko said:

OMFG! More shit I gotta learn rofl.

I agree - when they changed up the radios and radio menus for 4.34, I started by taking pics of all of them (the bottom graphic) just to wrap my head around the changes.  Then I built this voice control profile so I didn't have to memorize anything (except those 5 "add/remove hoomans" commands).  To use this profile myself, I have that bottom image on my tablet or phone just as an image reference so I can see "what" I can ask of AWACS or other contacts, in case something is new.  I certainly don't know everything by memory myself, but I also don't find that I use everything in every flight.  I definitely use the AWACS and ATC stuff a lot, and the ATC has really changed!  A little learning is half the fun of a sim, right? haha!
:hi:

  I'm relying heavily on Jeffu's blog post here to figure out these new features in Falcon BMS 4.34: 

 

Share this comment


Link to comment

hi =VG= Kavelenko,

I am testing  your beta profile. For me it works fine. I just need to learn the proper commands, but one done, it is ok.

The way you have write the profile is unusual for me, and at that time, I am not sure to fully understand it. But no matter.

As a french user i just need to set windows10 with US keyboard. My windows is in english version.

Really good job, I love to use it. Thanks

 

  • Like 1

Share this comment


Link to comment

Thank you very much!  (It's my profile, not Kavelenko ;) - lost in translation, I'm sure, don't worry about it!)

I had a feeling that the profile may look odd, all of my AVCS4 profiles follow a similar format, and must be grouped by category in order for the list to look correct.  By consolidating multi-part commands, and collapsing all categories, it should begin to appear much more ordered.  I enjoy placing as much as possible into "initialization" scripts so that if I change anything later, I can make changes in one place.  If you look inside most of the commands like "go stack;go spread;..." their content is almost exactly the same as the next or previous commands, and again, this makes it very easy to expand or edit in future if needed.

I would love to work with someone to add localization to this profile!  If we could translate my command words into French, and if Windows Voice Recognition and VoiceAttack both work in the French language, it would be very easy to modify this profile.  Again, all speech variables are in one file, so anything spoken by the profile can be changed to any language without hunting for them throughout the profile.  And editing the commands themselves would let you change any of the command words to French equivalents.  Proper nouns would likely remain the same, of course, OR you could change ALL callsigns in the profile to different ones if you edit the .vap and find/replace all.  I'll include a readme with instructions on changing/adding callsigns to the .vap profile file before the beta is finished.

If anyone would like to help with localization, RSVP

:hi:

Share this comment


Link to comment

Hi SemlerPDX

Of  course Speech recognition and Voice Atack can work with French. Even if I don't use it, I could do the translation I think. There is an other issue you need to take into account, and wich is maybe first, this is the AZERTY keyboard instead of the QUERTY one.

IN my opinion, Most of french, german ... people are playing  with english speech recognition but are not used to transpose the keys from onr type of keyboard to another one

Windblow

 

  • Like 1

Share this comment


Link to comment

Thanks for the feedback!  If people prefer English for VoiceAttack, there is no sense to waste time on localization.

I believe I can include an option for QUERTY or AZERTY.

Is this correct?
 

// AI COMMS Menu Lists
Set Text [KEY_AWACS_LIST] to 'A'
Set Text [KEY_WINGMAN_LIST] to 'Z'
Set Text [KEY_ELEMENT_LIST] to 'E'
Set Text [KEY_ATC_LIST] to 'T'
Set Text [KEY_FLIGHT_LIST] to 'R'
Set Text [KEY_TANKER_LIST] to 'Y'

 

Share this comment


Link to comment

Yes  it is  correct  for  these commands ...

Hi SemlerPDX

Of  course Speech recognition and Voice Atack can work with French. Even if I don't use it, I could do the translation I think. There is an other issue you need to take into account, and wich is maybe first, this is the AZERTY keyboard instead of the QUERTY one.

IN my opinion, Most of french, german ... people are playing  with english speech recognition but are not used to transpose the keys from onr type of keyboard to another one

Windblow

 

  • Upvote 1

Share this comment


Link to comment

in addition, you could include german Keyboard, which is a QWERTZ one ( see chap 4-29 list of keyboard layout, in the technical BMS Manual)

  • Like 1

Share this comment


Link to comment

I know this is a Stretch but what about a status command that gives you a run down on what features are on and what human pilots are set? 

  • Upvote 1

Share this comment


Link to comment

*For anyone with issues, per a message I received about keys not getting through:
You can ensure that keys are getting sent to the application by opening the VoiceAttack Profile, and clicking on Options along the top, and select "Send commands to this target" and then write in *Falcon BMS* between asterisks (*) for a wildcard catchall for the BMS game window.

This will ensure these keystrokes go where they are needed.  See image:
AVCS4sendToBMS.PNG

Share this comment


Link to comment

SitRep:
I have several great suggestions and will be working on adding several of these ideas to the next working beta (0.99b), if possible.  My release plan is simply this beta, and the 0.99b beta, for a few weeks until VoiceAttack beta that we are using gets it's own release, and then I'll add any final changes and polish, and release it as a version 1.0 - I don't expect much need for editing in future unless the radio menus get changed again, but will maintain the profile and entertain any useful suggestions even after final release.

If anyone has any other suggestions, feel free to let me know!  Thanks for all the feedback so far!

:hi: 

  • Like 1

Share this comment


Link to comment

BETA UPDATED TO v0.99 (final beta!)

Please download newest version!  Link below and updated in the main post above!  You don't have to remove the 0.98 beta profile, but it is recommended to not use both at the same time or variables may get messed up.  Thanks to everyone for helping to finish up final testing!

SitRep:

I've finished integrating the proposed changes I received through the v0.98 beta, and the v0.99 beta is now available for download (click here).  There is now an alternate All-Humans Mode that can be turned on, and will assume all pilots are humans unless you individually set Computer Pilots per callsign/flight/wing numbers.  All the same "Set a Human Pilot" commands have been copied to make "Set a Computer Pilot" equivalents.

You can also change the Keyboard Layout from the default QWERTY by voice command or just executing the "change" command found under initialization.

Per request, to speed up the interaction of adding/removing pilots from the exclusion lists, you can now say the entire Callsign + Flight Number + Wing Number when asked for the callsign. 

Example: 
"Set a Human Pilot"
"say the callsign"
"Cowboy 7 3"
"Cowboy 7 3 - is this correct?"
"Yes"
...
(bypassing the need to individually set Flight Number and then Wing Number!)

This will jump to the confirmation at the end of the command and greatly reduces the time spent interacting with the voice control system configuration.   During my testing, I found there must be a clear separation between the Flight Number and Wing Number when spoken, to avoid "Cowboy 7 3" getting recognized as "Cowboy 73", and your own results may vary.  Please test and let me know.  The old system is still in place, and you can even just say the Callsign + Flight number, and it will notice and skip to the Set Wing Number segment of the script.  The entire idea was to allow a lot of options to recognize how we speak, and the only catch is that we need to enunciate and keep succinct breaks between words for this style of input.  Further beta testing in this final 0.99 phase should help judge if this will work or if it needs adjustment.


Additionally, there are now VoiceAttack command log notifications whenever the profile loads showing the current profile settings, and also voice notifications if either PTT mode or the new All-Humans mode are On. 
 

Here's a copy of the changelog:

Beta v0.99 Changelog Jul2019
New Commands:
 -Change Default Keyboard Layout allows choices between QWERTY, QWERTZ, & AZERTY (per user request)
 -Turn On/Off All-Humans Mode : Reverse mode assumes all pilots are humans, add Computer Pilots individually as needed (per user request)
 -Copy of all Add/Remove Human Pilots commands for Computer Pilots & All-Humans Mode

Fixes/Improvements:
 -Can state an entire callsign plus flight & wing numbers when asked for Callsign (per user request to speed up the voice system interaction of adding/removing human pilots)
 -VoiceAttack log entries displays profile information on startup (current keyboard layout, push-to-talk mode on/off state, All-Humans mode on/off state) (per user request)
 -Speech notifications on startup for PTT mode and All-Humans mode if they are enabled (see above)
 -Forced profile initialization if not initialized on any command use (per bug report: on first download/import of profile, trying to use any command fails until voiceattack restarted)

 

 

*wheelchock2 had asked about a query system.  I have not made a system to ask which callsigns have been set/saved to either a Human Pilot or Computer Pilot, as it was always designed to be a throw-away use concept, add a few for the afternoon, adjust for different flights, reset at the end or beginning of a days' use of Falcon BMS.  I'd like to know if there is serious interest in a query system before I create one as it will add a bit of size to the profile, increase it's RAM footprint further, and possibly increase profile load time even further.  It would not make sense to add this if there is too little use for it.  Personally, I remove all human pilot callsigns before every flight, when I'm at the 2D map/mission planning phase.  Please let me know how you guys use the profile, and if you'd use something like a query system.

  • Like 1

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×