VAICOM PRO plugin for VoiceAttack

[3ra_Luke]

Same for me on A10C after latest beta update.

 

Same here. But for now (I´ve just purchased VIACOM Pro), only tried the A10C. I keep sayin orders (even most simples ones, i.e. flight rejoin), and they never arrive to the sim. And they are correctly recognized on the VoiceAttack window.

 

I followed the manual on all steps in the configuration, even watching a youtube tutorial, but no luck. Its me, or VoiceAttack is not friend of the latest DCS 2.5 beta? :huh:

 

Tnx.

[TLTeo]

Seems like all the modules are affected, it wasn't functional in the F86 either.

[Hollywood_315]

I cannot test myself atm. Though not impossible it seems unlikely that comms changes were made by ED other than to the FA-18C module. To confirm this, users who have things working normally for other modules in OB are requested to report.

 

As general guidance if you experience issues after a DCS update the plugin auto-restores lua code but only if 'install files manually' is not checked. Always test with easy comms on first. Carefully inspect your lua files (p33), remove any code blocks from previous versions and/or do a DCS repair if needed. Double check VA runs as admin, look at lua integrity on startup in debug mode and in case issues remain check your DCS.log for clues. Hope this is helpful.

 

Grtz

Hollywood

 

Verstuurd vanaf mijn SM-G960F met Tapatalk

[Greyman]

I've just experienced something that i haven't noticed before and wondered if it was caused by an option that i might have changed, in VA, VAICOM PRO or DCS?

 

When flying the easy spring instant mission in the A10C, when i ask "two, engage tanks", Voice Attack responds with "Two, engage armour", as i remember it doing usually, but then it also says "Flight, engage armour". Two confirms his obediance, so it's not a really big issue, but i'm sure that i haven't noticed this before.

 

Could this be just because the flight only consists of 1 wingman, or is there something else i'm missing?

[3ra_Luke]

As general guidance if you experience issues after a DCS update the plugin auto-restores lua code but only if 'install files manually' is not checked. Always test with easy comms on first. Carefully inspect your lua files (p33), remove any code blocks from previous versions and/or do a DCS repair if needed. Double check VA runs as admin, look at lua integrity on startup in debug mode and in case issues remain check your DCS.log for clues. Hope this is helpful.

 

Thanks for the reply. I carefully checked all .lua files and found duplicated 2.5.0 and 2.5.3 lines, so I step by step deleted the old VAICOM lines, and manually pasted the correct ones, following the manual.

I have included in the Menu Configuration of VAICOM PRO (just in case) the manual path for the sim (C:\Games\Eagle Dynamics\DCS World Open Beta) because its not installed of default path, and I checked "Manage DCS-side files manually). No luck.

I must be missing something.

 

I used the debug mode and this is part of the log. I only noticed a strange line (red). I fly A10C. As I said, inside VoiceAttack, the words are perfectly recognized (I´m spanish but I think my english is good enough for voice recognition :-)), but DCS does do nothing:

 

VAICOM PRO logfile

Plugin version 2.5.3 build 180610-01

License: PRO

Manual installation selected: skipping automatic files configuration

Checking VA profile.

Updating keywords database...

Success.

Loading keywords database...

Success.

Loading F10 menu items...

Imported menu items

Adding 0 imported ATCs.

Adding 0 imported menu commands.

Building master keywords table...

Success.

Building master labels table...

Success.

No new DCS modules to import.

Exported aliases to keywords.txt, keyword count = 480

Current profile string does not match database. <-----------------THIS IS ODD

Adding themepack collections

Chatter theme set to Default

Adding chatter resources.. Default

Resources added.

Chatter initialized.

Startup finished.

Ready for commands.

.

.

 

In the VAICOM PTT menu, I always see (default) and not the module name I´m using. Is this related somehow to the problem??

 

Please, help. Thanks in advance.

Edited July 22, 2018 by 3ra_Luke

[Sanatog]

Hi Hollywood, thanks for your suggestions.

 

 

