wheelchock2

request vector to tanker for BMS profile actually changes my view rather than selecting the comms window commands for vector to tanker. Profile: AVCS4 BMS - Immersive Voice Control Radios Issue: Command(s) pressing wrong keys in game Profile Version: 1.3.91 VoiceAttack Version: 1.8.6 Steps to reproduce: vector to tanker || AI COMMS 2 - AWACS - Vector Page vector to tanker || AI COMMS 2 - AWACS - Vector Page Expected Behavior: default functional operation Observed Behavior: (see attached error log file, if available) Personal Testing: (AVCS Automated Debug and Reporting used) Comments: AVCS CORE Version: 0.91.1 F_CORE_MAIN Version: 0.91.1Session Command Count:96 RAM(total):17108287488 RAM(available):12607397888 LastCMD:request vector to tanker PreviousCMD:request factor to tanker Playback:Speakers (Realtek High Definition Audio) Playback(comms):Speakers (Realtek High Definition Audio) Playback Volume:30 Playback Mute:0 Microphone:Microphone (Realtek High Definition Audio) Microphone(comms):Microphone (Realtek High Definition Audio) Microphone Volume:100 Microphone Mute:0 Speech Device Volume:100 Speech Device Mute:0 JOYSTICK1:1 JOYSTICK2:0 JOYSTICK3:0 JOYSTICK4:0 GAMEPAD1:0 GAMEPAD2:0 GAMEPAD3:0 GAMEPAD4:0 AVCS CORE Profile: AVCS CORE (v0.91b) AVCS Profiles List: AVCS_PROFILE_AVCSCORE90=AVCS CORE (0.90b) AVCS_PROFILE_AVCSCORE91=AVCS CORE (v0.91b) AVCS_PROFILE_AVCSBMS91=AVCS4 Falcon BMS Radios (v1.3.91b) 220027652 CID:0 -DEBUG-##- || INFO: ==========================NEW REPORT========================== 220041163 CID:2518 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220041194 CID:2518 -DEBUG-000- || RID:1872 || CAT:AI COMMS 2 - AWACS - Vector Page 220046091 CID:3134 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220046091 CID:3134 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220046122 CID:3134 -DEBUG-000- || RID:1872 || CAT:AI COMMS 2 - AWACS - Vector Page 220050726 CID:3134 -DEBUG-04- || INFO: LOOP page = 2 - Keyboard Key has been pressed == Q 220051153 CID:3134 -DEBUG-04- || INFO: LOOP page = 1 - Keyboard Key has been pressed == Q 220051484 CID:3134 -DEBUG-05- || INFO: Command complete - ~avcs_prefix_target = AWACS || Current TimeKeyIsHeldDown = 0.05 || Current TimeBetweenKeys = 0.05 220051531 CID:3134 -DEBUG-05b- || INFO: Final Keyboard Key has been pressed == 4 220235144 CID:0 -DEBUG-##- || INFO: ==========================NEW REPORT========================== 220248421 CID:3009 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220248452 CID:3009 -DEBUG-000- || RID:2106 || CAT:AI COMMS 2 - AWACS - Vector Page 220253284 CID:1870 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220253284 CID:1870 -DEBUG-000- || IS:1 || ACT:Spoken || CMD:vector to tanker 220253315 CID:1870 -DEBUG-000- || RID:2106 || CAT:AI COMMS 2 - AWACS - Vector Page 220257909 CID:1870 -DEBUG-04- || INFO: LOOP page = 2 - Keyboard Key has been pressed == Q 220258328 CID:1870 -DEBUG-04- || INFO: LOOP page = 1 - Keyboard Key has been pressed == Q 220258670 CID:1870 -DEBUG-05- || INFO: Command complete - ~avcs_prefix_target = AWACS || Current TimeKeyIsHeldDown = 0.05 || Current TimeBetweenKeys = 0.05 220258717 CID:1870 -DEBUG-05b- || INFO: Final Keyboard Key has been pressed == 4 Severity / Status: Non-issue View full bug report

Ok so I found some sounds I can use, kind of like the ones you had there...They'll do in the interim until you get them backed in. I added the accepted sound as you stated...I'll do some testing and see if it works ok or not. EDITED: After adding the unrecognized sound to F_AVCS_VAS_INVALID_COMMAND I found that it was playing this sound for all kinds of stuff that it couldn't recognize. From hearing the dog barking to my own breathing. I guess I didn't notice that VA was picking all that stuff up until I heard it playing the unrecognized sound all the time. So I removed it since it isn't too helpful anyway. Knowing that I should hear the "beep beep" sound after a correctly recognized command was enough for me. if I don't here the beep beep sound I added then I know it didn't get what I said and I repeat it. Works pretty well. Maybe you can come up with something fancier than that. My next test will be enabling all humans flight with PTT set to OFF and see if that works well. if so I will most likely keep it that way, typically I only fly with people and not a mix of AI other than normal ones AWACS, TOWER, TANKER.

Hey man, been using the profile without too many complications...I do have one issue which isn't an issue more of a request. I've been wanting to turn off the comms menu in game (she hack to turn the menu into a pixel so you can see it) and if I do that that is the only way I know if my command was accepted or not. It would be cool if you could get some feedback if the command was accepted without having to look at the VoiceAttack window. I typically have my VA window covered up by Helios or some other tool. i've tried setting the DEBUG command in your profile to say "say again" if a command wasn't accepted but that only seems to apply to actual commands. It fails to work if it accepted the command but didn't quite reach the confidence level. At this point nothing happens. Is there some way to do what I'm asking?

So I did what you've suggested with regard to setting a different PTT key. I used the Coolio POV switch on the Warthog Throttle as my VA profile PTT key and then set PTT mode on for the VA profile. This would work for MP but in Single player I like to use the UHF and VHF keys as I normally would . I've just set PTT mode off in SP so my blind calls are picked up by the VA profile (usually) without the need to press my alternate PTT key. It's kind of clunky but so far it works for me. I don't know how else you could do it without it ending up being an issue.

Some nice additions and glad to see that you are actively developing this profile. It is my goto for BMS single player and am currently trying to work it in with MP. The MP side of it for me is just a trust issue mostly. I don't want to inadvertently trigger the tanker done refueling until I'm directed by my flight lead to do so, but the blind call of done refueling still needs to occur. I guess using PTT mode and setting it to something other than COM1,COM2 is the answer. Again nice work and looking forward to the finished product!

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?