VAICOM 2.0 for VoiceAttack

[Hollywood_315]

@Shaz PM sent.

[shaz56]

hollywood thanks for quick reply. yes i have tried the "field" method, get the same result. also spent most of Sunday teaching speech recog.I'll do as you suggest and set back to false. It does recognise airfields if i try voice attack on it's own but not in game. I do find i have to slow down my normal speech (strong west country accent, UK) for it to respond. wingmen orders and atc on the ground working fine. Any idea's on why it would be changing my view sometimes ?

[shaz56]

just tried again, in the log the airfield (any) is recognised as is "select" but immediately after that has a red dot saying "incomplete command" !!!!!

I thought "airfield name" and "select" was all I had to say so how is it incomplete ?

[shaz56]

my latest log, heads buzzing, getting late, giving up on life, going to bed. won't be able to sleep coz can't switch off until sorted. OH the despair, LOL.

 

00:02:26 - Listening suspended

00:02:26 - Shortcut : 'Transmit VHF1 released'

00:02:25 - Progress status 5/5 (command executed)

00:02:25 - Select

00:02:25 - Progress status 4/5 (executing)

00:02:25 - Progress status 3/5 (command recognized)

00:02:24 - Recognized : 'select'

00:02:23 - Progress status 1/5 (recipient recognized)

00:02:23 - Recognized : 'mozdok'

00:02:22 - Listening resumed

00:02:21 - Shortcut : 'Transmit VHF1 pressed'

00:02:21 - Listening suspended

00:02:20 - Incomplete command

00:02:20 - Shortcut : 'Transmit VHF1 released'

00:02:19 - Recipient Error

00:02:19 - Progress status 1/5 (recipient recognized)

00:02:18 - Recognized : 'mozdok select' (ends with 'select')

00:02:18 - Recognized : 'mozdok select' (starts with 'mozdok')

00:02:16 - Listening resumed

00:02:16 - Shortcut : 'Transmit VHF1 pressed'

00:02:15 - Listening suspended

00:02:15 - Incomplete command

00:02:15 - Shortcut : 'Transmit VHF1 released'

00:02:11 - Recipient Error

00:02:11 - Progress status 1/5 (recipient recognized)

00:02:10 - Recognized : 'mozdok select' (ends with 'select')

00:02:10 - Recognized : 'mozdok select' (starts with 'mozdok')

00:02:07 - Listening resumed

00:02:07 - Shortcut : 'Transmit VHF1 pressed'

00:02:01 - Listening suspended

00:02:01 - Incomplete command

00:02:01 - Shortcut : 'Transmit VHF1 released'

00:02:00 - Progress status 1/5 (recipient recognized)

00:02:00 - Recognized : 'mozdok'

00:01:58 - Listening resumed

00:01:58 - Shortcut : 'Transmit VHF1 pressed'

00:01:33 - Listening suspended

00:01:32 - Shortcut : 'Transmit VHF1 released'

00:01:30 - Progress status 5/5 (command executed)

00:01:30 - Select

00:01:30 - Progress status 4/5 (executing)

00:01:30 - Progress status 3/5 (command recognized)

00:01:30 - Recognized : 'select'

00:01:28 - Progress status 1/5 (recipient recognized)

00:01:28 - Recognized : 'nalchik'

00:01:26 - Listening resumed

00:01:26 - Shortcut : 'Transmit VHF1 pressed'

00:01:20 - Listening suspended

00:01:19 - Shortcut : 'Transmit VHF1 released'

00:01:15 - Progress status 5/5 (command executed)

00:01:15 - Select

00:01:15 - Progress status 4/5 (executing)

00:01:15 - Progress status 3/5 (command recognized)

00:01:15 - Recognized : 'select'

00:01:13 - Progress status 1/5 (recipient recognized)

00:01:13 - Recognized : 'field 21'

00:01:11 - Listening resumed

00:01:10 - Shortcut : 'Transmit VHF1 pressed'

00:01:08 - Listening suspended

00:01:08 - Shortcut : 'Transmit VHF1 released'

00:01:06 - Invalid Radio

00:01:06 - Recognized : 'pincer high'

00:01:04 - Listening resumed

00:01:04 - Shortcut : 'Transmit VHF1 pressed'

00:00:45 - Listening suspended

00:00:45 - Shortcut : 'Transmit AUTO released'

00:00:43 - Progress status 5/5 (command executed)

00:00:43 - Select

00:00:43 - Progress status 4/5 (executing)

00:00:43 - Progress status 3/5 (command recognized)

00:00:42 - Recognized : 'select'

00:00:42 - Progress status 1/5 (recipient recognized)

00:00:41 - Recognized : 'mozdok'

00:00:40 - Listening resumed

00:00:39 - Shortcut : 'Transmit AUTO pressed'

00:00:34 - Listening suspended

00:00:34 - Shortcut : 'Transmit VHF1 released'

00:00:30 - Recipient Error

00:00:30 - Recognized : 'select'

00:00:27 - Listening resumed

00:00:27 - Shortcut : 'Transmit VHF1 pressed'

00:00:23 - Listening suspended

