VAICOM 2.0 for VoiceAttack

Hollywood_315 · April 10, 2016

Hey Blue - I suggest you check the note on keyboard layout (attached to first post), you may have a non-US layout mismatch.

You will also need to check that NUM keys and also the HOTAS MIC buttons are not in use anywhere in DCS config (see manual).

The HOTAS emulated keys must be set-up for press-and-hold in either TARGET or Autohotkey (check Davisons post #2).

If that doesn't fix things make sure to send me a PM.

shaz56 · April 10, 2016

script stops running randomly

I also find that the autohotkey script seems to randomly stop and need to be reloaded. Any thoughts or help would be appreciated

Hi Hollywood, I sent you a pm couple of days ago and not heard from you. Then I saw this above which is exactly what is happening to me, look forward to any remedy. thanks for being patient with us.

Hollywood_315 · April 11, 2016

Shaz there must have been some glitch, I don't have a message from you in my inbox.

Autohotkey must be run as administrator: for Jason that fixed it.

shaz56 · April 11, 2016

Hollywood Hi, yes i have admin rights set for all my software but to make sure i was selecting "run as admin" anyway to no avail. I had win10 upgrade from 7 but for some reason DCS would crash after ten minutes or so. Found out I could do a complete Fresh install so I'm in the process of re-installing everything from scratch, will let you know how I get on. Don't know what happened to my p.m. Thanks.

Hollywood_315 · April 11, 2016

No worries mate - let me know if this re-install improves things, if not send me a PM again and we'll get it sorted out.

Corbett1403 · April 11, 2016

Hi I can't get this too work iv tried I'm not great with computers iv done everything via instructions

Sent from my iPad using Tapatalk

Hollywood_315 · April 12, 2016

Hey Corbett

Well, always willing to help where I can. But generally there's a lot of things that can be specific to your setup.

So the description of the problem must be a bit more more precise for me to be able to support.

Below I will state -for everyone actually- how to raise a support ticket :D

----- SUPPORT INSTRUCTIONS -----

First I need you to make sure that you have read the User Manual and followed the detailed setup and usage instructions in there to the letter.

Also you must have carefully checked the notes attached to the first post (#1), and additionally Davisons post (#2) if you plan to use Autohotkey for HOTAS setup.

In this thread there is lots more additional useful info that could help you identify what could be your issue.

Try using the 'search this thread' forum function.

Then if all else fails please state the details of your problem (here or via PM), and under which circumstances it occurs.

Kindly include at the least the following info:

Windows version
DCS version
VoiceAttack version
VAICOM profile
Easy Comms mode ON or OFF
HOTAS/Autohotkey used
Other peripherals running (TrackIR, HELIOS,..)

This will help to get rapidly to the bottom of it.

In almost every case we manage to get things sorted out, so no worries!

Cheers

:beer:

Helpdesk Hollywood

----

Edited April 12, 2016 by Hollywood_315

Hollywood_315 · April 21, 2016

From the manual

done!!
Now for the getting it working :) :book:

Thanks mate, much appreciated.

You keep up the good stuff on the Vive thread-

I ordered one, so following with interest :thumbup:

Grtz

DigitalEngine · April 21, 2016

VoiceAttack problem [solved]

Just a heads up,

If your wanting to use Vaicom, which uses VoiceAttack, and your having a problem with VoiceAttack not seeing your recording device in the VoiceAttack voice "level bar", and your sure your recording device is configured and working, several others have had this problem also.

I, and several other have solved it by exiting a program called Sonic Suite 2, in the Windows task bar (the lower right windows task bar).

Seems as VoiceAttack can have conflicts with some sound management applications.

https://groups.google.com/forum/#!topic/voiceattack/VxNC27Bhw1E

Other than that, for VR especially, Vaicom is a must have and seems to work great!

Terrorvogel · April 27, 2016

Hi Hollywood,

first of all thank you for this promising tool!:thumbup:

Nearly everything is working now after reading the manual and this endless thread.

But i have two questions to make it really work for me:

1. Many spoken commands are not recognized altough i have learned them directly into the voice recognition library. For example Ka-50 profile: When i say "Two go recon two" then in VA-log there is shown: "to goal RE:"

No matter how often i'm repating the not recognized words learning in library...

Can you give me any hints how to sharpen the recognition or what i'm doing wrong maybe?

Mircophone is set up right and i am using a german Win 10 with english voice recognition and inside Voice Attack i have chosen the english voice recognition. My spoken englisch is not part the problem:huh:

Voice Attack is latest but NO beta!

I have changed the the engl. DCS communication key to german keyboard because nothing happend without.

The pathes were customized as described du to changes in DCS World openbeta.

2. Sometimes when using VAiCOM commands DCS changes to outside view. This is really annoying during fight and i do not find the cause. I have already deleted F-12 and F-11 keys inside DCS. In Trackir the F-keys are not enabled. Any ideas?

Kind regards,

Terrorvogel

Hollywood_315 · April 27, 2016

Hey Vogel,

Thanks :thumbup:

I assume you've done all the voice training,i.e. via Windows Control Panel / Ease of Access.

Then likely something minor, e.g. subtleties in speech timing can make the difference for recognition.

You just need to develop that by using it more.

For this example start with saying your command very deliberate, i.e. as 'two,'..(very short pause)...'go recon 2.'.

This will increase your hitrate. Then, when used more often, as MS Speech recognition learns, you'll be able to shorten your timing.

Let me know how it goes.

View switches should not occur when used correctly, but there's always the chance of a glitch.

A common mistake is releasing the PTT key too soon (i.e. before the beeps).

Also if you use Easy Comms OFF, TrackIR may be interfering with HOTAS MIC keybinds.

I'll send you a PM to see if this is reproduceable and can be nailed down to anything specific.

Grtz

DigitalEngine · April 28, 2016

Another tip I've noticed, sometimes a short pause between the recipient class and the command, for example, ATC Options. If I just stay "ATC Option", I'll get the main comm options menu, but if I say "ATC" (then about a 1.5 second pause or so) and then "options" then I'll successfully get the ATC Options menu.

Also, if you can have your Voice Attack widow up and viewable, you can see how Voice Attack/Windows is interpreting your words real time.

And you can train Windows10 to interpret certain individual words you and Windows10 maybe having difficulty with. For me the word "Chief" Windows10 just couldn't get until I did this.

All Apps>Windows Ease of Access>Windows Speech Recognition>Right Click on the Windows Speech Recognition Tool>Select "Open the Speech Dictionary">Change existing words> Select ether "Add a new word" or "Edit a word" as appropriate, and follow the directions.

Again thanks Hollywood for a indispensable app!!

Hollywood_315 · April 28, 2016

--- NEW MODULE AVAILABLE: MIG-15bis ---

A new module is available! The MIG-15bis.

You can now fly this epic aircraft without menus using VAICOM.

Thanks donators!

Download here:

https://www.digitalcombatsimulator.com/en/files/1884218/

Enjoy!

Hollywood

Note: This module requires VoiceAttack version 1.5.8.16 beta or higher.

Edited April 29, 2016 by Hollywood_315

Terrorvogel · April 28, 2016

Thank you for the hints guys!

Two things that went wrong here in my setup:

1. I noticed that every time i started Voice Attack my microphone volume is decreasing extremely (down to 15%). So i disabled under microphone's advanced properties the option "Allow applications to take exclusive control of this device. I have discovered inside the www that if creating a new windows voice-recognition-profile, the CURRENT volume of the microphone ist set and linked with this profile! So when you are creating a profile, watch at you current mic volume when doing this! Whenever windows voice recognition is being used (for example by Voice Attack), that saved/linked mic-volume will be restored and if it is too low (like in my case), recognition can make big problems.

So i deleted my englisch voice recognition profile after changing that mic setting in nr.1 and created a new one with perfect mic-volume settings.

2. That hint with the pause between the recipient makes everything better too! I hope windows is learning with the time so i can speak a little bit faster in future.

Now it is behaving a lot better

Hope this can solve some issues for others too.

Thanks again for your help!

Regards,

Terrorvogel

Kozmyk · April 28, 2016

Yeah that "Allow applications to take exclusive control of this device." gave me a few problems when I first started using Voice Attack. Once I found the sweet spot though, I never looked back. :)

