AVCS4 Immersive Voice Control Radios for VoiceAttack
-
@SemlerPDX No, I just did the run/admin. function via the properties dialog of VA, per VA’s instructions. After I acknowledge the error message I posted, it gives the “Import successful but…” message, stating how the import executed/disabled various sound, plug in, etc. aspects.
I wish I could post some screenshots but I have no way of making them small enough for the forum. -
@MnMailman said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX No, I just did the run/admin. function via the properties dialog of VA, per VA’s instructions. After I acknowledge the error message I posted, it gives the “Import successful but…” message, stating how the import executed/disabled various sound, plug in, etc. aspects.
I wish I could post some screenshots but I have no way of making them small enough for the forum.Please come to my Discord channel for support, it will be easier to go back and forth and share screenshots of your specific issue:
https://discord.gg/xDJUjYQked -
@SemlerPDX On the way, thanks.
-
@SemlerPDX The VG discord says I need to receive a text before I can speak or post there. …I don’t have a cell phone.
I appreciate your efforts,; above and beyond. I’ll keep messing with it and see if it takes. -
@MnMailman said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
@SemlerPDX The VG discord says I need to receive a text before I can speak or post there. …I don’t have a cell phone.
I appreciate your efforts,; above and beyond. I’ll keep messing with it and see if it takes.I don’t know how to help you. You already joined the VG Discord the first week of this month:
I’ve gone ahead and temporarily disabled the security measure we use on our Discord that forces new users to verify their account via phone number (this has nothing to do with us, only the user’s Discord account). This keeps us from having to play ‘whack-a-troll’ all day when some script kiddie gets banned and comes back to raise hell with 10 alternate accounts.
Please feel free to try joining our Discord again, and post up in the “voiceattack-avcs4” channel under “Help & Support”
-
@SemlerPDX Will do.
-
Update: I now have the program working perfectly thanks to the incredible help offered by SemlerPDX. Most people would have blown a complaint such as mine off, but not only did he not do that, he went far out of his way in assisting me.
Great program, great service. -
Dear @SemlerPDX, thank you a thousand times for your quick profile update!!!
Please, let me report a few issues:
-
The new JTAC commands give out QWERTY keys only
(although my profile is set to QWERTZ otherwise).
Tanker commands, though, DO work on my keyboard. -
Some older ones:
“Two, take the lead” produces wrong keys (w0 instead of wwww0) -
The term “Kickout” ONLY works with the prefixes “Wingman”, “Element” and “Flight”, but NOT with the prefixes “Two”, “Three” or “Four”.
(Could also be my pronounciation, though) -
“Flight, go higher” and “Flight, go lower” produce key errors (key down/release by variable not set, no keys pressed).
-
-
@Amadeus75 Thank you for the report, I’ll check in on those things.
For the flight command, try ‘Flight Go High’ and ‘Flight Go Low’ for now, and it will work. That one will require a systems change to implement in the more generic sense, so I had to trim the “er” from the end to make it work along with the non-flight versions of those commands.
Same thing with the JTAC - had not realized it would hard set itself like that.
As a temporary fix for now, it might be a little while to round up other bugs and fix them, here’s a version of the config table which will work for any user with a QWERTZ style keyboard:
https://www.dropbox.com/s/4dzbaia5r3j5ql9/avcs_config_table.zip?dl=1EDIT 2: The link above has (again) been edited and fixed - this file will work!!
Unzip the file to the location below to replace the ‘avcs_config_table.core’ file in that folder:
C:\Program Files (x86)\VoiceAttack\Apps\AVCS\CORE\BMS\40\update
If that is not your path it may be this one, depending on where you installed VoiceAttack:
C:\Program Files\VoiceAttack\Apps\AVCS\CORE\BMS\40\update
-
@SemlerPDX
Thanks a lot, I will try after work -
How exactly does one get the ptt function to work ? I spoke the command listed here to activate it, enabled my joystick in VA, but I still can do commands without ptt.
Trying to use the uhf/vhf buttons. -
@MnMailman said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
How exactly does one get the ptt function to work ? I spoke the command listed here to activate it, enabled my joystick in VA, but I still can do commands without ptt.
Trying to use the uhf/vhf buttons.By default, the PTT system will restrict only BMS Radio Commands, while other configuration commands like “Open the Command Reference” or “Re-initialize Profile” will continue to recognize even if PTT is not pressed.
There is also a ‘Global’ mode for PTT, and this will completely restrict VoiceAttack from recognizing anything said over the mic unless the PTT button has been pressed (or the ‘computer name’ has been spoken, if set).
I’ve thrown together a short demonstration video on the AVCS CORE Push To Talk Mode system that is used in AVCS4 BMS Radios profile. Hopefully, this may clear up any confusion or issues, and help separate misunderstandings (if any) from actual operational errors or bugs. Please check out this video and try to set up your PTT mode as desired, and if it still doesn’t work as demonstrated here, let me know and we can enable the automated debugging I built in and get a log file of what’s actually occurring when you engage these systems.
-
My first QWERTZ fix above was incorrect, I encoded it with HTML tags by mistake, and I’ve edited the file linked above in my dropbox.
To be clear, this is ONLY for users with QWERTZ keyboard layouts, for the new JTAC menu commands. If you have this style keyboard, see the post above on where to put this file:
https://www.dropbox.com/s/4dzbaia5r3j5ql9/avcs_config_table.zip?dl=1 -
@SemlerPDX
Thanks a lot for fixing this for us QWERTZ users
Works fine now! -
Sorry to ask another of my really basic questions, but I’m not sure how to get Voice Attack (with AVCS) to work with BMS 4.36.
It has been working fine with 4.35 U3, but now that I’m using 4.36, I can’t get BMS to respond to VA.
I haven’t changed anything in the PTT settings. So I’m guessing, at least, it’s not a PTT problem. It’s probably something more basic that I’m missing.
I’ll bet there is a way I’m supposed to “point” VA at 4.36, instead of at 4.35, and I’ve forgotten how, and can’t figure out how by noodling around in VA.
-
@Mylonite470 said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
Sorry to ask another of my really basic questions, but I’m not sure how to get Voice Attack (with AVCS) to work with BMS 4.36.
It has been working fine with 4.35 U3, but now that I’m using 4.36, I can’t get BMS to respond to VA.
I haven’t changed anything in the PTT settings. So I’m guessing, at least, it’s not a PTT problem. It’s probably something more basic that I’m missing.
I’ll bet there is a way I’m supposed to “point” VA at 4.36, instead of at 4.35, and I’ve forgotten how, and can’t figure out how by noodling around in VA.
Do have both running as administrator?
I believe you had to have them both run as admin in 4.35 and you may have forgotten to run the new BMS as Admin
-
Thanks, @CriticalMass , I’ll check on that.
Do you happen to know if BMS will be “run as administrator” by default if I launch it from the Alternative Launcher?
I fired up the AL and looked in the Configuration settings, but didn’t see anything about running BMS as Administrator. But this does have a familiar ring to it, as though “run as Administrator” can be set as a default either via the AL or in the BMS config settings…
-
@Mylonite470 said in AVCS4 Immersive Voice Control Radios for VoiceAttack:
Sorry to ask another of my really basic questions, but I’m not sure how to get Voice Attack (with AVCS) to work with BMS 4.36.
It has been working fine with 4.35 U3, but now that I’m using 4.36, I can’t get BMS to respond to VA.
I haven’t changed anything in the PTT settings. So I’m guessing, at least, it’s not a PTT problem. It’s probably something more basic that I’m missing.
I’ll bet there is a way I’m supposed to “point” VA at 4.36, instead of at 4.35, and I’ve forgotten how, and can’t figure out how by noodling around in VA.
If you have changed the target in the settings window below, then you many need to change it for BMS 4.36, any keyword in that process name has changed. I disabled the forced BMS targeting long ago, and recommend to users to keep this set to ‘Active Window’, but if you have had to change it for yourself, review this screen under Profile Options and ensure it’s either the correct name for the process or is set to ‘Active Window’
If keypresses will not get through to your game, you might try addressing the .exe by name - Surround the name with *asterisks for a wildcard name capture as Focus Target globally. You can also try simply “Falcon BMS.exe”, or “*Falcon BMS.exe”. The default action is set to Active Window which should work for most people, but if that does not work, you might need to check a few things.
/Ensure VoiceAttack is running as Administrator, and that no plugins are interfering with keypress commands. As a last test for keys not working, you can try increasing the TimeBetweenKeys and TimeKeyIsHeldDown variables via the “Open Keypress Timings Menu” command to adjust these timings globally for the entire profile. Test increase from default 0.05 to 0.10 to slow down keypress commands./
-
Well, I knew I was missing something basic, and I figured out what it was.
It was an “800-lb gorilla in the room”… I got a new throttle and set it up yesterday, before trying to use VA and AVCS in 4.36. I didn’t think I had created a PTT issue for myself, but I had.
I needed to enable the new throttle in VA Joystick options. Once I did that, all was well. AVCS PTT works in 4.36 just like it did in 4.35 U3.
As it happens, I got the new throttle right as 4.36 was coming out. I thought about setting up the throttle in 4.35 first, but decided not to. If I had done that, I would have had discovered the lack of VA functionality, and would have found my PTT mistake before installing and setting up 4.36.
I had (foolishly) thought that setting up the mic buttons in the KEYMAPPING part of the Alternative Launcher would make Voice Attack recognize the UHF and VHF switch actuations on the new throttle, as though it was the old throttle. I was mixing apples and oranges. I needed to go into VA’s joystick options and enable the new throttle.
Bonehead mistake, but I’m glad I spotted it. As always, many thanks to everyone for their suggestions, especially SemlerPDX. You really do a yeoman’s job putting up with folks like me, and I’m very grateful for it!
-
@SemlerPDX Sorry for the really noob question but this is only my 2nd profile for Voice Attack and I’m really confused how to install it. Is there an idiot’s guide somewhere please?? Thanks!