00:00:22 - Shortcut : 'Transmit VHF1 released'

00:00:19 - Progress status 5/5 (command executed)

00:00:19 - Select

00:00:19 - Progress status 4/5 (executing)

00:00:19 - Progress status 3/5 (command recognized)

00:00:19 - Recognized : 'select'

00:00:18 - Progress status 1/5 (recipient recognized)

00:00:18 - Recognized : 'anapa'

00:00:15 - Listening resumed

00:00:15 - Shortcut : 'Transmit VHF1 pressed'

00:00:13 - Listening suspended

00:00:13 - Incomplete command

00:00:12 - Shortcut : 'Transmit VHF1 released'

00:00:11 - Recipient Error

00:00:11 - Progress status 1/5 (recipient recognized)

00:00:11 - Recognized : 'Sochi select' (ends with 'select')

00:00:11 - Recognized : 'Sochi select' (starts with 'sochi')

00:00:08 - Listening resumed

00:00:08 - Shortcut : 'Transmit VHF1 pressed'

Edited December 10, 2015 by shaz56
forgot header

[Hollywood_315]

Hey Shaz. What will solve your problem is to state the call as two individual words with very small pause in between, as in 'Sochi. Select.'.

 

Will investigate, there's apparently some kind of snag when this command is spoken in one go.

BTW as I'm sure you are aware in VA options you can select the Speech Recognition engine to UK English instead of US English.

Good to cover for strong west country or Dutch accents lol

Edited December 10, 2015 by Hollywood_315

[shaz56]

hollywood, thanks again for your reply. yup the last two tips I have covered already, the software as a whole seems to be working so i'm hoping the more i use the better it will respond. Lately i have spent more time flaffing about setting things up rather than flying so i'll just continue to plug away. thanks again for all your help. Great work by the way. Next it'll have to be implemented for Arma 3, that has serious F menu issues as well, anyways "to the stars and beyond", LOL

[nigelmcelwee]

will this be updated with the new Nevada airfields too? I got it working in 2.0 but instead of saying nellis, I just say ATC. Also, 2.0 some of the commands are going through (double beep) but the AI dont comply. Like "flight...wedge" I hear the double beep but my flight doesnt say confirm or roger. But if I use the keyboard shortcuts, they do.

[Hollywood_315]

@Shaz per ardua ad astra - cheers

 

@Nigel, yes Nevada is going to be supported, I'm in touch with Whartsell (ATC mod) on this. With current 2.0alpha I have the same experience as you i.e. not all commands getting proper replies from AI. It seems in 2.0a this menu stuff is not all implemented yet by ED and is still in the works. What I have seen working so far though all looked fine. The Nevada airfield names list appears not yet in the menu so we may have to wait a bit more until next (beta) release until we can get it in place.

[nigelmcelwee]

@Shaz per ardua ad astra - cheers

 

@Nigel, yes Nevada is going to be supported, I'm in touch with Whartsell (ATC mod) on this. With current 2.0alpha I have the same experience as you i.e. not all commands getting proper replies from AI. It seems in 2.0a this menu stuff is not all implemented yet by ED and is still in the works. What I have seen working so far though all looked fine. The Nevada airfield names list appears not yet in the menu so we may have to wait a bit more until next (beta) release until we can get it in place.

 

Yeah ,I hear there is a whole new ATC system in the works so it might offer up some drastic changes to VAICOM! Looking forward to seeing this new ATC system.

[Dunravin]

Thanks for this awesome mod. I suspected voice attack was capable of much more than I could ever make it do.

 

Tested VAICOM 2.0 for Ka-50 on the 1.5 Open Beta | Easy Comms Off | G940 Stick button 4 mapped with AHK | Non US international keyboard | No issues after RTFM.

 

Regards

 

Dunravin'

[Hollywood_315]

--- NEW MODULE AVAILABLE: F-86F ---

 

--- NEW MODULE AVAILABLE: F-86F ---

 

I'm happy that today we are adding the popular F-86F Sabre to the list of VAICOM modules!

 

Download the VAICOM 2.0 profile for the F-86F here:

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

 

Enjoy!

Hollywood

[the_soupdragon]

oooh nearly missed this. Great stuff. Nearly all modules catered for now. Great work. Thanks Hollywood.

 

SD

[BaD CrC]

Hi Guys,

 

Can you please help a complete Vaicom 2.0 noob?

 

So I purchased and installed Voiceattack 1.5.8 (and did the training)

