VAICOM PRO plugin for VoiceAttack

[Greyman]

Not at my PC atm, but as there is a control bindings hierarchy, where at least general and UI take precedence over any aircraft mappings, maybe check if you can bind the map control to something other than F10.

 

I'd guess not, but maybe worth a look.

 

Edit: it looks like you can display the F10 map with a key other than F10. who'd have thought it?

Just go to the General tab, in the first drop down list on the Controls dialogue and search for "map". You should find a row for F10 Theater Map view, which will have F10 as its keyboard mapping. Just clear that and select another key or switch and your F10 binding in your aircraft should now work.

Edited October 15, 2019 by Greyman

[MAXsenna]

See that's my problem though , I have made individual commands for the things like flaps up/down, brakes , speedbrake etc. and imported to Vaicom profile. The ONLY one keybond i cannot get to work is the F10 key (whatever it is bound to ) so far i have tried space, \, `, and lctr + ralt + f12. All of them behave as if i have pressed nothing (but only for the f10 menu) if i add commands after it such as press f10 whilst IN the comm menu , it just brings up the map.

 

I will try yours out tonight and see if i get any luck,

 

Thanks.

 

This part of your comment intrigues me, how was/is this done???

 

"and made it available inside the VAICOM PRO profile."

 

Here. You just edit VAICOM profile and select "Options", and then you can select other profiles.

 

 

But it didn't work. At least not for me. It works in the original profile of course, but not through VAICOM. I guess it has something to do with how VAICOM controls that menu.

[bradleyjs]

Is there a way to turn the chatter off, I though there was simple way to do this but I cant find it.

 

Yes there is. Just press the default button that controls the chatter. On my TM HOTAS, it is the mic button depress. It toggles On/Off.

[MAXsenna]

