VAICOM PRO plugin for VoiceAttack

Is the module recognised in the control panel.

If no. Did you do the needed repair? (After every update).

Cheers!

 

Sent from my ANE-LX1 using Tapatalk

same problem, the sentence is recognized from VAICOM but not from DCS.

The firsts two or three sentence are recognize by DCS (eg. Ground power on) then nothing... and i CANNOT anuy more open DCS COMs menù (of course in vaicom Disable menù is OFF) with \ key or VHF UHF keys but if i try before a voice command or without to load vaicom they are working fine

sometimes it look like if it is very very slow or like if the message is recived in DCS only if DCS com menù key is pressed '\'

it seems to be a problem only in MP

i checked it in NTTR theatre, with F16 and SRS active

Yes I stated Vaicomm works in Voice attack just not ingame..I mean it still accepts the command ingame just that the command does not get triggered.. this is a mere hours old Fresh install of Win 10

Right. I think I get it. Commands are understood in VA, but doesn't get passed on to DCS.

Okay. Are you using Stable, OB, Steam? And have you set path an sliders accordingly?

Again, do you see the module in the VAICOM control panel after you have entered the cockpit in DCS?

Cheers!

Sent from my ANE-LX1 using Tapatalk

same problem, the sentence is recognized from VAICOM but not from DCS.

 

The firsts two or three sentence are recognize by DCS (eg. Ground power on) then nothing... and i CANNOT anuy more open DCS COMs menù (of course in vaicom Disable menù is OFF) with \ key or VHF UHF keys but if i try before a voice command or without to load vaicom they are working fine

 

sometimes it look like if it is very very slow or like if the message is recived in DCS only if DCS com menù key is pressed '\'

Right. I think I get it. Commands are understood in VA, but doesn't get passed on to DCS. Yes. When you've configured TX buttons in the VAICOM profile in VoiceAttack, they should be disabled in DCS.

Okay. Are you using Stable, OB, Steam? And have you set path and sliders accordingly?

Again, do you see the module in the VAICOM control panel after you have entered the cockpit in DCS?

One more thing, are you saying that if you press the "keyboard radio button" in DCS, suddenly the command works? If yes, which module?

Cheers!

Sent from my ANE-LX1 using Tapatalk

Okay. Are you using Stable, OB, Steam? And have you set path and sliders accordingly?

OB, F16, NTTR, but only in MP in instant flight it works fine

 

Again, do you see the module in the VAICOM control panel after you have entered the cockpit in DCS?

YES

One more thing, are you saying that if you press the "keyboard radio button" in DCS, suddenly the command works? If yes, which module?

Cheers!

YES

this is the sequence

Enter into the serve, asked for groung power by vocie command and the command is recognized from DCS, when i asked fro ground power off is reconignez from VAICOM but not from DCS, if i said it again, nothing if i press DCS menu command then without nay other key i get 2 or more ground power off from DCS, sometimes i have to press more then one time to open the com menù and usually after this any other voice command is not recognized

Right. I think I get it. Commands are understood in VA, but doesn't get passed on to DCS. Yes. When you've configured TX buttons in the VAICOM profile in VoiceAttack, they should be disabled in DCS.

Okay. Are you using Stable, OB, Steam? And have you set path and sliders accordingly?

Again, do you see the module in the VAICOM control panel after you have entered the cockpit in DCS?

One more thing, are you saying that if you press the "keyboard radio button" in DCS, suddenly the command works? If yes, which module?

Cheers!

 

Sent from my ANE-LX1 using Tapatalk

NEW TEST

it seems to be something on the server side, with other server it works fine ...

Suggestion are welcome

Hi

I use VoiceAttack in conjunction with Vaicom in DCS - mostly for commands to Jester.

A while back I had this issue where VA would continuously stop listening. After some googling I found that it was Sonic Studio - stopped that and all was well - uninstalled it for good measure :-p

What I also noticed was that while I was using VA in DCS the comms menu would keep popping up and disappearing. Googled the issue and one of the steps recommended was deleting an export.lua file. That resolved the comms menu popup, but now the "listening suspended" issue is back.

All seems to work fine until I'm loaded into my plane at which point VA gives the red disable icon over the headset icon and the log says "listening suspended".

No more Sonic Studio or the MSI software mentioned, so not sure what is causing it. Any help would be appreciated.

Thanks

I get the red mic symbol a lot.

Fixed by unplugging the usb mic (in my case the Rift usb) and plugging into another port.

Right. I think I get it. Commands are understood in VA, but doesn't get passed on to DCS.

Okay. Are you using Stable, OB, Steam? And have you set path an sliders accordingly?

Again, do you see the module in the VAICOM control panel after you have entered the cockpit in DCS?

Cheers!

 

Sent from my ANE-LX1 using Tapatalk

1. I am using OB

2. OK the settings where not saving.

3. Yes I see the module when I log in on the Vaicom CP..

OK, I ran the setup and reset all the options in Vaicom config and started DCS and it was working like it should be.. not entirely sure what changed but maybe after setting the settings in config then run DCS helped set them or similar, either way it is working now really wierd haha.