Kozmyk · April 28, 2016

--- NEW MODULE AVAILABLE: MIG-15bis ---

A new module is available! The MIG-15bis.
You can now fly this epic aircraft without menus using VAICOM.

Thanks donators!

Download here:

https://www.digitalcombatsimulator.com/en/files/1884218/

Enjoy!
Hollywood

Jolly good show.

the_soupdragon · April 28, 2016

NIce one mate

Black Viper · April 29, 2016

Hi Hollywood,

I read the whole thread and I think my problem is located in my german keyboard layout. I think I forget nothing what you described many times here; so I tried to do what you have written according to the keyboard layout. My problem only is, I can´t find the lines you mentioned. I tried to change the F15 profile first, I found many of the _Menu_Execute lines you mentioned, but NO line where the "\" for the menue is written in ! I would have to chance this into "#" as this is the DCS command for the menue in the german version. Could you please be so kind to tell me, if I´m searching somewhere wrong?

Thanks a lot in advance!

Hollywood_315 · April 29, 2016

Hey Viper,

Sure no problem. The steps are like this:

*) Load the profile and go to Edit (the icon with the pencil)

*) Then you'll see a long list of Categories. (If not: look below in VA status bar and press the small square icon left of 'XXX commands'.)

*) Press + next to category 'Process Management'

*) Now look for command '_Menu_Execute'. (Note you will be editing just this one, not other commands like '_Menu_Execute_ATC' etc.)