I have just given this is a test in both the M2000 and the A10C using both Easy Comms and Complex. All works as expected with Easy comms, however, with complex comms you are unable to communicate with elements using the various Radios.

 

 

 

Personally I use TX2, Map Multi to Single and Operate Dial and this typically allows me to use a single PTT to communicate on all radios. At the moment, in complex comms, this only works if I disable the Map Multi to Single and use the various PTT comms keys.

 

 

I have also tested clearing Lua code with auto and manual Vaicom Pro installation, which has made no apparent difference. No idea what to look for in the logs, but if you want to give some pointers im happy to have a glance through them.

 

Cheers

Edited July 22, 2018 by Sanatog
formating

[Greyman]

Thanks for the reply. I carefully checked all .lua files and found duplicated 2.5.0 and 2.5.3 lines, so I step by step deleted the old VAICOM lines, and manually pasted the correct ones, following the manual.

I have included in the Menu Configuration of VAICOM PRO (just in case) the manual path for the sim (C:\Games\Eagle Dynamics\DCS World Open Beta) because its not installed of default path, and I checked "Manage DCS-side files manually). No luck.

I must be missing something.

 

I used the debug mode and this is part of the log. I only noticed a strange line (red). I fly A10C. As I said, inside VoiceAttack, the words are perfectly recognized (I´m spanish but I think my english is good enough for voice recognition :-)), but DCS does do nothing:

 

VAICOM PRO logfile

Plugin version 2.5.3 build 180610-01

License: PRO

Manual installation selected: skipping automatic files configuration

Checking VA profile.

Updating keywords database...

Success.

Loading keywords database...

Success.

Loading F10 menu items...

Imported menu items

Adding 0 imported ATCs.

Adding 0 imported menu commands.

Building master keywords table...

Success.

Building master labels table...

Success.

No new DCS modules to import.

Exported aliases to keywords.txt, keyword count = 480

Current profile string does not match database. <-----------------THIS IS ODD

Adding themepack collections

Chatter theme set to Default

Adding chatter resources.. Default

Resources added.

Chatter initialized.

Startup finished.

Ready for commands.

.

.

 

In the VAICOM PTT menu, I always see (default) and not the module name I´m using. Is this related somehow to the problem??

 

Please, help. Thanks in advance.

 

i was getting this yesterday, but when i deleted the VAICOMPRO.export.lua file, to allow it to be automatically created by a restart of VA, the module name was properly changed to reflect the active aircraft.

[3ra_Luke]

i was getting this yesterday, but when i deleted the VAICOMPRO.export.lua file, to allow it to be automatically created by a restart of VA, the module name was properly changed to reflect the active aircraft.

 

YES!!!!! Your tip made me think that maybe using manual mode was not the answer, so I deleted all .lua files that VAICOM modifies and left the default files from DCS game folder, deleted the VAICOMPRO.export.lua and export.lua from settings folder, changed VAICOM to automatic and after run again VA, VAICOM did its magic with the auto configuration and it WORKED!!. The sim listened to me and my flight did as ordered. Also, the correct module appears on the VAICOM main screen.

 

THANKS SO MUCH!!! :pilotfly:

[Hollywood_315]

Thanks all

 

@greyman It will depend on your speech timing. If you leave sufficient micropause Two will be recognized as the recipient else it will revert to the default i.e. Flight. You can practise with Audio Hints to get used to the rhythm.

 

@Sanatog OK so if I understand correctly things work normally just as long as you don't use the M2S option. That would be a separate issue. You could try disabling Operate Dial to see if it makes a difference.

 

@Luke Sounds good thanks for updating. Re the red line you need to update your VA profile using the FINISH steps, see manual.

 

@Arakahn They need to be both the same number and refer to the Hornet's Intercom device ID. To know what this has now become (was 38 before) you'd need to dig into the cockpit scripts devices lua in the Hornet mod folder. But given the SRS numbers I've seen 37 and 41 would be inspired choices to try a quick test with.

 

Sent from my SM-G960F using Tapatalk

[Arakahn]

Thanks all

 

