VAICOM PRO plugin for VoiceAttack

[Hollywood_315]

@wildw1ng The chatter pack also includes a Russia theme.

[SneakyBastd]

Thanks Hollywood for your PM. That clued me in to signal strength possibly being the issue.

 

In case anyone else is wondering, I have done some research and it seems many others have trouble getting VA to recognise anything said through the Vive microphone. This surprised me, because it comes out nice and clear in TS and other chat apps.

 

I borrowed a friends stereo headset with a built in microphone, and straight away VA recognised most things I said without any voice training. So it looks like I'm buying a better microphone!

 

Update: got a Modmic 5.0 by Antlion. It works much better now.

Edited February 26, 2018 by SneakyBastd

[tmansteve]

Is it possible to make the chatter a little louder. With engines started and using Viacom, the chatter fades away.

 

Any help would be great

[sze5003]

Is it possible to make the chatter a little louder. With engines started and using Viacom, the chatter fades away.

 

Any help would be great

Try setting the sound and music volume in settings of dcs to 50% rather than 100. I don't think there is a way to set chatter volume louder via Viacom.

[tmansteve]

OK, just a thought. I love sound and I probably drown it out. No worries.

 

Cheers

[tmansteve]

Went through the Keyword recognition the other day. Most of the words were picked up with 87 to 97 percent but, there are just a few that will not come close. I looked at the new Hollywood intro which was very informative.

 

Tbilisi is a bugger and Kutaisi just cant get it. I say it as in sim but not recogised. Others are. Any help??

[Quax456]

Unfortunatly VAICOM do not work with an OFFLINE campaign like RED-Flag for the A-10C....

 

I tried everything but after deactivating VAICOM the Wingmen as well as the JTACS are responding and following their orders....

 

VAICOM has recognized al my commands, and has transmitted something but nobody is responding!

 

Very sad....

[sze5003]

Unfortunatly VAICOM do not work with an OFFLINE campaign like RED-Flag for the A-10C....

 

I tried everything but after deactivating VAICOM the Wingmen as well as the JTACS are responding and following their orders....

 

VAICOM has recognized al my commands, and has transmitted something but nobody is responding!

 

Very sad....

It's not compatible with all misisons. For example the jtacs will work through Viacom if the campaign uses the same jtac callsigns as the ones that are in the Viacom manual reference table. Certain commands like "copy" are doubles in the script and won't get picked up.

[Quax456]

And why do my AI wingmans doesn't respond?

 

Even if I use the F-Keys to send my orders?

[Hollywood_315]

Quax I just did a quick test with Red Flag campaign to test and my wingmen respond just fine.

There could be something else in play in your case, especially if you don't even get a response using menus.

Will send a PM: let's check some details.

[Quax456]

OK....got it to work.

The result: never ever let TacView making its entries first of all other.

Put it evry time at the end of the export.lua :cry:

 

Thx for the quick help!

[Hollywood_315]

Thanks for updating Quax! :thumbup:

[Goldrake]

Great piece of software, surpassed only by your dedicated technical support. I am truly enjoying it.

There seems to be a compatibility issue with SRS and the Huey.

In the event that you are having issues, like me, running VAICOM and SRS in the Huey and your mike remains open when you press the TM HOTAS Throttle mic key, the following fix may help.

Open C:\Users\**your PC name**\Saved Games\DCS\Scripts\DCS-SimpleRadioStandalone.lua

In the following section: function SR.exportRadioUH1H(_data)

Find and delete the following lines:

if SR.getButtonPosition(194) >= 0.1 then

_data.ptt = true

end

Restart the DCS Huey module

If you update SRS to a new version, after you have modified the lua, then the 3 lines will reappear and you will need to take them out again (until properly fixed).

[sze5003]

I installed Vaicompro and bought the license. Once it was installed my Oculus no longer works. I get an error that Oculus cannot reach runtime service....

 

