Jump to content

VAICOM PRO plugin for VoiceAttack


Hollywood_315

Recommended Posts

Yeah I copied my entire AppData + Documents folders over so was hoping the settings would carry over but clearly not. Also I copied the Vaicom pro folder in the prog files x86/voice attack/apps vaicom pro over too, im at a loss with this now, please let me know if you figure it out!

  • Like 1
Link to comment
Share on other sites

Yeah I copied my entire AppData + Documents folders over so was hoping the settings would carry over but clearly not. Also I copied the Vaicom pro folder in the prog files x86/voice attack/apps vaicom pro over too, im at a loss with this now, please let me know if you figure it out!
I will!

Sent from my MAR-LX1A using Tapatalk

Link to comment
Share on other sites

Yeah I'm at a complete loss I've tried everything I can think of to get it to work on my new install but no joy, commands get recognized by the application but then straight afterwards i get the error .... awaiting additional input, I hope someone finds a solution soon. I also just realized that both VA and VPRO have methods built in for backing up both the profiles from VA and the settings from VA along with being able to export settings from the VA one too.

Link to comment
Share on other sites

Well I solved the issue, it was a combo of me running the beta version of VA (unsupported by VPRO), and somehow my keyword list had gotten messed up and there was only a few keywords in the list , despite them all being in the profile.

Then I removed and reinstalled both VA and VPRO and used the default VA profile that is created by VPRO upon install.

 

All I have to do now is point my custom additions profile to the VAICOM profile and I should be good to go, a special thanks to MAXsenna who helped via his comments on the discord!

  • Like 1
Link to comment
Share on other sites

Well I solved the issue, it was a combo of me running the beta version of VA (unsupported by VPRO), and somehow my keyword list had gotten messed up and there was only a few keywords in the list , despite them all being in the profile.

Then I removed and reinstalled both VA and VPRO and used the default VA profile that is created by VPRO upon install.
 
All I have to do now is point my custom additions profile to the VAICOM profile and I should be good to go, a special thanks to MAXsenna who helped via his comments on the discord!
Thought that was you!
Happy to help!

Sent from my MAR-LX1A using Tapatalk

  • Like 1
Link to comment
Share on other sites

Hi,

 

VoiceAttack has just moved to 64 bit with its 1.8.8 version - does anyone know if VAICOM is compatible with the 64 bit version?

Processor : Intel Core i7 7800X (3.8 - 4.2 GHz) . Motherboard : ASUS TUF X299 . Memory : 16Gb DDR4 1333 . Graphics : NVIDIA GeForce RTX 2080 Super (+100 CC +700 MC) . Install : DCS on 500Gb SSD . Screen : 3440 x 1440 display with GSYNC . Control : TM Warthog HOTAS, CH Pro Pedals, Naturalpoint Track-IR . Software : VoiceAttack with VAICOM Pro, DCS BIOS

Link to comment
Share on other sites

I have been getting quite a lot of Voice attack crashes during missions, starts off fine, but after about 5-10 mins, the program shuts down, normally at a crucial time.. like calling the ball !!

i7 9400 @ 2.9 Ghz

32 GB RAM

1 TB SSD

RTX 2060 8GB

Windows 10 64 bit

Link to comment
Share on other sites

19 minutes ago, MAXsenna said:

Htmf.... Was gonna update post, and it deleted the content.
Anyway, Steam auto updated Voice Attack, 1.8.8 64bit.
VAICOM works without a hitch.
Cheers!
 

Great, thanks for that!  

  • Like 1

Processor : Intel Core i7 7800X (3.8 - 4.2 GHz) . Motherboard : ASUS TUF X299 . Memory : 16Gb DDR4 1333 . Graphics : NVIDIA GeForce RTX 2080 Super (+100 CC +700 MC) . Install : DCS on 500Gb SSD . Screen : 3440 x 1440 display with GSYNC . Control : TM Warthog HOTAS, CH Pro Pedals, Naturalpoint Track-IR . Software : VoiceAttack with VAICOM Pro, DCS BIOS

Link to comment
Share on other sites

I have been getting quite a lot of Voice attack crashes during missions, starts off fine, but after about 5-10 mins, the program shuts down, normally at a crucial time.. like calling the ball !!
Consider using the VAICOM tray app, and it will restart VA.
I haven't had VA crashes for ages. Lucky me!

Sent from my MAR-LX1A using Tapatalk

Link to comment
Share on other sites

 After todays update my Vaicom is nog longer functional. Every open mike goes from "listening" to "suspended" after 0.5 seconds. The open mike sound works correctly i.e. it plays when i press the button and when i release the button. The listening function however only works for 0.5 seconds. If i'm fast enough i can actually send a couple of basic commands in this short period so everything else seems to work.

 

This only happens when a module is loaded. Outside of modules the mike stays open an receives commands as normal.

 

I have reset the lua settings of the app and also upgraded voiceattack to the lastest 64 bit version. DCS is Latest beta build which is now the same as stable.

.