Yes, I set Windows 10 and my keyboard in English (although physically it's French)

I downloaded the latest Vaicom 2.0 and Ka-50 profile.

I downloaded the static atc mod and installed it with JSGME (don't know how it is suppose to look like in game though)

I dropped the VAICOM directory in apps directory and dropped the Ka-50 profile into the Profiles directory of VAICOM

I imported the Ka-50 profile into Voiceattack

Set voice attack with the recommended settings in the Vaicom manual

Ask Voice attack to use Ka-50 profile and send commands to DCS

Voice attack recognizes alright what I am saying but it always ends up with a "Invalid Radio" and nothing is happening in the sim.

What did I do wrong?

[HiWay]

Did you start with start mission command instead of press fly button?

[Hollywood_315]

Hey BaD CrC,

 

Couple of things to check

 

- Windows 10: make sure you run VA explicitly as administrator

- Doublecheck the physical key for comms menu both in DCS config and in VAICOM profile (see the note on non-US keyboards)

- Use Start Mission voice command to start each new mission (this loads the DCS settings such as for Easy Communication, see manual)

- If you run 1.5ob check the note on that

- Do not release the PTT key too soon, i.e. wait until you've heard the beeps.

 

Have a look and send me a PM if you get stuck on anything.

[Kozmyk]

Great Mod.

I struggled with it for a couple of days but it's starting to obey me now.:thumbup:

A lot was to do with me not holding PTT long enough.

 

One thing I DID notice was that Call Sign numbers weren't being recognised reliably.

Saying "Enfield One One" wasn't working but "Enfield Eleven" DID

 

I went and edited all the Call Sign commands to include a space and they work fine now.

i.e. *Enfield 1 1* instead of the original *Enfield 11*

 

I just have to program myself now with the usage syntax...

With my brain, that'll be the hard part.:pilotfly:

[Dachs]

Just started using VAICOM and Voiceattack, and its looking good so far.

Just have to get used to the syntax, but everything is working it seems.

Thank you for making this Hollywood, it must have been pretty time consuming!

 

And a tip for those using the .ahk script for their joysticks;

I've changed the .ahk script to use the "hidden" F keys. I think it's something I picked up from one of PeterP's posts, but I'm not sure.

Anyway, you can use keys from F13 through to F24, even though your physical keyboard only have F1 to F12.

This way you won't have any conflicts in DCS what so ever.

 

Edited .ahk file in spoiler tags:

 

 

 

; -- Chatter ON/OFF --

 

2Joy2::

Send {F16}

Return

 

; -- PTT buttons --

 

2Joy3::

Send {F17 down}

KeyWait 2Joy3

Send {F17 up}

return

 

2Joy4::

Send {F18 down}

KeyWait 2Joy4

Send {F18 up}

return

 

2Joy5::

Send {F19 down}

KeyWait 2Joy5

Send {F19 up}

return

 

2Joy6::

Send {F20 down}

KeyWait 2Joy6

Send {F20 up}

return

 

 

[BaD CrC]

Hey BaD CrC,

 

Couple of things to check

 

- Windows 10: make sure you run VA explicitly as administrator

- Doublecheck the physical key for comms menu both in DCS config and in VAICOM profile (see the note on non-US keyboards)

- Use Start Mission voice command to start each new mission (this loads the DCS settings such as for Easy Communication, see manual)

- If you run 1.5ob check the note on that

- Do not release the PTT key too soon, i.e. wait until you've heard the beeps.

 

Have a look and send me a PM if you get stuck on anything.

 

Thanks guys for your good tips. But still no go. Hollywood, incoming MP.

[eric963]

Dachs,

 

Do I need to make any other changes in the VAICOM scripts?

 

Thanks

Eric

[whiteside]

I watched Froogles video, set up a few commands and then abandoned it. Totally awesome software for this sim!

 

I downloaded VIACOM 2.0 installed it and now trying to get it to recocnise my voice to give a command but the Comm menu wont come up. What am I doing wrong?

Do I have to hit a button to activate it in DCS?

Edited December 21, 2015 by whiteside

[whiteside]

I can make my own profile work but not the viacom profile. Any ideas?

[Hollywood_315]

Hi Guys

 

Thank you all for your generous comments and feedback. Appreciated!

 

@Bad CrC Reply PM sent

@whiteside with VAICOM you don't wait for any menus to appear. I'll PM you with some tips.

[Dachs]

Hm, I've run in to quite a lot of recognition problems sadly.. A lot of goat trails instead of go trail and for instead of four, to instead of two and so on.

 

I don't remember having these problems using DWVAC, but maybe it's better at making intelligent guestimates of what the bozo behind the mic actually wants?

I've done alot of training, both using wordpad, correcting the offending words, and reading the MS training. In Wordpad I get the same problems, mixing up four and for and so on..

 

Mic level is fine, and a recording of myself is perfectly clear, without any noise.

A bit bummed about it, as the VAICOM way of doing things, are really neat and immersive, but it looks like I'm going back to DWVAC and my simple profile, if can't get this to work a bit better.

Any ideas out there?

[Hollywood_315]

Hey Dachs

 

- Hitrates will improve if you use it more,

- Also you can use the Speech Dictionary to increase your recognition rates: http://forums.eagle.ru/showpost.php?p=2552047&postcount=90

 

Cheers

[Dachs]

Yeah, I'm not giving up on it just yet!

Noticed I didn't run VA as admin, I think that helped a good bit.

Only tried it in DCS with a two-ship flight so far, but it recognized two reliably now. Think I will have a good long deep conversation with my computer tonight, then we'll see :director:

 

Already did the Speech Dictionary thing with four/for, but it didn't have much effect. I suspect my four simply dosen't have enough twang in it, for lack of a better term.

When I count one-two-three-four-five-etc it works like a charm, but used in a sentence it always chooses for.