*) Double-click the command to edit. Change the lines where '\' key is referenced and store with OK. (for F-15C this is lines 3 and 6).

Done! If you need more help just send me a PM.

Black Viper · April 29, 2016

Hey Viper,

Sure no problem. The steps are like this:

*) Load the profile and go to Edit (the icon with the pencil)
*) Then you'll see a long list of Categories. (If not: look below in VA status bar and press the small square icon left of 'XXX commands'.)
*) Press + next to category 'Process Management'
*) Now look for command '_Menu_Execute'. (Note you will be editing just this one, not other commands like '_Menu_Execute_ATC' etc.)
*) Double-click the command to edit. Change the lines where '\' key is referenced and store with OK. (for F-15C this is lines 3 and 6).

Done! If you need more help just send me a PM.

Hi Hollywood,

you´re unbelivable quick- thanks a lot! Seems I´m idiot, I go to the Voice attack folder on my c: drive and tried to change the lines with notepad++ !!:doh: Did not give a thought to change it in the Voice attack window !! Will give it a try this evening latest, but I think, I will now be able to find the lines. Sorry for my stupidity, maybe it happened because of my bad english...:cry: Will return here, if I got it !

Dutch60 · April 29, 2016

Hi Hollywood,

Importing of the new MIG-15bis profile is giving an error?

Voice Attack version is 1.5.8.14 (prerelease) on OS Windows 10 x64

Error Dialog:

Error loading profile data.

[There is an error in XML document (2439, 8).]

The string '' is not a valid Boolean value.

There seems something wrong in the XML?

Hope you can figure out what is wrong?

Love to fly the MIG-15bis.

Hollywood_315 · April 29, 2016

Hey landgenoot :-)

For the MIG-15bis can you try with latest VoiceAttack beta i.e. 1.5.8.16 and let me know how that goes. Send me a PM if you have more questions. There were some issues with previous VA beta versions e.g. .14, but .16 looks solid.

Thanks

Dutch60 · April 29, 2016

Upgrading to Voice Attack version is 1.5.8.16 (beta) fixed the problem

Thanks landgenoot :thumbup:

Black Viper · April 29, 2016

Hi Hollywood,

got it working! Thanks mate for this great program- really puts the feeling of being in a real jet to the next level !!!

Hollywood_315 · May 1, 2016

+++ IMPORTANT NOTICE FOR HOTAS USERS +++

Hey guys,

Great news!

VoiceAttack latest version (1.5.8.17 beta) now supports functions for joystick button release.

This means that keyboard emulation is no longer needed to use VAICOM Push-To-Talk with your HOTAS: TARGET and Autohotkey have just become obsolete!

This should make life a lot easier i.e. HOTAS PTT setup much more straightforward :)

Read below on a few simple steps to have your HOTAS now work directly with VAICOM. :joystick:

Join me in a big word of praise to the guys at VA who were kind enough (after much nagging from my side :D) to implement this new feature.

Thanks Gary!!

Grtz

Hollywood

++++++

--- HOTAS PTT direct setup ---

1/5/2016

You can use VAICOM PTT directly with your HOTAS.

Follow below steps to make VAICOM PTT respond directly to joystick buttons.

Adapt for each VAICOM profile that you intent to use.

First:

*) Upgrade your VoiceAttack to version 1.5.8.17 beta or higher.

Existing VAICOM users:

*) If you are already using keyboard emulation with TARGET or similar: disable it.

*) If you are already using keyboard emulation with Autohotkey: from now on do not run Autohotkey anymore.

To set up direct PTT:

*) In VA, go to options/general/ joystick options. With the + icon, add your joystick e.g. HOTAS Warthog Throttle. OK.

*) Load the VAICOM profile and go to edit (the icon with the pencil). Open (+) the Push-to-Talk category. Edit each command in there as follows:

*) Double click to open. Check 'When I press button' and click on the [...] button.

*) Select Joystick Buttons window: Press the refresh button (the circular arrow). Note: It is necessary to do this refresh every time before you set up a new button.

*) Then, on your joystick, press the physical button you want to use and it will be recognized in the window.

*) IMPORTANT: if you are editing the command for RELEASE e.g. 'Transmit VHF1 released', check the box 'shortcut is invoked only when all buttons are released'. Store with OK.

*) IMPORTANT: if you are editing the command for PRESS e.g. 'Transmit VHF1 pressed', do NOT check this box.

*) Note: Of course in above the joystick buttons used for VHF1 press and VHF1 release must be the same button! Make sure you get this right for each press/release combo.

*) Note: optionally you can uncheck the 'when I press keys' option for each command if you intent to no longer use your physical keyboard for VAICOM PTT.

*) Check in the VA log that PTT press/releases are correctly recognized.

Done!

------

Edited May 1, 2016 by Hollywood_315

Sign In

VAICOM 2.0 for VoiceAttack