Edited by Nickentik
Link to comment
Share on other sites

 After todays update my Vaicom is nog longer functional. Every open mike goes from "listening" to "suspended" after 0.5 seconds. The open mike sound works correctly i.e. it plays when i press the button and when i release the button. The listening function however only works for 0.5 seconds. If i'm fast enough i can actually send a couple of basic commands in this short period so everything else seems to work.
 
This only happens when a module is loaded. Outside of modules the mike stays open an receives commands as normal.
 
I have reset the lua settings of the app and also upgraded voiceattack to the lastest 64 bit version. DCS is Latest beta build which is now the same as stable.
.
Don't think I've seen this issue before,could you make a new thread for future reference?
You are referring to the option in VAICOM c control panel and the Tomcat, right?
I'm positive and don't that issue, but I'll check later tonight. Today I'm playing with another type of joysticks and pedals. Escavator. 10 axis. It's really hard with the muscle memory from flying. Flying is easier. Hats off to all escavator drivers!

Sent from my MAR-LX1A using Tapatalk

Link to comment
Share on other sites

Posted (edited)

@Nickentik

 

On the MP tab, inspect your VoIP Control slider.
If it's on TX Link mode, select MP Only and restart.

Alternatively select one of the other two modes with the slider.


For details on the TX Link feature for VoIP see manual page 26.

 

Grtz


Edited by Hollywood_315
  • Like 1

There is no spoon.

 

Avatar_old_80x80.gif.0c105925ce4b9f5b87697ea37cbde317.gif

VAICOM PRO plugin for DCS World

www.vaicompro.com

Link to comment
Share on other sites

4 hours ago, Hollywood_315 said:

@Nickentik

 

On the MP tab, inspect your VoIP Control slider.
If it's on TX Link mode, select MP Only and restart.

Alternatively select one of the other two modes with the slider.


For details on the TX Link feature for VoIP see manual page 26.

 

Grtz

 

Thanks for the quick reply Hollywood. That did the trick !

  • Like 1
Link to comment
Share on other sites

I am also having issues since today's update.  My push to talk is working in reverse now.  When the switch is active, no inputs are allowed.  When it's not, it is in hotmic.  I do not have hotmic engaged.

  • Like 1
Link to comment
Share on other sites

3 minutes ago, cgrxman said:

I am also having issues since today's update.  My push to talk is working in reverse now.  When the switch is active, no inputs are allowed.  When it's not, it is in hotmic.  I do not have hotmic engaged.

Have you updated Vaicom?  Fwiw -I was having issues with the latest dcs stable release update, and I was .1 version off the latest. (I’m guessing there was a vaicom update recently. 

Link to comment
Share on other sites

13 minutes ago, Dangerzone said:

Have you updated Vaicom?  Fwiw -I was having issues with the latest dcs stable release update, and I was .1 version off the latest. (I’m guessing there was a vaicom update recently. 

Vaicom updated automatically. That's when the issue arose.  I am at 2.5.25.0.

 

image.png


Edited by cgrxman
Link to comment
Share on other sites

I am also having issues since today's update.  My push to talk is working in reverse now.  When the switch is active, no inputs are allowed.  When it's not, it is in hotmic.  I do not have hotmic engaged.
Save for me.

Sent from my MAR-LX1A using Tapatalk

 After todays update my Vaicom is nog longer functional. Every open mike goes from "listening" to "suspended" after 0.5 seconds. The open mike sound works correctly i.e. it plays when i press the button and when i release the button. The listening function however only works for 0.5 seconds. If i'm fast enough i can actually send a couple of basic commands in this short period so everything else seems to work.
 
This only happens when a module is loaded. Outside of modules the mike stays open an receives commands as normal.
 
I have reset the lua settings of the app and also upgraded voiceattack to the lastest 64 bit version. DCS is Latest beta build which is now the same as stable.
.
I have the same problem after updating. Was working yesterday.

Sent from my MAR-LX1A using Tapatalk

Link to comment
Share on other sites

@Nickentik
 
On the MP tab, inspect your VoIP Control slider.
If it's on TX Link mode, select MP Only and restart.
Alternatively select one of the other two modes with the slider.

For details on the TX Link feature for VoIP see manual page 26.
 
Grtz
Hey@Hollywood_315, glad to see you again.
He's not referring to MP. He's referring to the open mic selection in the control panel.
I have the same issue after updating today. Was working fine yesterday.
Pressing a TX will immediately trigger "listening suspended" right after "listening resumed". Seems that several of us have that issue.
When selecting "open mic" ordinary VoiceAttack commands work fine.
Cheers!

Edit: Never mind that worked, but why would MP settings interfere with DP. Does this mean "transmit parallel" doesn't work anymore?

Sent from my MAR-LX1A using Tapatalk


Link to comment
Share on other sites

My MP setting was already at Broadcast Parallel and not TX Link.  I deleted the AUX 4 settings where I had them and went to ICS 5 to key up for ground crew.  That seemed to fix it.

Link to comment
Share on other sites

  • Recently Browsing   1 member

×
×
  • Create New...