Any ideas or has this issue already been solved? It looks like I'll have to re-install my Oculus software.

Nothing to do with vaicom pro. Everyone that owns an occulus can't use it right now because occulus let their software certificate expire. They are working on fixing it. No eta yet.

[Wicked.-]

Roget that! I didn't know, thank you sir.

[soupyc]

The issue is with Occulus, not Vaicom Pro.

 

Vaicom has no control over what is happening with Occulus. Reinstalling your software also wont help.

 

https://www.vrfocus.com/2018/03/is-your-oculus-rift-currently-not-working-this-might-be-the-reason-why/

 

http://www.ign.com/g00/articles/2018/03/07/oculus-rifts-stopped-working-this-morning-around-the-globe

[sze5003]

Ok, so now I can't use the Oculus even after a total removal and reinstall of Oculus software. I've also uninstalled Voice Attack and Vaicom and deleted the folders and still it will not run.... Any ideas...

You won't be able to use the occulus at all until occulus fixes their software certificate problem. Doesn't matter how many times you install and reinstall the occulus software. The certificate is old and does not allow the software to run. You have to wait until it's fixed by occulus.

[Wicked.-]

So, even if I didn't install anything new Oculus would not work and that just happened today? I've been flying everyday for the last month with no issues.

[sze5003]

Yup everyone is screwed until they fix it. Happened today the certificate expired at 1pm.

[Wicked.-]

Roger that. I deleted my bitching post. My apologies Hollywood.

[_schepper_]

You won't be able to use the occulus at all until occulus fixes their software certificate problem. Doesn't matter how many times you install and reinstall the occulus software. The certificate is old and does not allow the software to run. You have to wait until it's fixed by occulus.

Yesterday i had the same problem, i changed the date of my pc to the 05/03/2018 (disable automatic date input) restart the pc and ocullus works again (temporary) ;)

 

Sorry for solution in the wrong tread,

 

Still love vaicom pro verry mutch :)

 

 

----------------------------------------------------------

 

i7 2600K oc 4.7g / asus gtx 1080 gaming x+ / 16gig ram / ssd 500gig / oculus rift / jetseat se / saitek rudder ((next upgrade)mfg crosswind) / logitech warthog hotas + 20cm extention / vaicompro 2.5

Edited March 8, 2018 by _schepper_

[Hollywood_315]

Thanks guys - indeed VAICOM PRO is not involved with the Oculus software issue.

@Goldrake Props for sharing that fix: will be further looked into.

@schepper Good to hear! Cheers :beer:

[0414 Wee Neal]

Issue

 

Hi

 

I have the following message:

 

21:23:55 - Unable to get value from URI - Could not find a part of the path 'C:\Program Files (x86)\VoiceAttack\Apps\VAICOM\Tools\TEMP\mission.lua'.

 

Also when pushing LCtl+LAlt+c I dont get another window like I used to?

 

Can anyone advise on the issue?

 

Thanks

 

Neal

Edited March 8, 2018 by Bluethornton
Missed a bit

[Hollywood_315]

@Bluethornton

 

Kindly note that VAICOM 2.0 is now superseded by the VAICOM 2.5 (FREE/PRO) plugin.

VAICOM 2.0 users are advised to upgrade to this latest version: https://www.vaicompro.com/downloads.html

For reference you can find information on VAICOM 2.0 in this thread (now closed) https://forums.eagle.ru/showthread.php?t=151296

 

If you have the plugin already installed you need to check the active profile in VoiceAttack:

make sure to use the 'VAICOM PRO for DCS World' profile that comes with the plugin installation.

 

Hope this is helpful, send me a PM if you need further assistance.

Edited March 8, 2018 by Hollywood_315

[0414 Wee Neal]

HI

I have /had installed the full version of Viacom 2.5 Pro including chatter and it was working fine until my CMOS battery went FUBAR. Should I uninstall all and reinstall?

 

Neal