Well there was an update and Vaicom is not working again. it works but does not trigger an ingame action..

IT was stated to do a repair after an update, what is it that I should repair DCS or Vaicom?

Well there was an update and Vaicom is not working again. it works but does not trigger an ingame action..

 

IT was stated to do a repair after an update, what is it that I should repair DCS or Vaicom?

Close DCS. Close VA. Repair DCS. Delete export.lua (I have a working copy with settings for SRS, VAICOM and TacView in that order). Start VA. Close VA. Delete export.lua again. Copy my copy and rename to export.lua Start VA, start DCS.

It's cumbersome, but it works every time!

Cheers!

Sent from my ANE-LX1 using Tapatalk

This is what I do after every DCS update. (Like yesterday).

Close DCS. Close VA. Repair DCS. Delete export.lua (I have a working copy with settings for SRS, VAICOM and TacView in that order). Start VA. Close VA. Delete export.lua again. Copy my copy and rename to export.lua Start VA, start DCS.

It's cumbersome, but it works every time!

Cheers!

 

Sent from my ANE-LX1 using Tapatalk

OK I tried that and when I checked my settings they where all reset so I reinstared my settings and started DCS and it did not work. itv works to the point where VA hears the command but it does not trigger a responce in DCS..

Now I checked the Config screen ingame and when I went to the PTT screen the jet was not recognised, I was using the f16 and I dont think any jet is recognised in the PTT Screen maybe that is a clue?

OK I tried that and when I checked my settings they where all reset so I reinstared my settings and started DCS and it did not work. itv works to the point where VA hears the command but it does not trigger a responce in DCS..

 

 

 

Now I checked the Config screen ingame and when I went to the PTT screen the jet was not recognised, I was using the f16 and I dont think any jet is recognised in the PTT Screen maybe that is a clue?

Hmmm... You do run VA as administrator?

Sent from my ANE-LX1 using Tapatalk

Huh Well I guess that is what I needed to do but I thought I was running as admin but maybe when I repaired or reinstalled it the admin rights went off..

So I just tested it in Admin mode and it is working. I will try and keep in mind what you said about repairing DCS and Vaicom.

Huh Well I guess that is what I needed to do but I thought I was running as admin but maybe when I repaired or reinstalled it the admin rights went off..

 

So I just tested it in Admin mode and it is working. I will try and keep in mind what you said about repairing DCS and Vaicom.

Sent from my ANE-LX1 using Tapatalk

Hello !

Has anyone encountered popup of comm menu when using A10C II with Vaicom ?

I checked with legacy A10C and I don't have this problem. I can speech to my wingman through Vaicom and no popup.

I tested that with the Easy Instant Action mission in Caucasus in both airplanes.

Thanks for any advice !

Hello !

Has anyone encountered popup of comm menu when using A10C II with Vaicom ?

I checked with legacy A10C and I don't have this problem. I can speech to my wingman through Vaicom and no popup.

I tested that with the Easy Instant Action mission in Caucasus in both airplanes.

Thanks for any advice !

Does this only happen in that module?

Cheers!

Sent from my ANE-LX1 using Tapatalk

I couldn't get any response in the A10 II last night at all. Worked fine in the original A10. Only had time for a quick test flight so no real resetting of anything.

Sent from my SM-T835 using Tapatalk

Hi

Viacom Pro works fine in all my modules except the Huey. I get the read back of my message, but no response to my calls. Can anyone point me in the right direction?

Neal

Does this only happen in that module?

Cheers!

 

Sent from my ANE-LX1 using Tapatalk

Looks like yes, I tested FA18 with SC, wingman and ATC, HUey on a simple mission and again legacy A10C to no luck with the A10C_2 : every push on MIC Switch pops up the Comm menu, workaround is to use another radio to make that menu disapear...

Edit : FYI I am on latest OB repaired with no mods and I followed post patch instructions to re-enable Vaicom

Thank you !

@Nanolab Try disabling your HOTAS MIC keybinds in DCS config.

I couldn't get any response in the A10 II last night at all. Worked fine in the original A10. Only had time for a quick test flight so no real resetting of anything.

 

Sent from my SM-T835 using Tapatalk

Sent from my ANE-LX1 using Tapatalk

@Nanolab Try disabling your HOTAS MIC keybinds in DCS config.

Well, thanks a lot !! Simplest solution is always the best !

My bad : I knew I had to get through first installation steps of Vaicom because the plane was new and standalone : not a legacy A10C upgrade....

Everything is now working great !

Well, thanks a lot !! Simplest solution is always the best !

 

 

 

My bad : I knew I had to get through first installation steps of Vaicom because the plane was new and standalone : not a legacy A10C upgrade....

 

 

 

Everything is now working great !

Sent from my ANE-LX1 using Tapatalk

Tested myself. Acknowledge beep, but nothings happening. Only A-10C II, everything else is fine.

 

Sent from my ANE-LX1 using Tapatalk

Sent from my SM-T835 using Tapatalk