I was going to suggest that you submit this issue as a bug on their github tracker, but see that you already did 
. I guess one man’s bug is another’s feature request 
1 Like
VACOM PRO Community version has stopped working for me. Anyone else?
I get the mic click (press/release); VAICOM shows it’s recognized but DCS won’t respond. And it wont respond to “Options” (bring up the menu) or any of the “Other” commands in there. Actually, it wont respond to anything , even the stock commands.
Tried the custom install folder (even tried a temp one) and registry fix. Nothing. Thanks
Last time I had this issue, it was a launch order issue. Especially after DCS updates make sure to close DCS completely. Then restart Voice attack. It should install any missing integration scripts automatically. Only then start DCS again.
2 Likes
Works for me, at least in the Hornet. I reinstalled the latest version last night and did a quick test. FYI, the VIACOM release notes mention a bug in the DCS Launcher that enables easy coms on startup. And that’s what my system does. The work around is to not use the Launcher or remember to disable that option before flying a mission.
+1 what miRage said. In general you want to launch VA or the VAICOM launcher before DCS. The exception is if VA gets wonky while in a mission. You can Pause the sim, Alt-Tab to VA, close it, and the VAICOM launcher will restart it. But you most likely knew that.
Thanks all.
Starting VAICOM (among others) first has been SOP for me from the beginning. Just checked and Easy Comms WAS checked - I WISH they’d stop doing this; in all the years I’ve played DCS I have never used easy comm’s, so I didn’t think to look at that.
However, unchecked and still no joy. Gotta be something (some ‘switch’ or setting) I’ve missed. Worked a few weeks ago just fine (been that long since I’ve played on this install).
Grrr.
Want me to test a specific module to attempt to recreate the issue? You could also post on their Discord. Let me know if you want a copies of my Export.lua and VAICOMPRO.export.lua.
Still diggin…the export.lua looks fine - I’ve removed everything but VAICOM.
What I notice missing is the ‘confirmation’ beep I used to get, as in:
[press button to transmit and hold] “say command” [BEEP] [release button]
That [BEEP] isn’t there (I have the UI Sounds and Use Audio Cues both checked, which is normal for me cos over the years this has all been a bit finicky and I like the feedback).
The window shows the expected stuff:
Joystick: Transmit TX1 press
Listening resumed
Recognized: ‘options’ (confidence 95)
Joystick: Transmit TX1 released
Listening suspended
That all looks correct but no response from DCS.
Still digging. I’ll wander over to the Discord server in a while.
1 Like
For The Future:
Somehow it’s working again. No clue, exactly, what the issue was.
It seems the keywords got deleted; makes sense. I missed that these were
missing - the feedback window telling me it was hearing something threw me off and I could see the AI Commands were there and I was confusing the two.
I’m afraid to touch anything now 
EDIT
Gone back trying to find out what was wrong and why but all I know is:
The above had an extra category “AI Commands” that looked just like the Keywords box, containing the same data. It’s not there now.
All my PTT | Shortcut entries has “disabled shortcut” or (shortcut disabled). The word ‘disabled’ was problematic - I want something ENabled. Just not sure what yet. Manual not that much help here. Stumbled across an option to “Clear all disabled XXXX shortcuts” (there were a few, one each for mouse, keyboard, etc). After doing this…it made things worse 
Then I selected another profile from the main window dropdown and, viola! All works now. That AI Command category is gone too.
For DIAGNOSIS Purposes
This is what a correct response should look like in the feedback window (with Debug mode checked in VAICOM PRO applet), working bottom-to-top:
The bits in red were missing before
2 Likes
That must have been pretty good Bourbon for you to delete your keywords 
1 Like
I’m re-reading the LONG manual again in hopes I can update the above to something more useful than “I think I fixed it”
Doh! That reminds
See above edit. Thanks for the input BTW
1 Like
Major release of VAICOM Pro (free) to version 3.x.
YOU MUST DO A KEYWORD RESET AND RESTART VOICE ATTACK, DO FINISH IN THE EDITOR AND PASTE THE NEW KEYWORD SET TO THE PROFILE AS DESCRIBED IN THE MANUAL. More info on Discord and in the manual.
Join the great VAICOM Pro Community Discord for support, releases, and module specific information on VAICOM.
From Pene on Discord:
"Installation Instructions NOTE: If this is a new VAICOMPRO installation, you should follow the install instructions in the VAICOMPRO manual found in the VAICOMPRO/Documentation folder. or you can download from vaicompro-manual
To update from an older version of VAICOMPRO
-
Download the MSI installer.}
-
Uninstall Vaicom Pro via the Add or Remove programs or Apps Windows function if it is already installed.
-
Do not delete any folders. Not required!
-
Run the MSI installer and follow the instructions.
-
Future updates are managed automatically via an auto updater function.
As always, please update your VoiceAttack Profile and your VAICOMPRO keyword commands using the Editor tab in the VAICOMPRO configuration window. Instructions on how to do this can be found in the manual."
5 Likes
FYI, there is a new version of both VoiceAttack and VAICOM. VoiceAttack has been now updated to v2.x, but it’s not free. However, if you use it, the $10 seems very reasonable. VAICOM will continue to run on VA v1 for the time being. However, any improvements to VAICOM will be geared toward the new version of VA.
If you do choose to upgrade, there is a batch file in the new installation to migrate your old VA data. The new version of VA installs in \Program Files\ where the old one installed in \Program Files (x86). Also, the new version needs the .net 8.x desktop runtime.
Begin reading here about VAICOM regarding the integration with VoiceAttack v2 and continue below that post for info related to the community’s latest release.
3 Likes
I’ll wait a little as I don’t see any killer features. I might upgrade just to support the developers.
To be honest my enthusiasm is a little muted since Vaicom’s AI RIO for the Tomcat breaks Integrity Check and cannot be used online on most servers. Also there is no comparable support for the F-4 WSO. Maybe Heatblur opening up the jester API will allow better integration.
1 Like
Another in Pene’s (AnyTimeBaby) tutorial series for VAICOM. Very much worth a view if you use VAICOM.
2 Likes
Part of my…erm…Flight-sim Immersion Trifecta (FIT ) program…sorry, just popped into my pea brained head. So:
- VR (presence?)
- Haptic Feedback (feel)
- Comms (more realistic; has other benefits)
Looking into getting my hands in the game some day.
On that note: anyone tried this, with VR?
1 Like