VAICOM PRO plugin for VoiceAttack

Have you tried the track clip pro? It connects to your headset and not a baseball cap. I hate to see you miss out on a good program for something with an easy workaround.

 

 

Sent from my iPhone using Tapatalk

 

Thanks for that. Yes, I do have the track pro clip, but I don’t like the fact that it is wired, and, unless I spent a reasonable amount on a wireless set, the headset would be another wire!

I just don’t like wearing a headset for hours. Can’t hear the phone, people talking to you, becomes uncomfortable after a time, can’t move around, etc. I also have a good set of 5.1 speakers and DCS sounds great through them!

As DCS sound that interferes with VA tends to be mechanical and fairly constant, I’m a bit surprised that couldn’t be filtered out and distinguished from a human voice.

It is a shame as I am missing out on something good.

hi can you help me , i was import f10 menu command (COPY) from basic flight training , edit and save profile . This word was recognized , but no effect in game ...

hi can you help me , i was import f10 menu command (COPY) from basic flight training , edit and save profile . This word was recognized , but no effect in game ...

It does not work because it is also a duplicate word in the Viacom pro words list. You won't be able to use some of the f10 commands for the basic/advanced/tactical qualification misisons.

It does not work because it is also a duplicate word in the Viacom pro words list. You won't be able to use some of the f10 commands for the basic/advanced/tactical qualification misisons.

 

ok thanks

Myk problem is not with the airframe but with va and Viacom. I figured out how to get the comm menu to come up when i press the trigger in dcs but va does nothing.

@BlacleyCole I find it hard to follow, perhaps others can comment. I cannot help if you're not specific. Refer to my previous answer and consult the User Manual on how to set up your PTT configuration.

@Ganeshka Improvements for F10 commands are being addressed in upcoming update https://forums.eagle.ru/showpost.php?p=3427852&postcount=355

i found the best results with 100% command weight and confidence, plus talking like the in game ATC, clear pauses

 

i did have microphone really overdriven so it was really sensitive, soon as i put that back to default and did the above it works 99% of the time

 

i had good results with the rift mic and now ive combines the rift and my head set with boom mic its perfect.

 

its well worth plugging away to get it to work, because when its working its amazeballs (as my 9 yr old told me)

 

Just my tuppence

 

https://forums.eagle.ru/attachment.php?attachmentid=179538&d=1519162797

 

edit: i just called "Fencein" on a mission (as a joke) and my wingman said "copy" much amazeballs!! :pilotfly:

Edited March 21, 2018 by skunk160

Well got the mic working in the setup/test phases but doesn’t work in va.

Having an annoying issue here. I have Vaicom Pro installed and in order to hear the squelch when doing a mike press I have to Ctl+C then X out of the config pop-up. I don't need to do anything while there just bring it up and exit it. What''s wrong?

Following on from my earlier posts, I decided to buy a desktop microphone, and frankly, things are not much better.

I am really struggling with speech recognition in VA/Viacom, even with no other sounds, just in Keywords Training Mode.

The first really annoying issue is that I get this pop-up menu asking me which I want to select - see attached grab - EVERY time I say anything!

Secondly, even in silence, I am struggling to make VA/Viacom understand the first 2 phrases, i.e. AAA and Abort Inbound.

Can anyone help here? I have spent quite a lot of time over the last few days trying to get this to work.

You’re not supposed to be running speech recognition while VA is running mate! ������

You’re not supposed to be running speech recognition while VA is running mate! ������

Eh, have you read the manual?

If you have a brand new mic it's advisable to take the general Windows recognition training first so the engine can get used to your voice in combination with this new microphone.

Control Panel\Ease of Access\Speech Recognition

This will greatly reduce the number of these 'helpful' Windows alternates popups during Training Mode (which you can just cancel btw).

If you have a brand new mic it's advisable to take the general Windows recognition training first so the engine can get used to your voice in combination with this new microphone.

Control Panel\Ease of Access\Speech Recognition

This will greatly reduce the number of these 'helpful' Windows alternates popups during Training Mode (which you can just cancel btw).

Thanks Holywood. I have gone through the training 3 times already. Windows has no trouble understanding the normal commands.

I can hardly get VA/Viacom to recognise anything!

What is that annoying dialogue box I posted about in the attachment? Surely that shouldn't be coming up.

There is something weirdly wrong here. Yesterday, in my previous exchanges here, it was assumed that it was the noise from my external speakers causing the issue, but we can see that is not the root of the issue as I am doing the Keywords Training Mode in total silence!

It's a MS Windows thing. Carefully follow the steps noted in below link:

 

https://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/speech-alternatives-panel-comes-up-every-time/985becaa-a14d-4741-a16b-485026081b08

 

Also carefully inspect the input levels in VA window while speaking, making sure it uses the correct input device.

The VA meter should show a wide range of deflection.