@greyman It will depend on your speech timing. If you leave sufficient micropause Two will be recognized as the recipient else it will revert to the default i.e. Flight. You can practise with Audio Hints to get used to the rhythm.

 

@Sanatog OK so if I understand correctly things work normally just as long as you don't use the M2S option. That would be a separate issue. You could try disabling Operate Dial to see if it makes a difference.

 

@Luke Sounds good thanks for updating. Re the red line you need to update your VA profile using the FINISH steps, see manual.

 

@Arakahn They need to be both the same number and refer to the Hornet's Intercom device ID. To know what this has now become (was 38 before) you'd need to dig into the cockpit scripts devices lua in the Hornet mod folder. But given the SRS numbers I've seen 37 and 41 would be inspired choices to try a quick test with.

 

Sent from my SM-G960F using Tapatalk

 

Here is what I have in the devices.lua:

 

-- Radio & Comm

devices["UHF1"] = counter()--38 -- VHF/UHF Receiver-Transmitter - ARC 210

devices["UHF2"] = counter()--39

 

and the vaicompro.export.lua:

 

Flush = function(self)

local mod = LoGetSelfData().Name

if mod == "FA-18C_hornet" then

GetDevice(38 ):performClickableAction(3027,0.2)

GetDevice(38 ):performClickableAction(3027,0)

LoSetCommand(179)

return

end

 

I see in the PTT tab that COMM1 is at device 38 and COMM2 at device 39, recognizing FA-18C; works in easy comm but not in full comms :(

[Hollywood_315]

PM sent.

 

Sent from my SM-G960F using Tapatalk

[Greyman]

Thanks all

 

@greyman It will depend on your speech timing. If you leave sufficient micropause Two will be recognized as the recipient else it will revert to the default i.e. Flight. You can practise with Audio Hints to get used to the rhythm.

 

 

Thanks for the reply @Hollywood_315. I will give it a try

[Hollywood_315]

Ok so to summarize status the plugin works normally with all modules in 2.5 and 2.5OB both with easy comms on and off.

 

- Exception FA-18C in OB with easy comms off, caused by the change to the Hornet comms system. It 's being looked into, use easy comms on for now as workaround.

- Potentially a bug with Multi-to-Single, to be further investigated.

 

Cheers

 

Sent from my SM-G960F using Tapatalk

[Arakahn]

SUCCESS!!!! :D

 

For those who it does not work in the F18 with the latest OB update, here is the solution that @Hollywood_315 and I found.

 

In the DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\devices.lua you should have that line:

 

-- HOTAS Interface

devices["HOTAS"]= counter()--13 -- Stick and throttle grip

 

In vaicompro.export.lua change the device ID in this block:

 

if mod == "FA-18C_hornet" then

GetDevice(38 ):performClickableAction(3027,0.2)

GetDevice(38 ):performClickableAction(3027,0)

LoSetCommand(179)

 

would become

 

if mod == "FA-18C_hornet" then

GetDevice(13):performClickableAction(3027,0.2)

GetDevice(13):performClickableAction(3027,0)

LoSetCommand(179)

Edited July 23, 2018 by Arakahn

[Brun]

That's great news, thanks guys.

 

I did try a few numbers around 38. Don't think I'd have got round to 13 tho.

[Sanatog]

Hi Hollywood,

 

 

I have just tested turning the Operate Dial on and off and it doesnt appear to make any difference. I have also restricted the testing to the A10C, I have been flying it for a while so I'm used to when the radios respond better than I am with the M2000.

This all said, the odd thing is, if I test on the default Defend Camp Yankee mission the radios respond as expected.

 

If, however, i test on other missions, such as Through The Inferno (Georgia and Nevada) and Operation Titan Angel the radios do not change. But I can communicate if i use the various radio PTT buttons.

[Greyman]

SUCCESS!!!! :D

 

For those who it does not work in the F18 with the latest OB update, here is the solution that @Hollywood_315 and I found.

 

In the DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\devices.lua you should have that line:

 

-- HOTAS Interface

devices["HOTAS"]= counter()--13 -- Stick and throttle grip

 

In vaicompro.export.lua change the device ID in this block:

 

if mod == "FA-18C_hornet" then

GetDevice(38 ):performClickableAction(3027,0.2)

GetDevice(38 ):performClickableAction(3027,0)

LoSetCommand(179)

 

would become

 

if mod == "FA-18C_hornet" then

GetDevice(13):performClickableAction(3027,0.2)

GetDevice(13):performClickableAction(3027,0)

LoSetCommand(179)

 

That's awesome thanks guys.

 

Just tried it out and it appears to work perfectly. \o/\o/\o/

[funkyfranky]

SUCCESS!!!! :D

 

For those who it does not work in the F18 with the latest OB update, here is the solution that @Hollywood_315 and I found.

 

In the DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\devices.lua you should have that line:

 

-- HOTAS Interface

devices["HOTAS"]= counter()--13 -- Stick and throttle grip

 

In vaicompro.export.lua change the device ID in this block:

 

if mod == "FA-18C_hornet" then

GetDevice(38 ):performClickableAction(3027,0.2)

GetDevice(38 ):performClickableAction(3027,0)

LoSetCommand(179)

 

would become

 

if mod == "FA-18C_hornet" then

GetDevice(13):performClickableAction(3027,0.2)

GetDevice(13):performClickableAction(3027,0)

LoSetCommand(179)

Good find! Same thing that caused the key bindings problem ;)

