AVCS4 Immersive Voice Control Radios for VoiceAttack
-
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/ -
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/I set Warthog Throttle and also tried your workaround. Neither method worked Must be Thrustmaster Target software interfering.
I got to keep Thrustmaster Combined because that is the device recognized by BMS setup and Thrustmaster Combined Target software controls Warthog Joystick and Throttle.
I’ll continue to use your AVCS4 without push-to-talk. I can issue voice commands and get responses with your AVCS4.
Thrustmaster Combined Target software lights up UHF and VHF on the DED, but it doesn’t matter if push-to-talk is enabled or disabled with your AVCS4. -
@jc1:
I got to keep Thrustmaster Combined because that is the device recognized by BMS setup and Thrustmaster Combined Target software controls Warthog Joystick and Throttle.
I think we have a misunderstanding… You do NOT need to keep Thrustmaster Combined assigned in VoiceAttack Joystick Options Menu, which is what I was describing. BMS won’t mind, no other programs will mind what you have set in the VoiceAttack options, these are for the VoiceAttack program only. I was asking you to try removing the ‘Combined’ joystick from VoiceAttack Joystick Options menu and replace it with the Throttle - TM Warhog instead. Then try to see if the buttons are recognized in the VoiceAttack program.
If you’re all out of motivation to work towards fixing your issue, that’s just fine. But if you have a persistent attitude to not give up and get this to work like many others have, I’m definitely willing to work through it with you. I have a feeling there is something small that is being overlooked or that a simple setting or configuration edit will present itself as the solution. Another place to get help with VoiceAttack (in general) regarding things like the program not recognizing your joystick of some brand is the actual VA Discord - they help a metric ton of users for free everyday, and I bet there is something that Pfeil (or others) know about that I don’t. https://voiceattack.com/discord
@jc1:
Must be Thrustmaster Target software interfering.
I’m starting to think this may be the case. Hopefully, there is a way to use Target and VoiceAttack as well to recognize button presses. I’m gonna ask Kavelenko for advice, he also uses the TM WH for BMS, and AVCS4 BMS. Gotta be something simple. Still, it could be something else and is worth fighting for, if you are willing. PC’s sometimes require serious determination to get them to work as we want them to.
-
I think we have a misunderstanding… You do NOT need to keep Thrustmaster Combined assigned in VoiceAttack Joystick Options Menu, which is what I was describing. BMS won’t mind, no other programs will mind what you have set in the VoiceAttack options, these are for the VoiceAttack program only. I was asking you to try removing the ‘Combined’ joystick from VoiceAttack Joystick Options menu and replace it with the Throttle - TM Warhog instead. Then try to see if the buttons are recognized in the VoiceAttack program.
If you’re all out of motivation to work towards fixing your issue, that’s just fine. But if you have a persistent attitude to not give up and get this to work like many others have, I’m definitely willing to work through it with you. I have a feeling there is something small that is being overlooked or that a simple setting or configuration edit will present itself as the solution. Another place to get help with VoiceAttack (in general) regarding things like the program not recognizing your joystick of some brand is the actual VA Discord - they help a metric ton of users for free everyday, and I bet there is something that Pfeil (or others) know about that I don’t. https://voiceattack.com/discord
I’m starting to think this may be the case. Hopefully, there is a way to use Target and VoiceAttack as well to recognize button presses. I’m gonna ask Kavelenko for advice, he also uses the TM WH for BMS, and AVCS4 BMS. Gotta be something simple. Still, it could be something else and is worth fighting for, if you are willing. PC’s sometimes require serious determination to get them to work as we want them to.
I want to get this working and thanks for your offer to help out. I took your advice and assigned Warthog throttle as joystick #1. The 8 pictures below show how I did it. But in game I got no response from the call to “Request vector to tanker”. In picture #8 the first call was made without pressing the MIC switch on the throttle; call was recognized but no response. The second call was made after pressing the MIC switch down twice; again, call was recognized but no response.
Edit:
I disabled Push-toTalk and made Thrustmaster Combined the joystick #1. The button it recognized was 29. And I got the result shown in the picture below. The first “Request vector to tanker” gave me a response. When I press MIC down, listening is suspended and the headphone icon at the right turns red. If I say “Request vector to tanker” I get no response (seems correct). When I press MIC down again, listening is resumed and the headphone icon turns black. And when I say “Request vector to tanker” I get a response (seems correct). So when Push-to-Talk is disabled and Thrustmaster Combined is the joystick, I get the responses to “Request vector to tanker” as long as the MIC is listening. Then my question is: Why have Push-to-Talk enabled when Picture #8 shows it gives no response with Warthog throttle as joystick #1? -
@jc1:
I want to get this working and thanks for your offer to help out. I took your advice and assigned Warthog throttle as joystick #1. The 8 pictures below show how I did it. But in game I got no response from the call to “Request vector to tanker”. In picture #8 the first call was made without pressing the MIC switch on the throttle; call was recognized but no response. The second call was made after pressing the MIC switch down twice; again, call was recognized but no response.
Edit:
I disabled Push-toTalk and made Thrustmaster Combined the joystick #1. The button it recognized was 29. And I got the result shown in the picture below. The first “Request vector to tanker” gave me a response. When I press MIC down, listening is suspended and the headphone icon at the right turns red. If I say “Request vector to tanker” I get no response (seems correct). When I press MIC down again, listening is resumed and the headphone icon turns black. And when I say “Request vector to tanker” I get a response (seems correct). So when Push-to-Talk is disabled and Thrustmaster Combined is the joystick, I get the responses to “Request vector to tanker” as long as the MIC is listening. Then my question is: Why have Push-to-Talk enabled when Picture #8 shows it gives no response with Warthog throttle as joystick #1?I don’t know why you are enabling hotkey on that joystick in picture 5 … you need to ask AVCS to “Set a Push to Talk Button” and then push the button you want set. You have somehow ended up on a screen not part of AVCS PTT setup… It’s supposed to be very simple: bind your joystick/controller in VoiceAttack Options menu, verify buttons work (picture 3), then ask AVCS to Enable the Push to Talk mode – it should walk you through setting PTT buttons, and if not, the command “Edit Push to Talk Mode” will let you change any settings. You’d press the controller button you have assigned to your VHF button, and then set another Push to Talk button for UHF in the same way - this is all done through get-choice or get-input pop-up boxes by AVCS.
Remove your joystick as a Global Listening Joystick Button in VoiceAttack options – this is entirely handled for you automatically by AVCS.
The fact that you have got VoiceAttack to now recognized the throttle buttons is a good step forward.
-
I don’t know why you are enabling hotkey on that joystick in picture 5 … you need to ask AVCS to “Set a Push to Talk Button” and then push the button you want set. You have somehow ended up on a screen not part of AVCS PTT setup… It’s supposed to be very simple: bind your joystick/controller in VoiceAttack Options menu, verify buttons work (picture 3), then ask AVCS to Enable the Push to Talk mode – it should walk you through setting PTT buttons, and if not, the command “Edit Push to Talk Mode” will let you change any settings. You’d press the controller button you have assigned to your VHF button, and then set another Push to Talk button for UHF in the same way - this is all done through get-choice or get-input pop-up boxes by AVCS.
Remove your joystick as a Global Listening Joystick Button in VoiceAttack options – this is entirely handled for you automatically by AVCS.
The fact that you have got VoiceAttack to now recognized the throttle buttons is a good step forward.
I took your advice and again did pictures #1 to #4 for Warthog Throttle. Then I said “enable push to talk mode”. Then said “edit push to talk mode”. I got the dropbox shown in the attached picture VC-10.png. The “32” is there from a previous attempt when I chose the spacebar. Now, it doesn’t do anything when I push the Warthog MIC switch down in an attempt to change “32” to MIC switch down (button 5 on Warthog Throttle or button 29 on Thrustmaster Combined).
Then I started the game in Push to Talk mode. In the picture below, VC-11.png, the first “Request vector to tanker” was recognized but I got no response. VC-11.png shows I disabled push-to-talk. Then “Request vector to tanker” was again recognized, and I got a response.
I’m not sure what your Voice Attack profile is doing.Tried once more to “edit push to talk mode”. See below for VC-12.png. This time I got a message that said “PLEASE PRESS ANY KEY OR BUTTON NOW”, which I didn’t get before. Now “Request vector to tanker” is always recognized but I get a response only when MIC switch is pressed down for UHF. I think this is the Push-to-Talk I’ve been looking for. THIS IS GREAT! Now what do I have to do to get MIC switch UP for VHF, Warthog Throttle button 3, to behave the same as MIC switch down for UHF?
This is the final edit to this post. I answered my own question about setting MIC switch UP for VHF. I tried to “edit push to talk mode”. It gave me “32” in the second dropbox list, not what I wanted. Then I tried “Set a push to talk button”. I pushed Warthog MIC switch up for VHF and got “PTT Button Set to STATE_MIDDLEMOUSEBUTTON”. My Thrustmaster Target profile has MOUSE_CENTER assigned to Warthog button 3, Thrustmaster Combined button 27. Your AVCS4 button STATE_MIDDLEMOUSEBUTTON worked in the game in Push to Talk mode for VHF. THIS IS GREAT! My push-to-talk works in game for UHF and VHF.
Don’t know why I had to keep trying “edit push to talk mode” and “Set a push to talk button”, but it doesn’t matter anymore.
-
@SemlerPDX, Thanks for all the help you gave me. Now that I got Push to Talk working, can you tell me where the changes are made. I’d like to save copies of the files in case I have to reinstall them. Do I have to save a copy of Core 1.0 and Profile 1.40?
-
@jc1:
This is the final edit to this post. I answered my own question about setting MIC switch UP for VHF. I tried to “edit push to talk mode”. It gave me “32” in the second dropbox list, not what I wanted. Then I tried “Set a push to talk button”. I pushed Warthog MIC switch up for VHF and got “PTT Button Set to STATE_MIDDLEMOUSEBUTTON”. My Thrustmaster Target profile has MOUSE_CENTER assigned to Warthog button 3, Thrustmaster Combined button 27. Your AVCS4 button STATE_MIDDLEMOUSEBUTTON worked in the game in Push to Talk mode for VHF. THIS IS GREAT! My push-to-talk works in game for UHF and VHF.
Don’t know why I had to keep trying “edit push to talk mode” and “Set a push to talk button”, but it doesn’t matter anymore.
Oh yeah, that sort of behavior is definitely related to your use of TARGET software. Luckily, AVCS only cares what it “sees” and if you’ve tricked Windows to thinking that DX27/3 button is actually a Middle-Mouse button, AVCS PTT will pick that up just the same.
So glad you got it sorted! You’re definitely using the most custom setup of anyone who has had PTT issues yet, so if it makes you feel better, this may help someone else with a less-than-standard setup as well.
Setting a new PTT Button (or changing an existing button) should always be as easy as saying, “Set a Push to Talk Button”, where the system knows if there are already buttons set, and the user can choose a slot (number) from the drop-down box to add/set/change PTT assignments. Current limitations include improper display of key/button indicator to the right of the assignment (sometimes just an ASCII symbol) and the lack of a ‘delete’ feature (has to be manually deleted from save file if required), but these will come with the next version as well as a fix for POV style HAT switches. I’m still trying to enjoy the summer off, tomatoes finally coming in, BLT’s baby! Just living the life
@jc1:
@SemlerPDX, Thanks for all the help you gave me. Now that I got Push to Talk working, can you tell me where the changes are made. I’d like to save copies of the files in case I have to reinstall them. Do I have to save a copy of Core 1.0 and Profile 1.40?
All changes are located in the AVCS Save File for the current profile (BMS in this case). You can say, “Open the Save File”, or “Open the Save File Folder”, to view contents. If you open the save file in this way, AVCS will wait for it to close and detect any changes, and reload the AVCS profile (if any) to reflect changes immediately in the active profile.
To save a backup copy of your save file so you don’t lose your settings, say, “Open the Save File Menu” – see pic below – scroll all the way down to the last option, “Create a Shadow Copy of the current AVCS4 BMS Save File” and follow the prompts to choose a destination location for this file. If you ever need to restore settings from a save file, the option #7 just above ‘shadow copy’ allows the import of settings from a save file, guiding the user through the process with pop-up boxes as usual.
I’m sure you’re happy to be done doing the troubleshooting dance!! Cheers! Have fun and see you at Angels 20!
-
…
I’m sure you’re happy to be done doing the troubleshooting dance!! Cheers! Have fun and see you at Angels 20!+1
-
-
-
-
AVCS CORE v1.11 Major Profile Update
Please download and import this updated final version! Link below and updated in the main post above! AVCS CORE v1.11 will also import a new ‘AVCS4 USER PROFILE TEMPLATE (v1.0)’ - this template has not been changed from before. If you had AVCS CORE v1.0 and that template profile already, you can delete this duplicate 'AVCS4 USER PROFILE TEMPLATE (v1.0)Follow instructions during update to import previous version Save Files and to uninstall and delete the previous AVCS CORE v1.0 profile and config files
I had hoped that AVCS CORE v1.0 would be the final version, but I had not anticipated issues with Joystick POV directional buttons in the Push-To-Talk system, and I had not included a handy way to delete saved PTT buttons or keys. With this update, I’m happy to announce that AVCS CORE is now feature stable and (as far as I know) 100% bug free! I keep throwing every curveball and edge case I can think up at it, even including the update or new version profile import process, and everything just works. I don’t have anything more to add, and there is nothing left to take away.
As the ‘hub’ profile for my AVCS4 BMS Radios profile, and others I plan to release in time, it has always been my goal to have AVCS CORE as an unchanging stable framework that I can use as a platform to support end-game profiles indefinitely. Eventually, I plan to return to AVCS CORE to create a separate version packed with well designed and themed user interfaces for all options and menus which presently use simple VoiceAttack ‘Get user input’ actions, and while still supporting the original v1 simple ‘get user input’ interface version(s) which will remain free for all users. The artwork and GUI coding will take some time, and I have many other projects on my plate, so I don’t expect to be working on AVCS CORE again until late 2022 or even later.
I use AVCS CORE every day myself, with the included AVCS Template profile as my ‘main’ Windows voice control system, and am very glad to have this project version wrapped up for now.
Thank you all again for all the support and for the coffees! Cheers!
Download: (Click Here)
Public Release AVCS CORE v1.11 Changelog Oct-1-2021 Fixes/Improvements: -Updated minimum required version of VoiceAttack to 1.8.9 -Created new system in Push-To-Talk Mode for Joystick POV (4-way directionals only) -Created Delete system in PTT Mode to allow removal of any PTT entry already set -Fixed PTT Buttons Display List not retrieving correct keyboard key from keycode # (showing 'square' symbol instead) -Fixed CORE Config #2 (TTS file) error near 'AlreadyOn' phrase, CRLF (NewLine) missing, merging the variables into one
-
Has anyone posted a video demonstrating this working. Would really like to see it in action.
-
-
Disregard…I pushed through the brick wall this is space between my ears. Thanks to some help from some knowledgeable folks.
-
I have downloaded AVCS Core 1.11, and I would like to install it, but I have always had some trepidation when it comes to installing updated AVCS components for VoiceAttack. I’m always afraid of losing the custom commands I’ve made.
I wish I could recall the particulars, but I can recall updating some part of AVCS and/or VoiceAttack, and my custom voice commands (like “[my callsign] requesting the overhead”) went away and I had to create them again.
Have I perhaps missed the installation instructions on the veterans-gaming.com website? I wouldn’t be surprised if I have.
I am currently using AVCS Core 1.0 and AVCS4 Falcon BMS Radios 1.40, and when I start VoiceAttack, the following things automatically happen:
-
It starts AVCS Core 1.0
-
It tells me there has been an update to AVCS Core 1.0 (which I decline to deal with for the moment)
-
It automatically “switches over” (for lack of a better term, maybe “loads” is better) to AVCS4 Falcon BMS Radios 1.40.
Voice Attack then looks like this, and works fine:
I’m curious to know what I should do in order to:
-
Update AVCS Core 1.0 to 1.11
-
Maintain the “automatic switchover/load” to AVCS4 Falcon BMS Radios 1.40
-
Keep my custom commands intact (I think they’re part of AVCS4 Falcon BMS Radios 1.40.)
Sorry to be so dense about this, I’ve just always found these various components of the Voice Attack system to be kind of confusing, especially when it comes to installing and updating them. I apologize if I have missed a how-to guide for these installations and updates.
-
-
The update procedure for AVCS CORE v1.0 to v1.11 is pretty painless, I promise! Trust me when I say, all you need to do is import the latest version and follow the prompts and instructions noted in VoiceAttack Event Log. The following instructions can give you an idea of what to expect, but are not needed - it should be an intuitive process.
Any custom commands you have created in the AVCS4 BMS Radios Profile will remain unchanged and fully operational. Profile settings and saved options in AVCS CORE v1.0 can be imported into v1.11 by following prompts during first time initialization, but you will need to set the Preferred Profile again so AVCS CORE v1.11 will auto-switch to AVCS4 BMS as it did before - again, just follow the prompts.
The Push to Talk system has been overhauled - if you used it before, after you get back to AVCS4 BMS v1.40 through AVCS CORE v1.11 initialization, just say, “Set a Push to Talk Button” and follow the prompts (no manual command editing is required anymore).
Once AVCS CORE v1.11 has finished importing, switch to it and wait until after first time initialization is complete - you can then select AVCS4 BMS as the Preferred Profile (or say “Set a Preferred Profile” and select AVCS4 BMS).
During the import and first time initialization of AVCS CORE v1.11, former users of v1.0 will be presented with options to import previous version save file, and/or delete previous version save files and profile config files so you can delete AVCS CORE v1.0 - just follow the instructions and prompts. You do not need to delete AVCS CORE v1.0, but it is recommended.
(any AVCS profile can be uninstalled anytime in this manner (including config files) through AVCS CORE menu options - just say, “Open the Advanced Options Menu”, and select it from the list)A restart of VoiceAttack may be required if you delete the previous AVCS CORE config and profile version(s). Just switch to AVCS CORE v1.11 after restart, reset the Preferred Profile to AVCS4 BMS (again) if not already saved.
Then just switch to AVCS4 BMS.
Since AVCS CORE must be included in AVCS4 BMS through profile options, all you need to do is follow instructions to repeat this procedure for this new version.
(removing AVCS CORE v1.0 from the list, replacing it with AVCS CORE v1.11 per images below)Switch to AVCS4 BMS and open the Editor (see img above), then select Options near the top left, navigate to the following screen(s) as instructed above:
*again, be sure to remove AVCS CORE v1.0 from Included Profiles list, only include AVCS CORE v1.11 -
Thank you very much, @semlerpdx , that worked great!
I followed those instructions, and sure enough, there was no loss of the custom commands.
After AVCS Core 1.11 was imported and initialized, I restarted VoiceAttack, and it automatically loaded AVCS4 BMS 1.40 just as before.
I said:
“Kunsan approach, Goblin Two-One, single-ship F-16, inbound for runway Three-Six. Requesting the overhead”And Kunsan approach came back with:
“Good morning Goblin Two-One, Kunsan approach, you are cleared all the way in for overhead approach, runway Three-Six. Welcome back.”… just like they’re supposed to. Life is good!
-
-
<p>Hi @SemlerPDX,<br /><br />Don’t want to go over old ground but I fear I’m about to. I read through this thread trying to catch if I’ve missed something, especially your discussion with jc1. <br /><br /><br />Excuse me if I’m wrong and/or have imagined this experience, voice would only get transmitted on the correct frequency IF the correct PTT button (UHF/VHF) was pushed. It seems now it doesn’t care I can push either and the voice profile will run and be recognized in-game. I’m sure that when you had to set the up/down press/release HOTAS keys in the config, this worked as expected. <br /><br />Are my expectations now wrong or is there something I’m missing? <br /><br />I’ve set PTT buttons to global as my breathing was getting picked up as “queue f e” (I got bored of hearing local pressure ) - the issue above was before and after making the change to global.<br /><br />TANX<br /><br />Critical</p>
-
<blockquote>Hi @SemlerPDX,<br /><br />Don’t want to go over old ground but I fear I’m about to. I read through this thread trying to catch if I’ve missed something, especially your discussion with jc1. <br /><br /><br />Excuse me if I’m wrong and/or have imagined this experience, voice would only get transmitted on the correct frequency IF the correct PTT button (UHF/VHF) was pushed. It seems now it doesn’t care I can push either and the voice profile will run and be recognized in-game. I’m sure that when you had to set the up/down press/release HOTAS keys in the config, this worked as expected. <br /><br />Are my expectations now wrong or is there something I’m missing? <br /><br />I’ve set PTT buttons to global as my breathing was getting picked up as “queue f e” (I got bored of hearing local pressure ) - the issue above was before and after making the change to global.<br /><br />TANX<br /><br />Critical</blockquote><p><br /><br />VoiceAttack does not know which channel is which, and it is irrelevant to AVCS4 BMS. The PTT feature is only a on/off thing, and the allowance for two PTT buttons on the same assignment as UHF and VHF PTT buttons in the sim is only for immersion and functionality. You can actually set up to 6 different push to talk buttons with my system, and their only function is to allow recognition when pressed and deny it when not pressed, with no further logic.</p>
-
<blockquote>VoiceAttack does not know which channel is which, and it is irrelevant to AVCS4 BMS. The PTT feature is only a on/off thing, and the allowance for two PTT buttons on the same assignment as UHF and VHF PTT buttons in the sim is only for immersion and functionality. You can actually set up to 6 different push to talk buttons with my system, and their only function is to allow recognition when pressed and deny it when not pressed, with no further logic.</blockquote><p><br />Righty oh! I thought that was the case, but was I imagining it with previous releases? Thanks regardless, love your work!<br /><br />Also, I’ve mapped a third button that only turns on (global) listening mode and for not flight stuff like “toggle pilot”, “toggle NVG” etc. Not sure what this achieves as I think UHF/VHF buttons will do the same, but I don’t get the audio feedback/squelch. I’m happy :)<br /><br /><br /></p>
-
-
Re: AVCS4 Immersive Voice Control Radios for VoiceAttack
Profile has been patched for the new BMS 4.36 version and the updated Radio Menus lists. New page added for JTAC, plus many more - see updated Command Reference for complete changes and new radio menus graphic
Public Release AVCS4 BMS v1.40.4 Changelog April-24-2022 This is a simple Live Update patch fix, no new profile download is required - the following fix applies to this update: New Commands: -Added new JTAC Menu under "Y" command lists, say "Open the Command Reference" for updated lists -Many new radio commands listed in CommRef, report any bugs or issues please! Fixes/Improvements: -Updated order and position of lists, all new commands supported -Some previous phrasings retained for additional recognition options -Removed duplicate phrases in data 1 config
Updated Command Reference Pic for BMS 4.36: