VAICOM 2.0 for VoiceAttack

[Kozmyk]

HOTAS PTT

 

Excellent work chaps.

 

VA Gary is a top man isn't he. :thumbup:

Always so helpful.

[GregP]

AWESOME! What a great addition to this already wonderful program. And Hollywood, thanks for the detailed instructions.

[CrackerJack]

I'm setting up the PTT as per your instructions. I'm not aware of the check box you are referencing when you say:

 

*) 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.

 

I don't see a check box labeled 'shortcut is invoked only when all buttons are released'??

[Hollywood_315]

Hey Jack,

 

Did you update VA to 1.5.8.17 beta?

The checkbox is at the bottom of the Select Joystick Buttons window, where you assign the joystick button press.

 

Verstuurd vanaf mijn GT-P7300 met Tapatalk

[CrackerJack]

Thanks I didn't have the Beta installed just the updated release. Its all good, cheers!

[NatoBoomerang]

Hey Guys - I just downloaded the trail version of Voice attack...but none of the options are highlighted. I can't import the F-15C profile, I have added the Viacom 2 folder to VoiceAttack\Apps...do I need to buy the full version for Voice Attack to add the profile?

[NatoBoomerang]

Hey Guys - I just downloaded the trail version of Voice attack...but none of the options are highlighted. I can't import the F-15C profile, I have added the Viacom 2 folder to VoiceAttack\Apps...do I need to buy the full version for Voice Attack to add the profile?

 

Ok, so I need to purchase a Key for Voice Attack...now the option Add a profile is available, but NEW Problem as per be attached...any help please guys...

 

Win 7 HE with Voice Attack v1.5.8.18, I have added Viacom 2 added as per the following file structure VoiceAttack\Apps\VIACOM

 

I am getting the following Error when attempting to import either the A10C or F15C profile...there was an error reflecting type "VoiceAttack.Profile"

 

I am stuck as to how to proceed...can anyone help please?

 

thank you.

[Hollywood_315]

Hi,

 

I confirm the Import Profile issue in current beta (.17).

Reported to VoiceAttack Support, I expect they will address this soon.

Note: this affects import of new profiles only, existing ones run ok.

 

In the meantime can you download 1.5.8 release version and try

getting started with that for now.

 

I'll update when I have more news.

 

Thanks

Edited May 2, 2016 by Hollywood_315

[Kozmyk]

Hi,

 

I confirm the Import Profile issue in current beta (.17 /.18 ).

Reported to VoiceAttack Support, I expect they will address this soon.

Note: this affects import of new profiles only, existing ones run ok.

 

In the meantime can you download 1.5.8 release version and try

getting started with that for now.

 

I'll update when I have more news.

 

Thanks

I had a problem exporting .vap files in 1.5.8.17

I reported to Gary and he fixed it in no time.

1.5.8.18 Exports and Imports fine for me

[Hollywood_315]

Thanks Kozmyk,

 

Same for me actually.

I can reproduce this error in 1.5.8.17 beta, but in 1.5.8.18 beta this seems to have been fixed already.

 

@NatoBoomerang can you double-check that you are running .18 and not .17?

Version .18 should be ok. Thanks.

[NatoBoomerang]

Hey Hollywood, updated to .18 Beta and I am now able to load the F15 profile...now, I'm following your instructions to get it all setup, fingers crossed!

 

Thx!

[Nicolai]

Hey Hollywood

 

First of all thank you for this amazing enhancement to DCS.

I think everyone who has fiddled around with Voice Attack can appreciate the massive amount of work that has gone into Vaicom.

 

I have been messing around with Vaicom for a few weeks and have unfortunately encountered most of the common problems.

However, after combing through this thread and the manual numerous times I have been able to solve most of them. I strongly urge other users to read this thread thorougly before complaining about this and that. They will most likely find the answer there.

 

These are the problems I've had:

-The URI error.....Fixed. I'm on 1.5b and corrected the cmd.

-Invalid radio.....Fixed. I had originally dowloaded the latest VA beta. Re-installing the current release version solved that problem.

-Auto hotkey PTT....Never really got that working, but fortunately the latest VA release makes this irrelevant.

-TrackIR interference.....Fixed. I have deleted and/or changed every possible key command I can think of that might screw up Vaicom.

-Non-US international keyboard....Fixed (I think ). I have re-assigned "\" to OEM102 in both DCS and the two lines in Menu_Execute.

 

However.....after all this I am still not able to get it to to work properly

The time has come to ask for help.

 

1) I'm stuck with the changing-to-external-view-problem

My voice commands are recognized in VA, but not in DCS (at least not in the way they are supposed to be recognized)

-Yes, I am using Whartsell's VAC ATC Menu Mod 1.0 via JSGME

-Yes, I am holding the PTT-key until the command is properly recognized.

No response from ATC....just the changing of view.

I have read somewhere that double clicking recognized commands in the VA log should display the actual command sent to DCS, thereby enabling me to analyzed/troubleshoot. However, I get nothing when i double click.

 

2) My PTT press and release does not work on my TMWH. I use button no. 1 on the stick.

I suspect this is due to the fact that I am currently on the VA 1.5.8 which for some reason does not have the tick box 'shortcut is invoked....'

Installing the beta version could supposedly solve this, but as mentioned earlier, I've had more serious problems with the beta and apparently I am not the only one.

For now I am stuck using the NUM1 mapped to my Tartarus as PTT.

 

A little general info on my setup:

-TMWH extended stick (no active Target profile)

-X55 Rhino Throttle (no active HUD profile)

-Saitek Combat Rudder Pedals

-TrackIR5

-Razer Tartarus

-DK keyboard

-DCS 1.5b (and 2.0a but I haven't even started to work on that)

-JSGME 2.6.0.157

-VA 1.5.8

-Vaicom 2.0

-UH-1H Vaicom profile

 

 

Your help is greatly appreciated

 

//Nic

Edited May 22, 2016 by Nicolai

[Hollywood_315]

Hey Nic

 

Thanks! Good to hear you appreciate VAICOM.

 

Yep during stetup you can come across some potential snags and indeed it seems you covered just about all of them :)

Can be a bit of a pain but the rewards are high once you get things working properly. So let's have a look.

 

*) The one thing I don't see mentioned is that VA must run as Administrator. But I assume you have that covered.

*) For VA I recommend upgrading to 1.5.8.18 beta version. It is stable and gives you the option to set up your TMWH HOTAS

button presses directly for PTT, which is a much cleaner way of doing things than via keyboard emulation.

Of course if you prefer release version 1.5.8 with the Tartarus for now then that's fine too.

*) For this one:

I'm stuck with the changing-to-external-view-problem

 

It could have to do with VA not running as admin but more likely it is related to the Non-US International keyboard i.e. the OEM102 setup.

This can be tricky to get right, even though you seem to have followed the correct steps.

VA must send the same key as is used in DCS config and keyboard mapping mismatch can screw this up.

Let me send you a PM and we'll get it out of the way :joystick:

 

Grtz

[Hollywood_315]

Hey Hollywood.

Are you going to create a Module for this great program for use in the SA342 Gazelle? I really hope so.

 

Cheers

SD

 

Hey SD

Sure, sounds like a good plan to me. I'll put it on the list for when funding is available.

For now I have planned to look into the L-39 first.

Grtz

[pepin1234]

This work with Mig-29 versions?

[Hollywood_315]

This work with Mig-29 versions?

There's no specific VAICOM profile for MIG-29 at this time, but you can try with using the SU-27 profile. There's a good chance that it will work.

 

Verstuurd vanaf mijn SM-G935F met Tapatalk

[tribundf]

Hey guys,

 

I have to say this mod is incredible. Takes some getting use to for sure but a great tool to have.

 

 

How is it possible to talk to a different ATC in Nevada. The ATC mod. I installed, removed all the names...

Edited June 14, 2016 by tribundf

[Hollywood_315]

Hey guys,

 

I have to say this mod is incredible. Takes some getting use to for sure but a great tool to have.

 

 

How is it possible to talk to a different ATC in Nevada. The ATC mod. I installed, removed all the names...

 

Thanks for the comment!

Whartsell's Static ATC mod is not yet compatible with 2.0 / Nevada at this time.

If the situation changes I'll make sure to let you know, updates via this thread: http://forums.eagle.ru/showthread.php?t=138994

[tribundf]

Thanks Hollywood!

 

Yeah I found that post too. No worries, I think using the nearest airport works just fine for now.

[Dazven]

Loving this so far, but is the SU-27 profile cross compatible with the SU-33?

[Hollywood_315]

Should be the case I believe, but I didn't test it myself.

Send me a PM if you encounter any issues.

Cheers

