hornblower793

All, For those who are not yet aware, @Hollywood_315 has placed the Vaicom source on github this morning and is therefore no longer supporting it. We are in the process of pulling together an ongoing development and community management team and will update as further details become available. Massive thanks to @Hollywood_315 for having produced such a great tool and supported it for so long. Sent from my SM-T835 using Tapatalk

Unfortunately no I haven't, and have had no time to fly myself either recently. Hopefully that will change soon though

It doesn't exist as a command - I had that for a while and it disappeared with an update. I just ignored it

There are 4 of them at the moment - I am sure others will follow

Which modules? Have you confirmed the settings sliders are correct for your DCS install (standalone / steam and stable / openbeta)? If these are right please could you turn on Vaicom debug, restart Vaicom and then post the resulting log here (found in the logs folder of your Vaicom install). Happy New Year [emoji5] Sent from my SM-T835 using Tapatalk

Yes - turn off auto browse in Vaicom config Sent from my SM-T835 using Tapatalk

Does it show the commands you are speaking and then say whether they are recognised or not? Sent from my SM-T835 using Tapatalk

What does the VA / Vaicom log show? Sent from my SM-T835 using Tapatalk

Also, do you have auto browse turned on or off in the Vaicom settings? Sent from my SM-T835 using Tapatalk

What settings do you have in Vaicom config? Does this happen for all aircraft, and does something similar happen if DCS isn't loaded. It might be worth turning Vaicom debug on, restart VA and then post the Vaicom log here - this will let us see if there are any config messages that might give a clue Sent from my SM-T835 using Tapatalk

You are right -@MAXsenna is good and these forums do work very well Sent from my SM-T835 using Tapatalk

You can daisy-chain profiles so you can have your profiles running at the same time. It sounds like you have opened Vaicom using the executable. This is designed to auto restart VA / Vaicom if it crashes during use. To close this you need to right click on it and close it. If you don't want this, open VA directly. It is not crazy integration - it is done so that Vaicom can get information from DCS about what is happening / available recipients etc.. It does take some getting used to, but I am another British English user (southern UK) who can confirm that it works very well. Sent from my SM-T835 using Tapatalk

If this is with VCP also running have you tried the REL HOT option in VCP? Sent from my SM-T835 using Tapatalk

I don't think so, as the wheel is just a visual way to get the Vaicom options so Hollywood will need to change both Sent from my SM-T835 using Tapatalk

You either need to keep the pause or add the phrase you want to use as an alias Sent from my SM-T835 using Tapatalk

Or just double-click any single row in the column saying AI Communications Sent from my SM-T835 using Tapatalk

It normally means something has got slightly corrupted. If shutting everything down and restarting doesn't work try: 1. Close DCS and VA, copy Export.lua in your saved games > scripts folder and then delete export.lua. Restart to see if it works. Copy back any other lines in your saved export.lua (put them back in the same order). If still not fixed then 2. Use the set custom path option in Vaicom config. Point this to your main DCS folder, tick fix reg, set the sliders the right way and then restart VA - go back into config and uncheck set custom path. If neither work, post your Vaicom log file here (with Vaicom debug turned on) and we will have a look. Sent from my SM-T835 using Tapatalk

If you have installed the 64-bit version of VoiceAttack (VA) and have used the Vaicom installer you will need to add an additional step. 64-bit is a recent development for VA and the Vaicom installer still assumes VA is installed in the Program Files (x86) folder as a 32-bit program. You will therefore need to copy the files from Voiceattack\apps\vaicompro in the x86 folder to Program Files\Voiceattack\apps\vaicompro Sent from my SM-T835 using Tapatalk

If it is not showing the module that normally means it is looking in the wrong place for DCS. Please could start VoiceAttack, open Vaicom config, turn on Debug on the Config tab, restart VA and then post the Vaicom logfile here (this will be found in the <voiceattack install dir>\apps\VAICOMPRO\logs folder. Please could you also post a screenshot of the Vaicom Config and MP tabs Like Max I am just a user, but between us and others on the forum we can normally sort issues

The information above is not quite correct - you do not need the 'Auto browse' feature for it to work. Auto browse allows you to switch tabs without just by saying the name of the tab, but also means that if you are elsewhere in the Kneeboard (e.g. on an airfield layout) it will switch back to the Vaicom tabs whenever a message comes in. Without auto browse on you have to say <tab>.....page (e.g. Texaco....page, air traffic....page) to bring the relevant tab up. You can use callsigns for the relevant tab - REF works with Chief as a page name (REF = Refueling)

Dave, It sounds like the configuration isn't right and the other issues are following on from that. Just checking that you have set up Voiceattack and Vaicom following the instructions in the Vaicom manual, and that you have correctly pointed Vaicom to your DCS install (standalone / steam and OB / stable) in the Vaicom config. Please could you post a screenshot of the (voice disabled) message. Are you on Discord? If so, I am happy to jump on a voice call at the weekend to work through this.

Is it CTD or does VA just close leaving you in DCS with no voice commands? If the second one then try using the Vaicom app to start VA - if VA then closes during flight this will automatically restart it Sent from my SM-T835 using Tapatalk

Yes to slider - it means that they are totally off when the pedals are not pressed and fully on when you have pushed them down Sent from my SM-T835 using Tapatalk

Like@Maxsenna says, we have all been there.... Sent from my SM-T835 using Tapatalk

You have the keyboard disabled in VA (the middle icon on the right hand side of the screen) click on it to remove the red circle Sent from my SM-T835 using Tapatalk