[Biga42]

Where do I find this vaicompro.export.lua file to edit?

 

Thanks!

[mobua]

Hi @Hollywood_315,

 

Just purchased PRO licence and having the following issues:

 

1. Can't reach recipient on UHF radio 2. VA (recognizes my voice correctly.)

1.1 VAICOM recognizes easy communication as ONeven though it is set to OFF.

 

2. VAICOM fails to recognize the airframe operated, it instead states default.

 

I am operating on the latest DCS Open Beta.

Edited July 24, 2018 by mobua

[Buckeye]

Anyone ever have an issue where the first voice command they give Voice Attack bugs out and shuts down? When I reopen it, it gives a message that says “There was an improper shutdown...”

 

Any ideas on how I can fix this?

 

 

Sent from my iPhone using Tapatalk

[Fercyful]

Where do I find this vaicompro.export.lua file to edit?

 

Thanks!

 

I have it here :

 

C:\Users\[uSER]\Saved Games\DCS\Scripts\VAICOMPRO

 

Good luck! :thumbup:

 

ps: I use an util called "Everything" (is free) is great for find files in the computer in seconds.

 

https://www.voidtools.com/en-us/

 

Highly recommended

[Biga42]

Thanks!!

[mobua]

Ok so to summarize status the plugin works normally with all modules in 2.5 and 2.5OB both with easy comms on and off.

 

- Exception FA-18C in OB with easy comms off, caused by the change to the Hornet comms system. It 's being looked into, use easy comms on for now as workaround.

- Potentially a bug with Multi-to-Single, to be further investigated.

 

Cheers

 

Sent from my SM-G960F using Tapatalk

Hi @Hollywood_315,

 

Just purchased PRO licence and having the following issues:

 

1. Can't reach recipient on UHF radio 2. VA (recognizes my voice correctly.)

1.1 VAICOM recognizes easy communication as ONeven though it is set to OFF.

 

2. VAICOM fails to recognize the airframe operated, it instead states default.

 

I am operating on the latest DCS Open Beta.

 

Also;

i. I have DCS installed on a secondary drive (not C:).

ii. In the logs when starting VA it states "DCS World installation path = C:\Program Files\Eagle Dynamics\DCS World". Which is not the case...

 

Greatful for any assitance...

[Archer_111]

Just doing a simple routine reset of Viacom Pro files and then delete the whole plug-in from VoiceAttack, followed by doing a reinstall of a fresh set of Viacom Pro 2.53 + Chat.dll 2.51 back in, has saved me lots of angst and troubles of fighting those weird and crazy bugs every time when DCS is patched with a new update.

Edited July 25, 2018 by Archer_111