[x39crazy]

Any of the current profiles work for the Kurfurst or Dora?

[Captain Orso]

Hi Hollywood,

 

I cannot get this to work. In the VA window, if I switch out from DCS, I can see that VA recognizes what I've said, but DCS still doesn't open the COMM's menu to do anything that I can recognize. Also, after ever time I PTT and issue a command, when I check VA, I see the command was recognize, and it states 'Invalid radio'.

 

I have VA 1.5.8.29 Beta installed, because the 1.5.8 GA version doesn't have the 'shortcut is invoked only when all buttons are released' setting for HOTAS PTT, or at least I couldn't find it. I've copied the VIACOM2 base and VIACOM2 P-51D packages into 'c:\Program Files (x86)\VoiceAttack\Apps\'.

 

I haven't installed the Hide COMM's Menu, nor the No Player Voice mods yet; only the Static ATC mod via JSGME, because I wanted to hear and see things work first.

 

Oh, and I edited the 'VAICOM_fetch_data.cmd' vor 1.5 Beta, because that's what I'm running. The cmd file works too, because I've switched out of DCS and seen the mission files copied into the ..\TEMP folder.

 

After looking through this thread for 'invalid radio' I suspect the issue may have to do with my keyboard--I have a German keyboard. I've tried both the 'System Default' and 'German-Germany' settings in VA, but with the exact same results.

 

Any ideas?

[MrMgrMatt]

Hi Hollywood,

First off, I want to thank you for creating this. The depth is amazing. This is mandatory when playing in VR, not to mention substantially increasing the immersion factor. :-)

 

I have a suggestion that I have implemented in my own profile that others may find useful.

1. For the F10 Aux commands, to help it be more of a catch-all, I duplicated and edited the "proceed" command into 5 different commands:

*menu* - Removed top 5 lines

*alpha* - Removed top 5 lines; Changed Set text command from 'proceed' to 'alpha'. Removed Execute command, '_Menu_Execute_Aux' (and wait until it completes)

*bravo* , *charlie* , *delta* , *correction* - set each of these up like alpha, but changed the key press from F1 to F2 for bravo, f3 for charlie, f4 for delta, f11 for correction.

 

Below is a sample interaction with the above:

<hold hot mic>

Speak "Mystery menu"

{F10 menu pops up on screen}

If you want option 2, speak "Bravo"

{Vaicom simulates F2 press, menu reflects F2 press and remains displayed}

You were wrong, you really wanted option 3; Speak "correction charlie"

{Vaicom simulates F11, F3; Menu reflects the presses and remains displayed}

You want option 1 of this submenu, which ends up being the final choice "Speak Alpha"

{Vaicom simulates F1; Comms menu disappears as it normally would when you hit a final command option}

</release hot mic>

 

 

With that being suggested, I have ran into an actual issue though too. Some of the missions I play have 2 tankers (S-3B "Arco" for the fast movers and KC-135 "Texaco" for us who play in the dirt), but the current script assumes 1 tanker only and always stops short, usually on the wrong tanker.

 

Single Tanker Comms Flow; Initial refuel request

HM, F6 for Tanker(s), F1 for rejoin.

 

Multiple Tanker Comms Flow; Initial refuel request

HM, F6 for Tanker(s), {F1, F2 ... or F6} to select the appropriate tanker, F1 for rejoin.

 

Are there any changes that can be made that will work for single and dual tanker missions? My first thought is a mod similar to the ATC mod that will always list all tankers in a specific order, but I hope that you (or someone else here) knows of an easier way.

[Hollywood_315]

Hey guys

 

@x39crazy I haven't tested this myself but you could try if the P-51D profile works for those modules.

 

@Orso Invalid Radio is sometimes caused by releasing PTT too soon, i.e. make sure you hold it long enough until you've heard the beeps,

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

 

@MrMgrMatt Great suggestion on the Aux menu, this has been a somewhat unprioritized area in VAICOM.

I recommend everyone who often makes use of the Mystery callsign to follow your steps :thumbup:

 

Regarding the multiple tankers etc. that's certainly on the list for a future update version. What would be great to have to enable this is a universal comms menu-reordering mod that would not just sort ATCs submenu but also JTACs tankers, AWACS etc. by callsign name. As far as I know such a mod is not out there yet but hopefully Wartsell or others will feel inspired to get such a tweak in place sometime soon.

Edited July 4, 2016 by Hollywood_315