EDIT: VA input device is set in Recognition tab of VA options window, also there (un)check the Disable Adaptive Recognition and Disable Acoustic Echo Cancellation options to see if it makes a difference.

 

If you need more help send me a PM.

Edited March 21, 2018 by Hollywood_315

@skunk160 Much amazeballs helmet dude! Gotta have me one of these too lol

Sound like a pretty decent recognition rate you've got there there @99% :pilotfly:

And yep Fence In / Out is part of the Extended command set..

 

Cheers

It's a MS Windows thing. Carefully follow the steps noted in below link:

 

https://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/speech-alternatives-panel-comes-up-every-time/985becaa-a14d-4741-a16b-485026081b08

 

Also carefully inspect the input levels in VA window while speaking, making sure it uses the correct input device.

The VA meter should show a wide range of deflection.

EDIT: VA input device is set in Recognition tab of VA options window, also there (un)check the Disable Adaptive Recognition and Disable Acoustic Echo Cancellation options to see if it makes a difference.

 

If you need more help send me a PM.

Thanks Hollywood. I’ll try it all again tomorrow and PM you if necessary. I really want to make this work. Too good to miss out on!

@BlacleyCole Can you be more specific on what you are trying to accomplish with VA? Are you having problems issuing commands in the Huey?

Yes I can pull up VoiceAttack and viacompro I put in my registration info have to everytime but that might be because the fields revert to the input email and key I have tried not entering the info yet. I go in to dcs start up a mission hit lark+ lalt+c that sometimes will open Viacom pros app I have my trigger set to pilot mic comm or something similar I have the chatter pack and come to think of it I only hear chatter when I input the key for chatter I key the mic ie press the trigger say something nothing happens I say stuff like tower taxi tower hover check no response but if I use the f commands I get a response.

 

GoldRake can you do two things For Me?

 

1)write a checklist for step by step on how you installed both VoiceAttack and Viacom pro with you configuration settings

2) write a detailed step by step checklist for how you pull up va and vp in dcs to get it work from the desktop.

 

Tia

Edited March 23, 2018 by BlacleyCole

+++ Release update 2.5.1 +++

 

Hey guys

 

Happy to announce that VAICOM PRO version 2.5.1 can now be downloaded from the website:

https://www.vaicompro.com/downloads.html

It features some significant updates based on the wishlist posted earlier

https://forums.eagle.ru/showpost.php?p=3427852&postcount=355

and quite a few minor code improvements have also been included.

 

Details are in the updated User Manual. Descent and Cargo flows are now supported for helos,

specific menu functions were added (see page 20), there's an improved F10 import function

and no less than 21 additional callsigns can now be used for JTAC (page 45).

 

Existing (2.5.0) users please carefully check the included installation notes:

for this new installation you need to first remove your current installation folder.

 

- This update will reset your keywords database.

- If you want to keep a reference to your old database you can use the Export function in the Keywords Editor.

- PRO users will not need to re-enter license key information after the update.

- You will not lose any speech recognition (training profile) information with this update.

 

- If you don't want to re-download the Chatter.dll file, make a back-up copy first and put it back later in the Extensions subfolder.

- Remove your existing VAICOM PRO installation folder and it contents completely from the VoiceAttack Apps folder.

- Then proceed with the regular plugin installation steps for the 2.5.1 plugin.

- After install go through the FINISH steps to update the VA profile (manual page 28 ).

 

Happy flying!

Edited March 23, 2018 by Hollywood_315

Thanks a lot Hollywood!

Wow! Thanks Hollywood that was fast!

@BlacleyCole I mostly followed the manual for step by step checklist. I would not be able to improve the manual with a checklist. Sounds to me that the best way to help you get your VA going is to meet you on a public mp server and compare notes through Teamspeak. When I get back to my PC I am going to update to version 2.5.1. Let me know if you are on mp.

 

Sent from my SGH-I337M using Tapatalk

Well...

 

First go didn't work that well. I removed the old install, replaced with the new one and even retrained with the new key words. But, still had trouble calling up the F10 menu and JTAC callsign Uzi will not respond. Using nearest works but selects the wrong JTAC. Trying to use the menu to call up Uzi still will not get a response either. Only way to get Uzi to respond, is by reassigning the HOTAS mic buttons to the radios then use the menu option in Vaicom Pro.

 

The F10 menu sometimes works but mostly calls up the options so not sure if it's just having trouble recognizing "mission" or "server" first. Didn't have trouble in training these though.

 

Thoughts? I'll keep trying.

@Hellride OK Uzi as JTAC callsign works fine here during testing. Just to check are you on FREE or PRO version. Can you try a few other missions to test and catch me on PM to narrow it down. Cheers

 

EDIT: Forgot to mention one thing, existing users need to go through the FINISH steps after install to update the VA profile (manual page 28 ).

You may have done this already but just in case. I'll update the install notes.

Edited March 23, 2018 by Hollywood_315