VAICOM 2.0 for VoiceAttack

[FeistyLemur]

If I do it all in one go like that the best I seem to be able to get is command recognized, profile not available. But the profile is installed. I didn't change the name of any of them.

 

90% of the time it still says command unrecognized. I tried blacklisting some words and recording pronunciations in the windows speech dictionary to get it consistent but I'm trying right now and i consistently get either "command unrecognized' or 'profile not found' if it does register at all.

Edited February 25, 2016 by FeistyLemur

[FeistyLemur]

I seem to be having a lot of problems with selecting things now that I look at it more. I can't select different airfields or farps. It locks to the nearest 80% of the time, sometimes I can fluke it off and get it to go to another airfield but most of the time it stays locked to nearest.

 

I think I must be doing something really wrong somewhere.

[FeistyLemur]

Hi guys. After installing VA, VAICOM and Hotkey, I´m fighting with some issues and I´m wondering if someone could help me. Basically, everything is working but not really very well. I started with DCS 1.5 openbeta and switched to the 1.5 stable version. My issues are as follow:

 

- When I start VA and select the respective profile (A-10C), the famous „Unable to get value from URI - Could not find file 'C:\Program Files (x86)\VoiceAttack\Apps\VAICOM\Tools\TEMP\mission.lua“ appears. I tried several hints and tipps but nothing worked. I have to admit that this is not a real problem for me, because VA is working.

- When I start a new flight with the „start mission“ command, it starts but stops immediately. I have to click ESC and then resume the mission to go on.

- When I call ATC, always the nearest tower is being called. Despite easy communications is not selected and the proper radio frequency is set. After calling the original tower the nearest tower and the appropriate freq is being set automatically.

 

As already said, help is much appreciated.

 

Just adding this guys response because I'm seeing exactly the same behavior he describes, except for the get data part.

 

I've spent a lot more time with it tonight, and I cannot reliably get selection of atc working. Airfield usually goes to nearest and I've found it nearly impossible to get it to select another airfield. Once or twice it's worked but it seems really sticky and unresponsive when using the 'select' commands. This is in addition to my issues with profile selection. I also see the exact same thing he describes when saying "start mission"

 

The thing I'm starting to question is the version of Voice attack. The install guide says you need the beta, but the version listed is actually lower than the current release version. I'm using 1.5.8, the beta listed on their site is 1.5.8.14 I tried both and the 1.5.8.14 beta doesn't work well at all. It hangs importing profiles and gives errors.

 

I'm wondering if there are any problems running this with the current version. There seems to be no way to download previous versions of voice attack.

[Hollywood_315]

Hi Feisty, Sinball

 

