AVCS4 Immersive Voice Control Radios for VoiceAttack
-
SemlerPDX, hello and thanks SO MUCH for your detailed answer to my dumb question! I’ll give this a go, I’m sure it’s going to work.
I’ve read all the pages of this thread and I am overwhelmed with admiration not only for your skill in making this software, for your generosity in making it available for free, and for the staggering amount of patience you’ve shown over 22 pages of this thread!
Best wishes from a rainy England
Alan
-
Update: success, it works, it’s like magic! SemlerPDX, thank you once again!
regards
Alan -
Just in case someone else needs something like my added commands, here they are from my save.txt:
AVCS_BMS_COMMANDS_AI COMMS 1 - Formation Management 1=Close Up;Switch Side;Shackle;Break Right;Break Left;Go Higher;Go Lower;Flex;Take The Lead;Kickout AVCS_BMS_KEY_ELEMENT_Shackle=2 AVCS_BMS_KEY_FLIGHT_Shackle=2 AVCS_BMS_KEY_WINGMAN_Shackle=2 AVCS_QCC_COMMAND_MAX=75 AVCS_QCC_DATA_MACROS_1=QCC#1[(1)]1[(2)]EXEC[(4)]Request Air Refueling[(3)] AVCS_QCC_DATA_MACROS_2=QCC#2[(1)]1[(2)]EXEC[(4)]Request Picture[(3)] AVCS_QCC_DATA_MACROS_3=QCC#3[(1)]1[(2)]EXEC[(4)]Declare[(3)] AVCS_QCC_DATA_MACROS_4=QCC#4[(1)]1[(2)]EXEC[(4)]request help[(3)] AVCS_QCC_DATA_MACROS_5=QCC#5[(1)]1[(2)]EXEC[(4)]wilco[(3)] AVCS_QCC_DATA_MACROS_6=QCC#6[(1)]1[(2)]EXEC[(4)]unable[(3)] AVCS_QCC_DATA_MACROS_7=QCC#7[(1)]1[(2)]EXEC[(4)]check in[(3)] AVCS_QCC_DATA_MACROS_8=QCC#8[(1)]1[(2)]EXEC[(4)]check out[(3)] AVCS_QCC_DATA_MACROS_9=QCC#9[(1)]1[(2)]EXEC[(4)]request relief[(3)] AVCS_QCC_DATA_MACROS_10=QCC#10[(1)]1[(2)]EXEC[(4)]Request Rescue Chopper[(3)] AVCS_QCC_DATA_MACROS_11=QCC#11[(1)]1[(2)]EXEC[(4)]Vector To Nearest Air Threat[(3)] AVCS_QCC_DATA_MACROS_12=QCC#12[(1)]1[(2)]EXEC[(4)]Vector To Target[(3)] AVCS_QCC_DATA_MACROS_13=QCC#13[(1)]1[(2)]EXEC[(4)]Vector To Package[(3)] AVCS_QCC_DATA_MACROS_14=QCC#14[(1)]1[(2)]EXEC[(4)]vector to tanker[(3)] AVCS_QCC_DATA_MACROS_15=QCC#15[(1)]1[(2)]EXEC[(4)]vector to divert field[(3)] AVCS_QCC_DATA_MACROS_16=QCC#16[(1)]1[(2)]EXEC[(4)]Vector To Home Plate[(3)] AVCS_QCC_DATA_MACROS_17=QCC#17[(1)]1[(2)]EXEC[(4)]vector to carrier group[(3)] AVCS_QCC_DATA_MACROS_18=QCC#18[(1)]1[(2)]EXEC[(4)]Back In Pre Contact Position[(3)] AVCS_QCC_DATA_MACROS_19=QCC#19[(1)]1[(2)]EXEC[(4)]done refueling[(3)] AVCS_QCC_DATA_MACROS_20=QCC#20[(1)]1[(2)]EXEC[(4)]Install EPU Ground Safety Pin[(3)] AVCS_QCC_DATA_MACROS_21=QCC#21[(1)]1[(2)]EXEC[(4)]Remove EPU Ground Safety Pin[(3)] AVCS_QCC_DATA_MACROS_22=QCC#22[(1)]1[(2)]EXEC[(4)]install chocks[(3)] AVCS_QCC_DATA_MACROS_23=QCC#23[(1)]1[(2)]EXEC[(4)]remove chocks[(3)] AVCS_QCC_DATA_MACROS_24=QCC#24[(1)]1[(2)]EXEC[(4)]Request Taxi For Departure[(3)] AVCS_QCC_DATA_MACROS_25=QCC#25[(1)]1[(2)]EXEC[(4)]Request Taxi To Ramp[(3)] AVCS_QCC_DATA_MACROS_26=QCC#26[(1)]1[(2)]EXEC[(4)]Request Hotpit Refuel[(3)] AVCS_QCC_DATA_MACROS_27=QCC#27[(1)]1[(2)]EXEC[(4)]Ground Say Again[(3)] AVCS_QCC_DATA_MACROS_28=QCC#28[(1)]1[(2)]EXEC[(4)]Ready For Departure[(3)] AVCS_QCC_DATA_MACROS_29=QCC#29[(1)]1[(2)]EXEC[(4)]Request Landing[(3)] AVCS_QCC_DATA_MACROS_30=QCC#30[(1)]1[(2)]EXEC[(4)]report on final[(3)] AVCS_QCC_DATA_MACROS_31=QCC#31[(1)]1[(2)]EXEC[(4)]report overhead break[(3)] AVCS_QCC_DATA_MACROS_32=QCC#32[(1)]1[(2)]EXEC[(4)]Tower Declare Emergency[(3)] AVCS_QCC_DATA_MACROS_33=QCC#33[(1)]1[(2)]EXEC[(4)]tower abort[(3)] AVCS_QCC_DATA_MACROS_34=QCC#34[(1)]1[(2)]EXEC[(4)]Tower Say Again[(3)] AVCS_QCC_DATA_MACROS_35=QCC#35[(1)]1[(2)]EXEC[(4)]Request Vectors For Visual Approach[(3)] AVCS_QCC_DATA_MACROS_36=QCC#36[(1)]1[(2)]EXEC[(4)]Request Vectors For Instrument Approach[(3)] AVCS_QCC_DATA_MACROS_37=QCC#37[(1)]1[(2)]EXEC[(4)]Request Overhead Approach[(3)] AVCS_QCC_DATA_MACROS_38=QCC#38[(1)]1[(2)]EXEC[(4)]Request Unrestricted Approach[(3)] AVCS_QCC_DATA_MACROS_39=QCC#39[(1)]1[(2)]EXEC[(4)]Approach Declare Emergency[(3)] AVCS_QCC_DATA_MACROS_40=QCC#40[(1)]1[(2)]EXEC[(4)]approach abort[(3)] AVCS_QCC_DATA_MACROS_41=QCC#41[(1)]1[(2)]EXEC[(4)]traffic in sight[(3)] AVCS_QCC_DATA_MACROS_42=QCC#42[(1)]1[(2)]EXEC[(4)]Approach Say Again[(3)] AVCS_QCC_DATA_MACROS_43=QCC#43[(1)]1[(2)]EXEC[(4)]airborne[(3)] AVCS_QCC_DATA_MACROS_44=QCC#44[(1)]1[(2)]EXEC[(4)]Request QNH[(3)] AVCS_QCC_DATA_MACROS_45=QCC#45[(1)]1[(2)]EXEC[(4)]Request QFE[(3)] AVCS_QCC_DATA_MACROS_46=QCC#46[(1)]1[(2)]EXEC[(4)]Takeoff Runway[(3)] AVCS_QCC_DATA_MACROS_47=QCC#47[(1)]1[(2)]EXEC[(4)]Landing Runway[(3)] AVCS_QCC_DATA_MACROS_48=QCC#48[(1)]1[(2)]EXEC[(4)]request wind check[(3)] AVCS_QCC_DATA_MACROS_49=QCC#49[(1)]1[(2)]EXEC[(4)]Request Ground Abort 1[(3)] AVCS_QCC_DATA_MACROS_50=QCC#50[(1)]1[(2)]EXEC[(4)]Request Ground Abort 2[(3)] AVCS_QCC_DATA_MACROS_51=QCC#51[(1)]1[(2)]EXEC[(4)]Request Ground Abort 3[(3)] AVCS_QCC_DATA_MACROS_52=QCC#52[(1)]1[(2)]EXEC[(4)]Request Ground Abort 4[(3)] AVCS_QCC_MACROS_1=*request fuel;*request observation;*request precontact;*request prix contact;*request rejoin AVCS_QCC_MACROS_2=*picture;*say picture AVCS_QCC_MACROS_3=*declare bullseye;*declare contact;*declare contact bullseye;*declare target;*declare target bullseye AVCS_QCC_MACROS_4=*help needed;*fighter assistance;*fighter support AVCS_QCC_MACROS_5=*request granted AVCS_QCC_MACROS_6=*cannot comply;*request denied AVCS_QCC_MACROS_7=*checking in;*on station AVCS_QCC_MACROS_8=*checking out;*is are TB;*leaving station;*off station AVCS_QCC_MACROS_9=*request are TB AVCS_QCC_MACROS_10=*request chopper;*so are;*Search and rescue; AVCS_QCC_MACROS_11=*bogey dope;*tumbleweed;*where is the nearest threat AVCS_QCC_MACROS_12=*i need a target;*request vector to target;*vector to assigned target;*vector to planned target AVCS_QCC_MACROS_13=*request package posit AVCS_QCC_MACROS_14=*i need a tanker;*tanker posit;*request vector to nearest tanker; AVCS_QCC_MACROS_15=*i need a divert field;*request vector to alternate;*request vector to divert field AVCS_QCC_MACROS_16=*pigeons AVCS_QCC_MACROS_17=*vector mother AVCS_QCC_MACROS_18=*prix contact;*prix contact position;*stablized;*stablized and ready AVCS_QCC_MACROS_19=*disconnect;*finished refuelling;*request disconnect;*showing a full tank;*tank is full;*topped off;*topped off and ready to go AVCS_QCC_MACROS_20=*install eepeeyou pin AVCS_QCC_MACROS_21=*remove eepeeyou pin AVCS_QCC_MACROS_22=*place chocks AVCS_QCC_MACROS_23=*pull chocks AVCS_QCC_MACROS_24=*ready to taxi;*taxi to runway AVCS_QCC_MACROS_25=*taxi back to parking AVCS_QCC_MACROS_26=*ready for hotpit refuel AVCS_QCC_MACROS_27=*Ground repeat last AVCS_QCC_MACROS_28=*ready for takeoff;*request takeoff AVCS_QCC_MACROS_29=*inbound for landing; *inbound AVCS_QCC_MACROS_30=*on final;*base three green;*final three green AVCS_QCC_MACROS_31=*on the break;*breaking AVCS_QCC_MACROS_32=*declaring an emergency tower;*tower i'm an emergency aircraft AVCS_QCC_MACROS_33=*going around;*on the go;*missed approach AVCS_QCC_MACROS_34=*tower repeat last AVCS_QCC_MACROS_35=*request the visual AVCS_QCC_MACROS_36=*vectors for i.l.s. AVCS_QCC_MACROS_37=*request overhead pattern AVCS_QCC_MACROS_38=*approach own navigation;*request full I.L.S. approach;*request full TACAN approach AVCS_QCC_MACROS_39=*mayday mayday mayday;*declaring an emergency approach AVCS_QCC_MACROS_40=*aborting approach;*executing missed approach procedure AVCS_QCC_MACROS_41=*has a visual on the traffic AVCS_QCC_MACROS_42=*say again approach AVCS_QCC_MACROS_43=*on departure AVCS_QCC_MACROS_44=*altimeter setting AVCS_QCC_MACROS_45=*field elevation setting AVCS_QCC_MACROS_46=*departure runway AVCS_QCC_MACROS_47=*landing runway AVCS_QCC_MACROS_48=*wind check AVCS_QCC_MACROS_49=*one is ground aborting AVCS_QCC_MACROS_50=*two is ground aborting AVCS_QCC_MACROS_51=*three is ground aborting AVCS_QCC_MACROS_52=*four is ground aborting
This is still a bit of a work in progress for me too, but possibly a good starting point. Thanks again SemlerPDX for this great work!
-
Push to talk is enabled. VoiceAttack is recognizing my commands. But I’m not getting a response to my commands in the game. What could be causing this?
-
@jc1:
Push to talk is enabled. VoiceAttack is recognizing my commands. But I’m not getting a response to my commands in the game. What could be causing this?
Typical cause for this with BMS and all programs that send key commands is make sure you are running the program as Administrator. Try that first would be my recommendation.
-
Yes, I’m running as adminstrator. Seems that voiceattack recognizes my command before the game, but in game it’s as if the mic is not on. And Windows shows the mic is working.
-
@jc1:
Push to talk is enabled. VoiceAttack is recognizing my commands. But I’m not getting a response to my commands in the game. What could be causing this?
@jc1:
Yes, I’m running as adminstrator. Seems that voiceattack recognizes my command before the game, but in game it’s as if the mic is not on. And Windows shows the mic is working.
If VoiceAttack is recognizing commands outside the game, but not when BMS is active or fullscreen, then it could be related to microphone issues and not the profile or Push to talk system.
Can you see the microphone bar moving in the VoiceAttack window? Does it behave as if your microphone is muted when you are in game in BMS, but not when you are outside the game?
Sometimes this can be as simple as another program taking exclusive control of the recording device (IVC perhaps) and “stealing” it away from VoiceAttack once BMS has loaded up. If that is the case, it could be as simple as disabling exclusive control of your microphone in Windows Sound settings - under the Advanced tab of the Properties window for your device, uncheck the box circled and hit OK or Apply… give it a test and see if it worked, and if not, you may need to start troubleshooting:
(find your microphone under the ‘Recording’ tab along the top - then select it and click Properties and the Advanced tab)…if that doesn’t work:
Disable Push to Talk mode for a test, then call a proper radio command and see if it fires in-game. Alt-tab to the VoiceAttack window to see if it captured speech in the event log. Below the event log, VoiceAttack has an indicator which moves when speech is detected. If you set this program to “Always on top” in Options, you can see if this bar is moving when you speak while BMS is the active window.Are commands recognized in game when you have Push to Talk disabled?
Are you using the ‘global’ mode for Push to Talk, or the default mode?
Last questions … is the microphone icon showing a red marker like this indicating a ‘muted’ state:
…and if using “global” Push to Talk mode, is it swapping to ‘unmuted’ state when you push the PTT button(s) you have set like this:
-
This is what I get. Although there was a response in No PTT, even with the remark at the top of that picture, I couldn’t get any more responses in No PTT. In PTT mode, the commands were recognized but there was no response. In both cases the sound bar did move at the bottom of VoiceAttack. I don’t know what to make of it. I didn’t test global vs default because I’m not familiar with that. I hope this picture gives you some new ideas to help find out why there is no response to my voice commands. And thanks for all you’ve done.
The Windows mic test showed the mic working in 2D, as this picture shows.
-
@jc1:
This is what I get.
…Apologies, I had not realized you weren’t using the latest version of AVCS4 BMS Radios. The version pictured in your screenshots (v1.3) is depreciated, and no longer supported. So many issues were fixed and evolved in the current systems, I’m sure you’ll be fine if/when you upgrade/update (including resolving your error finding the AFM sound file shown in the top most image). The current version of AVCS is even capable of debugging for you, to help you see where and why your PTT button is not being detected by the PTT system, or even generate a semi-automated bug report if you want, for example.
The AVCS4 BMS download package is presently on version 1.40 and this also requires the “hub” profile AVCS CORE (v1.0) which handles initialization of the AVCS4 BMS profile (and any others I release). You do not need to remove AVCS4 BMS v1.3, but I’m unable to provide support for that version. I literally archived my dev build of that version over a year ago.
Download the hub profile AVCS CORE here: veterans-gaming.com/…/avcs-core-profile-framework-for-voiceattack/
Download the latest AVCS4 BMS profile here: veterans-gaming.com/…/avcs4-voice-control-radios-for-falcon-bms/
-
No apologies needed. Please accept my thanks for all the work you’ve done with this sound stuff. I downloaded your latest files and will get back here later to let you know how things turned out.
-
This post is deleted! -
Apologies, I had not realized you weren’t using the latest version of AVCS4 BMS Radios. The version pictured in your screenshots (v1.3) is depreciated, and no longer supported. So many issues were fixed and evolved in the current systems, I’m sure you’ll be fine if/when you upgrade/update (including resolving your error finding the AFM sound file shown in the top most image). The current version of AVCS is even capable of debugging for you, to help you see where and why your PTT button is not being detected by the PTT system, or even generate a semi-automated bug report if you want, for example.
https://i.imgur.com/WgP5ULf.png
The AVCS4 BMS download package is presently on version 1.40 and this also requires the “hub” profile AVCS CORE (v1.0) which handles initialization of the AVCS4 BMS profile (and any others I release). You do not need to remove AVCS4 BMS v1.3, but I’m unable to provide support for that version. I literally archived my dev build of that version over a year ago.
Download the hub profile AVCS CORE here: veterans-gaming.com/…/avcs-core-profile-framework-for-voiceattack/
Download the latest AVCS4 BMS profile here: veterans-gaming.com/…/avcs4-voice-control-radios-for-falcon-bms/
@jc1:
No apologies needed. Please accept my thanks for all the work you’ve done with this sound stuff. I downloaded your latest files and will get back here later to let you know how things turned out.
Success:
@SemlerPDX, I got the latest version of VoiceAttack v1.8.9. I was using v1.8.5. I got your latest software. And now I can fly Falcon BMS 4.35.2 with your voice calls. Thank you so much! -
@SemlerPDX, I got this error. Not sure why it’s not available. How do I get it back?
Edit: I exited twice and the next time it worked???
-
@jc1:
@SemlerPDX, I got this error. Not sure why it’s not available. How do I get it back?
Edit: I exited twice and the next time it worked???
I don’t know what is going on there. Have you renamed my AVCS4 BMS profile or are you using another profile called “Falcon BMS 4.35.2”?
Restarting VoiceAttack is typically the best way to resolve any errors initializing the profiles. Glad you got it sorted. Just remember, never rename the AVCS CORE or AVCS4 BMS Radios profiles or it will break key functions.
-
I use Warthog Throttle. I got DX27 assigned to MSU (Mic switch up) for VHF and DX29 assigned to MSD (Mic switch down) for UHF. Using your 1.40, how do I assign these buttons for Push-to-Talk?
-
@jc1:
I use Warthog Throttle. I got DX27 assigned to MSU (Mic switch up) for VHF and DX29 assigned to MSD (Mic switch down) for UHF. Using your 1.40, how do I assign these buttons for Push-to-Talk?
Just say, “Set a Push to Talk button”, and follow the pop-up prompts to set and save up to 6 total controller/keyboard/mouse buttons as PTT buttons.
There are two modes in my Push to Talk system, the new “Global” mode mutes all microphone input to VoiceAttack unless the PTT button(s) press is detected, and the (default) old version only prevents BMS in-game radio menu macro commands from firing unless PTT button(s) press is detected. I don’t use “Global”, personally, because I also have extra commands to Reset and Pause my head tracking (TrackIR) and I don’t want to have to push my VHF/UHF buttons assigned to PTT in order to issue these voice commands. In this mode, the only time PTT is needed is when a BMS radio command is issued, otherwise every AVCS command will keep working without PTT so you can have an “in game” setup and “out of game” setup of commands outside the PTT mode.
Any issues, let me know! We have already identified an issue with the PTT system, it does not recognize POV buttons, those special kind of 4- or 8-way ‘HAT’ style button are not handled the way the rest of the ‘HAT’ switches work. Requires a workaround, eazy peazy, but folks should know that POV won’t work until I have time to get it coded and release a new major version update.
-
Just say, “Set a Push to Talk button”, and follow the pop-up prompts to set and save up to 6 total controller/keyboard/mouse buttons as PTT buttons.
There are two modes in my Push to Talk system, the new “Global” mode mutes all microphone input to VoiceAttack unless the PTT button(s) press is detected, and the (default) old version only prevents BMS in-game radio menu macro commands from firing unless PTT button(s) press is detected. I don’t use “Global”, personally, because I also have extra commands to Reset and Pause my head tracking (TrackIR) and I don’t want to have to push my VHF/UHF buttons assigned to PTT in order to issue these voice commands. In this mode, the only time PTT is needed is when a BMS radio command is issued, otherwise every AVCS command will keep working without PTT so you can have an “in game” setup and “out of game” setup of commands outside the PTT mode.
Any issues, let me know! We have already identified an issue with the PTT system, it does not recognize POV buttons, those special kind of 4- or 8-way ‘HAT’ style button are not handled the way the rest of the ‘HAT’ switches work. Requires a workaround, eazy peazy, but folks should know that POV won’t work until I have time to get it coded and release a new major version update.
It looks like the issue I got is that the Warthog MIC switch is one of those ‘HAT’ style buttons that requires a workaround. I’ll look forward to your next new major version update.
Associated with this problem is the Voice Attack utility menu. In previous I was able to assign DX27 to one joystick from the utility menu and DX29 to a second joystick from the utility menu in order to specify two buttons, one for UHF and one for VHF. In this VoiceAttack utility menu, (see below), I can only assign to one joystick. When I click on Assign 2, it doesn’t show Thrustmaster Combined.
When I click on Assign 2 I get this:
This option no longer lists Thrustmaster Combined, which is where I would like to assign DX29.
-
@jc1:
It looks like the issue I got is that the Warthog MIC switch is one of those ‘HAT’ style buttons that requires a workaround. I’ll look forward to your next new major version update.
Associated with this problem is the Voice Attack utility menu. In previous I was able to assign DX27 to one joystick from the utility menu and DX29 to a second joystick from the utility menu in order to specify two buttons, one for UHF and one for VHF. In this VoiceAttack utility menu, (see below), I can only assign to one joystick. When I click on Assign 2, it doesn’t show Thrustmaster Combined.
When I click on Assign 2 I get this:
This option no longer lists Thrustmaster Combined, which is where I would like to assign DX29.
The Thrustmaster Throttle is not assigned as a controller in VoiceAttack options (first screenshot) so you need to click on Assign 2 and select ‘Throttle - HOTAS Warhog’ (second screenshot) since this is the device which contains the buttons you want VoiceAttack to listen to. After that, you can run the PTT Setup command again in AVCS and all should work. Also, FTR, there is a valid and easy workaround for those who actually ran into the POV issue, so they don’t need to wait for me to get the next version released. BUT this is not your problem - you just need to assign your device so VoiceAttack can watch its buttons. (DX27 and DX29 by definition can’t be part of a POV because POV does not have DX button numbers for cardinal directions, which is the entire reason my system doesn’t catch them yet)
You have ‘Thrustmaster Combined’ set as Joystick 1 … I’m not a WH owner, but I suspect this is for the ‘stick’ only, or special program recognition for ‘both’ that is not supported by VoiceAttack, and not both stick and throttle as one would assume. You also might want to set Assign 1 directly as the ‘Joystick - HOTAS Warthog’ as well, or not at all, depending on how you are using your WH with VoiceAttack. If it is only for my AVCS PTT system, you don’t even need the stick assigned, just the throttle with the buttons you are using for PTT.
afaik the only ‘POV’ style DirectX button on the Thrustmaster HOTAS is the ‘grey pyramid’ POV HAT on the flight stick, but you can press Windows Start Key and type ‘Set up USB game controllers’ and select your device then ‘Properties’ button to review all button actions. POV style HAT-switch buttons are clearly labeled as such.
-
The Thrustmaster Throttle is not assigned as a controller in VoiceAttack options (first screenshot) so you need to click on Assign 2 and select ‘Throttle - HOTAS Warhog’ (second screenshot) since this is the device which contains the buttons you want VoiceAttack to listen to. After that, you can run the PTT Setup command again in AVCS and all should work. Also, FTR, there is a valid and easy workaround for those who actually ran into the POV issue, so they don’t need to wait for me to get the next version released. BUT this is not your problem - you just need to assign your device so VoiceAttack can watch its buttons. (DX27 and DX29 by definition can’t be part of a POV because POV does not have DX button numbers for cardinal directions, which is the entire reason my system doesn’t catch them yet)
You have ‘Thrustmaster Combined’ set as Joystick 1 … I’m not a WH owner, but I suspect this is for the ‘stick’ only, or special program recognition for ‘both’ that is not supported by VoiceAttack, and not both stick and throttle as one would assume. You also might want to set Assign 1 directly as the ‘Joystick - HOTAS Warthog’ as well, or not at all, depending on how you are using your WH with VoiceAttack. If it is only for my AVCS PTT system, you don’t even need the stick assigned, just the throttle with the buttons you are using for PTT.
afaik the only ‘POV’ style DirectX button on the Thrustmaster HOTAS is the ‘grey pyramid’ POV HAT on the flight stick, but you can press Windows Start Key and type ‘Set up USB game controllers’ and select your device then ‘Properties’ button to review all button actions. POV style HAT-switch buttons are clearly labeled as such.
When you say, “The Thrustmaster Throttle is not assigned as a controller in VoiceAttack options (first screenshot)”, I’m not sure about that. Thrustmaster gives the option to combine joystick and throttle into one device, Thrustmaster Combined, such that 32 DX buttons can be recognized. Windows USB game controllers does recognized Thrustmaster Combined, as this screenshot shows:
DX29 is lit up on the bottom picture because I pressed the Warthog Throttle MIC switch down. This activates UHF in my setup.
DX27 is the button for VHF in my setup. I didn’t take a picture to show that it lights up when I press the Warthog Throttle MIC switch up.Now maybe my expectations can’t be met with your VoiceAttack profile, due to limitations of the VoiceAttack software itself, not you. I was hoping that your profile, with Push-To-Talk enabled, would allow only UHF commands when the UHF button (DX29) is Push-To-Talk and only allow VHF commands when the VHF (DX27) button is Push-To-Talk. Am I expecting too much?
In the meantime I will continue to use your profile while Push-To-Talk is not enabled. What happens is that I can make UHF and VHF calls and your profile gets the correct response. I press MIC switch down or up for UHF or VHF and the DED lights up, but that is, as they say, eye-candy.
Thank you very much for all the work you’ve done to make voice communications in BMS Falcon possible.
-
The Thrustmaster Throttle is not assigned as a controller in VoiceAttack options (first screenshot) so you need to click on Assign 2 and select ‘Throttle - HOTAS Warhog’ (second screenshot) since this is the device which contains the buttons you want VoiceAttack to listen to. After that, you can run the PTT Setup command again in AVCS and all should work. Also, FTR, there is a valid and easy workaround for those who actually ran into the POV issue, so they don’t need to wait for me to get the next version released. BUT this is not your problem - you just need to assign your device so VoiceAttack can watch its buttons. (DX27 and DX29 by definition can’t be part of a POV because POV does not have DX button numbers for cardinal directions, which is the entire reason my system doesn’t catch them yet)
You should at least try this ↑ above, remove the “combined” setting from VoiceAttack Joystick options menu and set the throttle as one of the controllers - then save the setting, and run the AVCS PTT Setup.
I’m fairly confident it will work.
After you have tried that, and IF it doesn’t work, then you can just use the workaround (and the note at the end on how to duplicate the command to set a second button)
https://veterans-gaming.com/forums/topic/10188-avcs-bug-report-push-to-talk-ptt-not-recognizing-joystick/