Okay, I deleted my previous post because I suddenly noticed that I had clicked on the "headset icon", and was not using any TX button, and thus had a false positive. :(

 

So I edited and added some commands. Turned off "headset", and used TX1 button.

And it does work! :D

 

This is how I did it:

 

Made a standalone profile, and parsed it into the VAICOM profile, only using the "Options" button on top when editing VAICOM profile, without ANY other editing of or importing into the original VAICOM profile.

 

Now, I was writing a long piece, but I got seriously confused when I noticed that VoiceAttack, at least on my computer, are not using the same slash key. At least the graphics of it. VoiceAttack shows me using Forward Slash, but ED is using Backwards Slash...

Anyway

When i test this in the F-5E, the radio button on the throttle quadrant is happily clicking away through the menu. I don't think timings are important here.

The key combination is the "Right Alt + /" in the VoiceAttack profile, but "Right Alt + ", in DCS Controls Setup.

Now that said. I do not have any special "Menu Commands", so I have no idea if it will work for others.

I also tested in in the F-16C. After a few tries it worked, but it was very buggy, and sent me to external views all over the place.

Then I tested in the Ka-50, but it doesn't have transmit switch , and was only set up with the default "Menu Command", \ key. Changed it to "Right Alt + ", and it worked but a little behaviour like the F-16C, so timings might be important after all.

 

But I got this to work with "Single TX" setup in VAICOM. And that was the goal. Might do some tuning later, if any questions feel free to ask. :thumbup:

 

EDIT: For some reason the \ and / keys disappears som places in this post.

Edited October 15, 2019 by MAXsenna

[Badass1982]

Tried all that still doesn't work for me, I can either leave it listening all the time by making sure the red Cross is not on the headphone icon. Or use push to talk and have it not work .

[Badass1982]

How can it be that only one command (despite trying different keys) won't work.

[Greyman]

Perhaps check that those keys are not bound to a command that is higher in the DCS hierarchy, as I said in my post above. Any bindings in General or UI layer will override anything that you bind in the aircraft controls

[Badass1982]

Nope they are completely unbound until I bind them of course.

[bradleyjs]

Wow! It seems like I opened a can of worms here! LOL

 

Anyway, I’m guessing that the issues that we’re experiencing will be solved in the coming months from either DCS and/or VAICOM.

 

So, hopefully the information provided here can assist it’s that. I’m available for testing if needed...

[Hollywood_315]

Hi guys

 

Ok not sure I could entirely follow the last pieces of this thread, but in any case in relation to the plugin and the Viper module:

 

- The greyed-out VHF radio (and consequently missing squelch and beep sounds, etc.) is caused by seemingly inaccurate values returned by the sim related to the Viper VHF radio device on/off state,

- This seems simply an EA loose end which in all likelyhood will be ironed out by ED at some point,

- Just in case I added a report in the viper forum section: https://forums.eagle.ru/showthread.php?t=252665

- Let's see if this leads to follow-up by ED dev. which should resolve the issue for VAICOM PRO users,

- Only if no fix by ED is implemented, ad-hoc workaround patches in the plugin may be considered for the Viper,

- For other modules there is no issue.

 

Thanks,

Hollywood

[MAXsenna]

Hi guys

 

Ok not sure I could entirely follow the last pieces of this thread, but in any case in relation to the plugin and the Viper module:

 

- The greyed-out VHF radio (and consequently missing squelch and beep sounds, etc.) is caused by seemingly inaccurate values returned by the sim related to the Viper VHF radio device on/off state,

- This seems simply an EA loose end which in all likelyhood will be ironed out by ED at some point,

- Just in case I added a report in the viper forum section: https://forums.eagle.ru/showthread.php?t=252665

- Let's see if this leads to follow-up by ED dev. which should resolve the issue for VAICOM PRO users,

- Only if no fix by ED is implemented, ad-hoc workaround patches in the plugin may be considered for the Viper,

- For other modules there is no issue.

 

Thanks,

Hollywood

 

Yeah, thanks Hollywood!

Saw your post.

 

For above discussion, some users have a problem with using a single TX button to get custom communication items to work.

[Hollywood_315]

Ah ok thanks.

For using a single PTT button for all modules, use the selector to set PTT mode to SNGL.

This controls mic listen on/off states as normal.

Hope it helps, grtz

[Badass1982]

In reply to Hollywood, mind you it works fine using the way u implemented it in saying things like options, take f12 for example but if we want to add specific commands to say do a bunch of comm menu commands at consecutively for some reason va/Vaicom Pro won't recognize our menu command example as follows

 

One command that is set up such as:

 

When I say

 

"Fighter Support" <<< my custom comm menu command.

 

Press "/" to get Into the comm menu <<<< this is the command that doesn't work no matter what you map it too.

 

Press "F1" to select whatever option

 

Press "F2" to select whatever option.

 

Not sure if it's a DCS issue or VA or VAICOM but I can't figure it out , thanks for all your hard work Hollywood, and the other guys in here helping out.

Edited October 16, 2019 by Badass1982
Backslash isn't showing up in the forums for some reason

[Hollywood_315]

@Badass Right- not exactly sure though why you'd want to create such a custom command:

 

- All standard commands found in the menus are already available in the plugin keyword set,

- You can use the Import F10 Menu feature to add any non-standard menu commands,

- The options/take commands are there to navigate the menus if all else fails.

 

That said if you must, you may have some success by sending the '/' keystroke twice instead of once.

Grtz

[jameslockridge]

As for the tanker issues u guys are having , try this : say exactly "shell approaching for refueling" with a small pause after the shell. Repeat for Texaco and or Arco, I was having loads of issues with this until I said this exact phrase

 

 

I tried this exactly as suggested but still can not get the tanker to answer me.

[dburne]

Ah ok thanks.

For using a single PTT button for all modules, use the selector to set PTT mode to SNGL.

This controls mic listen on/off states as normal.

Hope it helps, grtz

 

Hollywood,

Just an fyi I gave this a try just to check out, setting it to SNGL, and voice attack closes during my flights with it set this way.

No problem with it set to NORM.

[MAXsenna]

@Badass Right- not exactly sure though why you'd want to create such a custom command:

 

- All standard commands found in the menus are already available in the plugin keyword set,

- You can use the Import F10 Menu feature to add any non-standard menu commands,

- The options/take commands are there to navigate the menus if all else fails.

 

That said if you must, you may have some success by sending the '/' keystroke twice instead of once.

Grtz

 

@ Hollywood Thanks for the feedback!

 

Damn, I forgot to about the double "//". I just remember that sometimes outside VAICOM I had to press it twice on the keyboard to get the menu. AND it started to work in my test when I set the keypress to 0,5 seconds.

 

@ Hollywood

Do you know why VoiceAttack uses the the forward slash while DCS uses the backward slash, and it still works?

 

At least it's seems to be like this in my setup.

[Badass1982]

So to answer hollywoods question, I'm not sure exactly how the import f10 menu works (other than what he mentioned above) but I have never been able to get the menu to work by saying anything other than (in this order)

 

1 Options, 2 Whatever option you want e.g. flight but say the f number or "take" then the number

 

However if i dont want to have to say all those commands to get to say the 5th or 6th nested option in the comm menu I tried to create my own voice attack command to do all the commands for me when i say one phrase:

 

So if i have a custom command that reads as the following:

 

when i say Voice command "Fighter Support Sorii"

 

1: press "" (Which is the open comm menu keybind)

2: press"f10" (which is "F10.other" in the comm menu)

3. press "F1" (which is "F1.Request Support in the comm menu)

4. press "F1" (which is "F1.Request Fighter Support in the comm menu)

5. press "F1" (which is "F1.Sori" in the comm menu)

 

There are others which i intend to create to take care of the myriad other commands but i hope you can now see what I am intending to do,

 

I want to be able to say 1 command phrase to choose all those menu options in one go , it has to be possible but for some reason none of the three programs will accept the initial command despite what keybinding i give it.

 

I am running the Missions Operation Snowfox and in this case Operation Clear Field.

 

Thanks in advance.

 

M

Edited October 16, 2019 by Badass1982

[Hollywood_315]

@Badass The import F10 Menu function is described in the user manual. It includes recursive import of the complete command tree and is by far the recommended option for this.

@dburne Thanks Don not reproducible here, SNGL all working fine. Perhaps your Windows application log will give a clue.

@MAXsenna It can vary depending on your keyboard locale mappings.

@jameslockridge Try with "Approaching for Refuel", see the user manual reference tables.

[Badass1982]

Thanks just found it. I HOPE this works the way I want it to.

 

Importing F10 Menus

Some missions make use of the ‘Other’(F10) menu for special commands. If in Preferences the option

‘Import F10 Menus’ is enabled the F10 menu items will be added to the keyword database.

The imported keywords cannot be used immediately, the updated keywords list must first be added

to the VA profile. See Keywords Editor section in the Configuration Window chapter.

[jameslockridge]

I am saying Approaching for Refuel. Then I hear Voice Attack say the command, but the tanker never responds.

 

It works for me in the F-18

[jameslockridge]

I am saying Approaching for Refuel. Then I hear Voice Attack say the command, but the tanker never responds.

 

It works for me in the F-18

 

My bad I found it in the Training option.

[MAXsenna]

I am saying Approaching for Refuel. Then I hear Voice Attack say the command, but the tanker never responds.

 

Nice! I didn't see you posted just before me! :-)

 

EDIT:

 

It works for me in the F-18

Stoopied question. But you have, of course, made sure you've tuned the radio to the tanker?

 

"VoiceAttack" say the command. You mean the "confirmation beep"?

What does the VoiceAttack log show?

 

Sent from my ANE-LX1 using Tapatalk

Edited October 16, 2019 by MAXsenna

[bradleyjs]

Hi guys

 

Ok not sure I could entirely follow the last pieces of this thread, but in any case in relation to the plugin and the Viper module:

 

- The greyed-out VHF radio (and consequently missing squelch and beep sounds, etc.) is caused by seemingly inaccurate values returned by the sim related to the Viper VHF radio device on/off state,

- This seems simply an EA loose end which in all likelyhood will be ironed out by ED at some point,

- Just in case I added a report in the viper forum section: https://forums.eagle.ru/showthread.php?t=252665

- Let's see if this leads to follow-up by ED dev. which should resolve the issue for VAICOM PRO users,

- Only if no fix by ED is implemented, ad-hoc workaround patches in the plugin may be considered for the Viper,

- For other modules there is no issue.

 

Thanks,

Hollywood

 

Thank you Hollywood for addressing this issue. My gut tells me that ED will fix it fairly soon. In the meantime, no harm, no foul! ;)

Edited October 16, 2019 by bradleyjs
Typo - my Bluetooth keyboard isn’t up to par

[dburne]

@Badass The import F10 Menu function is described in the user manual. It includes recursive import of the complete command tree and is by far the recommended option for this.

@dburne Thanks Don not reproducible here, SNGL all working fine. Perhaps your Windows application log will give a clue.

@MAXsenna It can vary depending on your keyboard locale mappings.

@jameslockridge Try with "Approaching for Refuel", see the user manual reference tables.

 

I apparently had not updated Voice Attack in a while, updated to latest version now it is working fine.

 

Thanks,