You are using the right VA version i.e. 1.5.8. There's an issue with VA's most recent beta (they're working on it).

Per Kozmyk's suggestion, check which DCS version you are running and adjust the patch (post #1) accordingly:

 

http://forums.eagle.ru/showpost.php?p=2671397&postcount=242

 

If the path is not set correctly, your Easy Communications setting will not get read properly which would lead to the symptoms you're describing.

For instance the Select command for ATC only works in Easy Comms ON mode, see manual.

 

Let me know if this works: if not send me a PM and we'll narrow it down.

Cheers

[FeistyLemur]

I spent a lot of time with it last night and may have it figured out. I just assumed it was automatic but the profile switching appears to require set up. The profile switch commands are kind of a strange mixture spread over the profiles and don't have the actual command in place which has to be added. So I got that fixed and it works well now.

 

I find that calling the profiles as 'aircraft select f15c' for example is really fiddly and problematic. Even when I specifically add "f15c" to the windows speech recognition dictionary and record an example, it doesn't work well. Even when it looks like the unrecognized command should have worked in the monitoring window. Plane designations are just hard to pick up for it when I speak them. I changed them to full simple words and set the appropriate command for the profile to enact. EG instead of MIG21 and KA 50 ( the two profiles I use) I set the suffix to bison and shark respectively. This is much more reliable. All of the profile switch commands had the commands broken. If I had to guess it would be maybe because they were looking for profiles that aren't imported yet as you import the profile itself so perhaps it replaces the command for the profile with an error message and never fixes it unless you do it manually.

 

As for the radio issue. I'm still finding some fiddly behavior with them in certain situations. After reading the manual several times and experimenting I think I fully understand how it works and it does work most of the time. The key mistake I was making was not understanding that the radio has to be tuned to the appropriate airfield, as well as requiring you to call 'airfield ATC select' to change it. I seem to have problems getting nalchik to work. It recognizes the command 'nalchik' ATC select options' but under no circumstances can I ever get it to tune to nalchik yet other than flying close to it and catching it with 'nearest / proxy'

 

For example, in testing last night I was flying the KA-50 towards nalchik in the "cold start in mozdok" mission. As I was flying toward it I set my radio to 136 for nalchik, called nalchik set atc options 20 times, and it would not pick up under any circumstance. However, I set the radio for Minivody, called minivody set atc options, it picked up no problem. Then I swapped back and forth between minivody and mozdok(assistent in ka50) several times, it worked 100% reliably going back and forth between those two. But nalchik, nothing, when I got close enough nalchik became "nearest" then it tuned in and worked. Haven't figured out an explanation for that yet.

 

Other than that remaining quirk I've yet to figure out, everything's working great and I'm really enjoying the program a lot, thanks for creating it.

Edited February 25, 2016 by FeistyLemur

[Hollywood_315]

Ok thanks a lot for the update. I'll send you a PM later with a question or two regarding the Nalchik thing. Appreciate the feedback.

 

Verstuurd vanaf mijn C1905 met Tapatalk

 

EDIT: Issues caused by trying to use SELECT command for ATC in Easy Communications OFF mode. This doesn't work: SELECT command is only available with Easy Communications ON. In addition, specifically for Nalchik airfield a bug was identified, see post below. Thanks @FeistyLemur

Edited February 26, 2016 by Hollywood_315

[Sinball]

I´ve checked my settings and the keybindings in DCS again. There were still some key mappings that need to be removed. I also changed Easy communication to ON. After that, I started a quick flight and obviously it´s working better. At the coming weekend I will check all more in detail.

All I can say now is that the not removed keybindings probably caused the most problems.

[FeistyLemur]

Found the problem.

 

Time for my first bug report. Under "Call ATC' heading, select multipart command "Nalchik*' scroll through the definitions. Nalchik is mistyped as Malchik. It's mis-typed in every one of the profiles.

 

I fixed it in all of the profiles I chose to import and it works good now.

 

Amazing what a monkey wrench a small boy can throw into things when he sneaks into your code isn't it.

[Hollywood_315]

@Feisty Yep, confirmed! Good job on digging this up :thumbup: I will attach a note to first post.

With the snag now out of the way: enjoy VAICOM!

[Hollywood_315]

Hey Hollywood I own the TM Warthog. When I try to map the "push to talk" functionality in your A-10C map and tryin use it in game for some reason it opens external views. It's like pressing F6, F8, etc on the keyboard. I just want to use my TM mic switch to toggle the correct transmissions (VHF/UHF). I've fixed the problem in the F-15 map simply by turning off the conflicting view keyboard commands in DCS. Just want to know if theirs a way to exclusively map the "push to talk" commands to my HOTAS instead of keyboard commands that conflict with DCS.

 

 

Hey dadunn,

 

There seems to be a config problem with your HOTAS: you should not see these view switches.

 

First of all make sure you have followed the steps in the user manual e.g. remove all HOTAS MIC joystick bindings.

It's important that your Warthog sends the emulated keyboard keys using press-and-hold:

I don't know if you use TARGET for this but if you use Autohotkey instead make sure to check out Davisons post

(#2 in this thread) and carefully follow the steps there. Feel free to send me a PM if you need more help with this.

[LuX]

HI

 

Hi, this is my first post on DCS.

Hollywood great work on VAICOM :thumbup:

 

I have only one problem: I start mission via Voice Attack and mission starts, but when I call ATC or request startup it gives me this error:

 

Send commands to: DCSWorld

Key send exception: It appears that the process has been closed

Error acquiring process handle for command "start" (Global Level)

 

If I select: Digital Combat Simulator in send commands menu it gives me Invalid radio.

 

Again great work and keep up, I hope Eagle Dynamics will use your idea (with your agreement) for import this voice control

 

Sorry for bad English

 

Greetings from Croatia

[Hollywood_315]

Hey Lux

 

Thanks man :) Not quite sure what could be causing this error, first time I've heard of this one,

but it may be related to admin settings or VA version or something like that.

Anyway let me send you a PM with some checks to go through and we'll figure it out.

 

Grtz

[LuX]

I have admin rights on Voice (version: 1.5.8)

Windows 10 Pro 64bit

DCS World 1.5.3 (not open beta)

I installed modes manual (backup/copy/paste method)

Voice attack config (like in manual)

keys numpad from 0 to 3 are working

Easy communication is ON

I have screenshots in attachment

[Hollywood_315]

OK can you try and hold the PTT key longer? From the second screenshot it appears you're releasing too soon.

Do not release the PTT key until the command is fully executed i.e. until you've heard the two beeps.

I'll send you a PM with some more checks.

Edited March 1, 2016 by Hollywood_315

[LuX]

Yep is my bad, I did not press key long enough. :pilotfly:

 

Tnx for advice:thumbup:

 

But can you tell me what about radio interaction I mean custom (chatter) voice like from your trailer (voice from tower example)

 

How to activate that voice

[Hollywood_315]

No problem - good we got that solved! :joystick:

You can activate the chatter function by using 'Chatter' voice command, e.g 'Chatter On' or 'Chatter Off',

and also you can use a key for this, NUM. by default.

[LuX]

Again thank you for such great mod, it really gives more simulation to the game.

 

See ya:megalol:

[Bob Denny]

alright just an FYI for everyone.

 

If your voice attack has the lines highlighted in the image below, run voiceattack as an Administrator.

[...etc]

There is another possible reason which I just discovered. If your Windows user name has any spaces in it, the VAICOM_fetch_data.cmd batch script will fail to locate the mission data and give you the same errors as shown i n the image above. Find this cmd file in Program Files (x86)\VoiceAttack\Apps\VAICOM\Tools and change the COPY command to quote the source path

 

COPY /Y "%USERPROFILE%\AppData\Local\Temp\DCS\tempMission.miz" TEMP\tempMission.zip

 

This one took me a while to find. I'm still struggling with VAICOM and will report additional issues as I go. Also sorry I can't figure out how to put uploaded images inline, my editor only offers via URL, and the attachment manager doesn't offer a way to place it except the [noparse][attach][/noparse] BBCode by number as in the quote ?!?!?

Edited March 6, 2016 by Bob Denny

[Bob Denny]

VoiceAttack "Check For Updates"

 

Watch out... if you have the 1.5.8.9 (prerelease) version of VoiceAttack installed, a check for updates will not tell you that the final release is out there. See the attached image for proof. Once you go to the VA site, the production VA 1.5.8 is there.

[Bob Denny]

Made some progress, but it's still acting quacky. Firstly, it seems I have to speak commands one word at a time, watching VoiceAttack out the corner of my eye to see it recognize each word. If I do that, it seems to be recognizing words 100%. If I say the exact thing just a bit faster, the recognition goes to he**. Example "Sukhumi hawg11 [request] start" works every time if I say it one word at a time and the progress in the VA log is good. But just a little faster and it hears goofy stuff like "ciccone hog 11". Miraculously in this example VAICOM figured it out anyway

 

6:13:01 PM - Shortcut : 'Transmit VHF1 pressed'

6:13:01 PM - Listening resumed

6:13:04 PM - Unrecognized : 'ciccone hog 11'

6:13:05 PM - Recognized : 'request start'

6:13:05 PM - Progress status 1/5 (Recipient selected ATC: auto set by context)

6:13:05 PM - Process Status 2/5 Player callsign hawg 11

6:13:05 PM - Progress status 3/5 (command recognized)

6:13:05 PM - Progress status 4/5 (executing)

6:13:05 PM - ATC

6:13:06 PM - Request Startup

6:13:06 PM - Progress status 5/5 (command executed)

6:13:07 PM - Shortcut : 'Transmit VHF1 released'

6:13:07 PM - Listening suspended

 

But at this point, where it seems to be OK, it either causes F9 to be sent out, which is TrackIR's Pause command or more often it leaves the Comm menu visible for Mozdok. Anyway, here it is with each word spoken separately:

 

6:14:04 PM - Shortcut : 'Transmit VHF1 pressed'

6:14:04 PM - Listening resumed

6:14:06 PM - Recognized : 'sukhumi'

6:14:06 PM - Progress status 1/5 (recipient recognized)

6:14:08 PM - Recognized : 'hawg 11'

6:14:08 PM - Process Status 2/5 (player callsign recognized)

6:14:10 PM - Recognized : 'start'

6:14:10 PM - Progress status 1/5 (Recipient selected ATC: auto set by context)

6:14:10 PM - Process Status 2/5 Player callsign hawg 11

6:14:10 PM - Progress status 3/5 (command recognized)

6:14:10 PM - Progress status 4/5 (executing)

6:14:10 PM - ATC

6:14:10 PM - Request Startup

6:14:10 PM - Progress status 5/5 (command executed)

6:14:19 PM - Shortcut : 'Transmit VHF1 released'

6:14:19 PM - Listening suspended

 

looking at the timing you can see the slower pace. In both cases, though, the wrong thing is done even though the right command was executed (request startup) but to no effect in DCS except maybe an F9 or a Mozdok Comm menu (as usual). The radio is on the correct freq for Sukhumi 129.0.

 

As a sanity check, without changing anything, I activated VHF1 for "Options" which causes the Comm menu to appear. Now, while holding the comm button down, I can use the F-keys to select ATC, Nearest, Sukhumi, Request Startup and it executes fine. Why would VAICOM leave me at the Mozdok menu? And what's up with the F9 commands? I've seen F9 appear at other times too.

 

The initial smoke test in the VAICOM manual,. "Chief, ground electric power off" works great. I get a readback, and I don't have to read the stuff word by word.

 

This is a system that runs a great high frame rate, has the Thrustmaster HOTAS Warthog sticks and TrackIR, using a Logitech G430 gaming headset/mic, I have trained voice recognition three passes and I am sure it's for that gaming headset mic as I set it up with a profile to be used with VoiceAttack.

 

Lastly, is there a complete VoiceAttack log somewhere? It looks like I can only get info by select-all/copy out of its window. Is that all there is?

 

I spent 8 hours getting this far (including a 90 min trip to Best Buy for the G430 headset/mic and its installation and firmware update), and I think I am really close.

Edited March 7, 2016 by Bob Denny
Completed the message

[Hollywood_315]

Hey Bob

 

Good to hear you're making progress.

You will need to remove the interfering F9 keyboard hook from your TrackIR config,

i.e. change it to a different key.

 

Airfield names recoginition will improve over time as you use it more,

also you may want to add these to your MS Speech Library.

Feel free to send me a PM if you need help with this.

 

Cheers

[Hollywood_315]

Hey Hollywood, just want to say too thanks for creating this. Ive been using VAICOM for a couple of weeks now and find it great.

 

Quick question though: Im getting an Oculus Rift soon so I want to add my own commands to your profile such as "briefing" to open up the briefing window. Ive tried to add this command but its not working. Just wondering what the general procedure is for adding own commands to your profiles? In the example above im trying to bypass the need to use the mic switch.

 

Hi Precog,

 

Thanks, good to hear!

 

Sure in principle you can add any command you like. Just add it to Special Commands category, or create a new one.

If you add a new voice command you can use it while holding down any VAICOM PTT hotkey.

 

If you want to add new commands to be used specifically without pressing any PTT key at all you will have to use a VoiceAttack trick:

 

In Profile options, there's the 'Override listening if my spoken command begins with...' option.

If you add a word there for example 'computer', you could say 'Computer, Briefing' without any PTT keypress.

 

Grtz

[Mick F]

How does VAICOM work with F10 options? If it best just to give the "options" command and work with F-keys from there?

[Kozmyk]

I have TrIR commands moved to:

Centre on a Joystick Button.

Pause on Alt+ F9

Precision on Alt +F10

 

Keeps it all nicely out of the way of DCS.

[Bob Denny]

Hey Hollywood, did you happen to see my post about the VAICOM_fetch_data.cmd script? It seems like a bug.

 

And Kozmyk, great idea (though I already had moved the centre to the joystick paddle). I just made the change. Thank you.

Edited March 7, 2016 by Bob Denny
add note to Kozmik