Jump to content

VAICOM PRO plugin for VoiceAttack


Hollywood_315

Recommended Posts

Hey guys, some notes:

 

 

@Atelophobia Very low recognition rates usually point to a problem with your mic/device routing setup.

You need to spend time with the manual and ref tables: all commands for radio tuning menu control etc. are already there i.e. no need to add anything.

germany_orig.png BTW You can also use the German recognition engine if you prefer: make a translation of the English keywords to German and export your .csv file to share with the community

http://forums.eagle.ru/showpost.php?p=3795713&postcount=1636

 

Thank you Hollywood_315 !

 

I ll admit I didnt have too much time with both manuals. But when going through roughly it felt like most stuff is not yet important for me. I struggled with the basics. Even with basics like radios and radio tools work in DCS and what is important, Same for combining all those tools like discord, TS3 plugins etc in usefull warthog and VA profiles. Another reason was the annoying messingaround with windows speech settings all over the place andgoing through the boring speech recognition twice. Especially as a Dad - time is valueable :P

I ll try to go through again. I also prefer sticking to english. My DCS as well as Steam is set to english too. Its just Win itself which I prefer in german.

Beside that I want to take advantage of the work others did and offer. No need to do all by myself.

 

Going to test with microphone of headset plus microphone of my Vive pro tonight again, My confidence level gets better. But what about the needed settings in Win. They dont matter? Also speech recognition test was always in german. No matter how hard I tried :(

 

So most time went into basics instead of getting known to VA and VAICOM.

 

I ll try harder.

Win 10 Pro | Trustmaster Warthog | MFG Rudders | VivePro Wireless Gear Lens modded | 1080ti OC Asus | 32 GB DD4 RAM | i7 9700 | Razer Chroma Orbweaver Keypad | Corsair KB | Derek Switchbox | USB Keypad | Logitech 502 | Jetseat with SimShaker Software | TrackIR5 | Autotkey | Thrustmaster Cougar MFDs | Monstertech Mounts | Saitek Throttle Quadrant

Link to comment
Share on other sites

Thanks Snako

 

 

 

But I am still a little confused.

 

 

 

OK.

 

So we dont have to manually import the commands they are automatically imported into Vaicom. Correct?

Then why does the manual say you wont be able to use them imediately. you must import them??

 

 

 

If I want to fly a single player campaign (ARGO campaign or the UN campaign) there are usually a whole load of commands on the F10 menu How do I use these commands in DCS? how do I know what the keywords are and the voice commands to issue these commandss

 

 

 

Maybe I'm just being dense or just missing something but I just cant get to grips with this for some reason its just not clicking.

 

 

maybe someone can talk me through in baby steps just how to do this.

 

 

Cheers

SD

I am hoping I understand the issue here

 

How about using the Take1, Take 2,............. Take 12 voice commands

 

These command invoke the corresponding F1............... F12 commands in the comms menu.

 

So for F10 command to display custom radio for certain campaign mission, you call out Take 10 and this will invoke F10 and it goes like that. To select whatever is next on the menu like F4, you call out Take4.

 

I am assuming here that you want to be able to use the regular F1-F12 comms command in dcs.


Edited by Eaglewings

Windows 10 Pro 64bit|Ryzen 5600 @3.8Ghz|EVGA RTX 3070 XC3 Ultra|Corair vengence 32G DDR4 @3200mhz|MSI B550|Thrustmaster Flightstick| Virpil CM3 Throttle| Thrustmaster TFRP Rudder Pedal /Samsung Odyssey Plus Headset

Link to comment
Share on other sites

Hollywood, after today’s Vaicom update I can’t access configuration menu. Any clues, please?

 

 

 

After todays dcs update and addition of F14

Same herejoystick.gif

 

 

Try Lctrl Lalt V (not C)


Edited by Dispatch
found in commands

~

Link to comment
Share on other sites

After todays dcs update and addition of F14

Same herejoystick.gif

 

 

Try Lctrl Lalt V (not C)

 

no it is Lcrt + Lalt + C.

AMD RYZEN 7 2700 / 32GB / RTX2070 / 500GB M.2 with Windows and DCS / 2 - 500GB SSD / Rift S/ TM Warthog with F18 stick and Virpil WarBRD / Foxx Mounts/ MFG Crosswind rudders + 3 MFD's | Now enjoying VR with PointCTRL controllers + Gamematrix JetSeat

Link to comment
Share on other sites

New version for F14 - What has changed

 

When starting VA it updated to a new version to support the F14. I looked quickly but could not see what was added. I wanted to go in myself and add Check for the assisted startup with Jester.

 

BTW after it restarted it stated it had no new modules to import. This was after the F14 was installed.

 

Just would like to know so I don't screw something up.

AMD RYZEN 7 2700 / 32GB / RTX2070 / 500GB M.2 with Windows and DCS / 2 - 500GB SSD / Rift S/ TM Warthog with F18 stick and Virpil WarBRD / Foxx Mounts/ MFG Crosswind rudders + 3 MFD's | Now enjoying VR with PointCTRL controllers + Gamematrix JetSeat

Link to comment
Share on other sites

No problem here access the config menu after today's DCS update with F14.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

I can also access the config menu but I am not sure what the update actual added as far as F-14 options...I was hoping it added so sort of voice commands for Jester but I cannot seem to find any.

 

I did have a problem opening the config window after I had added a few commands. When I restarted VA it was fine again.

AMD RYZEN 7 2700 / 32GB / RTX2070 / 500GB M.2 with Windows and DCS / 2 - 500GB SSD / Rift S/ TM Warthog with F18 stick and Virpil WarBRD / Foxx Mounts/ MFG Crosswind rudders + 3 MFD's | Now enjoying VR with PointCTRL controllers + Gamematrix JetSeat

Link to comment
Share on other sites

I can also access the config menu but I am not sure what the update actual added as far as F-14 options...I was hoping it added so sort of voice commands for Jester but I cannot seem to find any.

 

Isn't Jester something Hollywood said he would be working on?

Would not think it would be available immediately.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

Today's plugin update was to enable standard radio communications functionality on the F-14.

The upcoming AIRIO extension is a separate module for VAICOM PRO that allows you to interact with Jester directly without using the menu wheel.

This is going through testing atm and will be released in the next week or two.

Grtz

There is no spoon.

 

Avatar_old_80x80.gif.0c105925ce4b9f5b87697ea37cbde317.gif

VAICOM PRO plugin for DCS World

www.vaicompro.com

Link to comment
Share on other sites

Today's plugin update was to enable standard radio communications functionality on the F-14.

The upcoming AIRIO extension is a separate module for VAICOM PRO that allows you to interact with Jester directly without using the menu wheel.

This is going through testing atm and will be released in the next week or two.

Grtz

Just brilliant :thumbup:

A warrior's mission is to foster the success of others.

i9-12900K | MSI RTX 3080Ti Suprim X | 128 GB Ram 3200 MHz DDR-4 | MSI MPG Edge Z690 | Samung EVO 980 Pro SSD | Virpil Stick, Throttle and Collective | MFG Crosswind | HP Reverb G2

RAT - On the Range - Rescue Helo - Recovery Tanker - Warehouse - Airboss

Link to comment
Share on other sites

Today's plugin update was to enable standard radio communications functionality on the F-14.

 

The upcoming AIRIO extension is a separate module for VAICOM PRO that allows you to interact with Jester directly without using the menu wheel.

 

This is going through testing atm and will be released in the next week or two.

 

Grtz

Oh that's awesome. Can't wait for the airo extension.

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Link to comment
Share on other sites

I have added a few commands to interact with Jester, I added Check and Loud and clear. I will get the AIRIO when it becomes available.

AMD RYZEN 7 2700 / 32GB / RTX2070 / 500GB M.2 with Windows and DCS / 2 - 500GB SSD / Rift S/ TM Warthog with F18 stick and Virpil WarBRD / Foxx Mounts/ MFG Crosswind rudders + 3 MFD's | Now enjoying VR with PointCTRL controllers + Gamematrix JetSeat

Link to comment
Share on other sites

Hi! I have tried the new 2.5.9.2 and I have continuously having communication menus even I don't press it and also I have the option to hide them. With the F14.

I made the spanish diccionary, so I don't know if the new additions to radios, can break something.

Link to comment
Share on other sites

Today's plugin update was to enable standard radio communications functionality on the F-14.

The upcoming AIRIO extension is a separate module for VAICOM PRO that allows you to interact with Jester directly without using the menu wheel.

This is going through testing atm and will be released in the next week or two.

Grtz

 

:thumbup:

 

Awesomeness Hollywood, thank you so much for all your efforts.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Link to comment
Share on other sites

Today's plugin update was to enable standard radio communications functionality on the F-14.

The upcoming AIRIO extension is a separate module for VAICOM PRO that allows you to interact with Jester directly without using the menu wheel.

This is going through testing atm and will be released in the next week or two.

Grtz

Thank you for your job. Looking forward to trying it! :pilotfly:

i5 8400 | 32 Gb RAM | RTX 2080Ti | Virpil Mongoose T-50 base w/ Warthog & Hornet sticks | Warthog throttle | Cougar throttle USB | DIY Collective | Virpil desk mount | VKB T-Rudder Mk IV | Oculus Rift S | Buddy-Fox A-10 UFC | 3x TM MFDs | 2x bass shakers pedal plate| SIMple SIMpit chair | WinWing TakeOff panel | PointCTRL v2 | Andre JetSeat | Winwing Hornet UFC | Winwing Viper ICP

FC3 - Warthog - F-5E - Harrier - NTTR - Hornet - Tomcat - Huey - Viper - C-101 - PG - Hip - SuperCarrier - Syria - Warthog II - Hind - South Atlantic - Sinai - Strike Eagle

Link to comment
Share on other sites

Today's plugin update was to enable standard radio communications functionality on the F-14.

 

 

It doesnt work for me even after it says it finished updated voiceattack.

No matter what i try i wont get the F14 name to show up in the plugin or get VAICOM to work in the cat.

 

 

VAICOMPRO.export.lua file doesnt show the F14 in the savedgames/DCSopenbeta/scripts/VAICOMPRO

 

 

After 2 reinstalls off this software it works all of a suddon....


Edited by Mainstay

g8PjVMw.png

Link to comment
Share on other sites

@Hollywood_315

 

The community will be forever in your debt...

 

'A significant contribution to DCS'

 

Ref post # 1817 & 1819 (auto-updating)

 

Same again with 2.5.9.2

 

Anyone else having this issue?

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

@Hollywood_315

 

The community will be forever in your debt...

 

'A significant contribution to DCS'

 

Ref post # 1817 & 1819 (auto-updating)

 

Same again with 2.5.9.2

 

Anyone else having this issue?

 

I have the same problem. I had to manually update the latest two releases (downloaded the new release from the website and replaced the dll file)

Link to comment
Share on other sites

KI am still having this issue after having used VAICOM PRO for over a year and would love to get this solved. I reinstalled DCS just to make sure that wasn't the problem, having come from 1.5 install, 2.5 beta, then release, etc... Just wiped it all out and installed 2.5 release, then updated to open beta.

 

I am using VAICOM PRO 2.5.9.2, VoiceAttack 1.7.3, DCS 2.5.4.28461.

 

This has been happening since I first began using VAICOM PRO, primarily UH-1 and Ka-50 is what I fly. After the latest DCS update, as usual, I reset just my "Lua code" through the Reset page (Master Zero). Easy Comms is off. I am not using a custom DCS path.

 

Everything starts out fine. I can change frequency in the Ka-50, talk to tower, talk to wingmen, use the "options" command and get a menu, etc. Everything works as expected. Until it doesn't. I can't figure out a pattern, but at some point in nearly any mission the comms seem to get out of sync between DCS and VAICOM PRO. What happens is I say a command to my wingman, hear the confirmation (high) beep, but don't see anything printed in the upper left. VoiceAttack registers the command in the log. The command is not acknowledged by my wingman. However, if I repeatedly press the TX button a few times, it will eventually print to the upper left and the wingman will acknowledge. It seems like it can store more than one of these commands in limbo, and then execute only eventually after repeating TX.

 

Any ideas here?

 

EDIT: not sure if this is helpful, but it seems like it's always 4 presses of the TX before the response processes in DCS once it gets stuck. Also, once this happens, it never recovers without starting the mission. I'll confirm whether it's the mission or DCS entirely. It does not require a restart of VoiceAttack to fix it.

 

EDIT: confirmed, it's just a restart of the mission, not DCS.


Edited by Rangoon
Link to comment
Share on other sites

Aircraft not recognized in a specific mission

 

I ran into a problem recently, where VAICOM Pro won't recognize my aircraft in a mission I've made. This only occurs in that particular mission. Any other mission I've tried works fine.

 

I've tried deleting Export.lua, using Custom path and resetting the .lua files, without success.

 

The VoiceAttack window won't update upon mission start with the Callsign, module etc. I have this issue with all modules I place in that mission.

 

This is the first time I've had this problem and I've flown that mission multiple times before. It showed up after DCS update OB 2.5.4.2846 and the subsequent VAICOM Pro 2.5.9.2 update.

 

The mission itself has the FA-18C as player aircraft and the only difference from before is the inclusion of the F-14B as an escort flight.

 

 

EDIT: I ran some tests, essentially rebuilding the mission piece with tests in between changes. Going by elimination, the problem was... too many oil and gas platforms. Together with the F-14's, I had set up a few extensive oilfields, but ininitially, I never thought that'd affect VAICOM. I am unsure if this is a new issue that came with the last patch or if the F-14 had something to do with it.


Edited by Harker
Testing results

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

I am hoping I understand the issue here

 

How about using the Take1, Take 2,............. Take 12 voice commands

 

These command invoke the corresponding F1............... F12 commands in the comms menu.

 

So for F10 command to display custom radio for certain campaign mission, you call out Take 10 and this will invoke F10 and it goes like that. To select whatever is next on the menu like F4, you call out Take4.

 

I am assuming here that you want to be able to use the regular F1-F12 comms command in dcs.

 

 

Aha

 

 

Sorry for late response I have been a bit distracted by the F-14 :)

 

 

Thanks for replying.

 

 

 

So if there is a mission based F10 menu choice to embark troops under F10 - menu item 4- Menu Item 2

 

I would just need to say Options(to bring up the F10 menu) - Take4 (to choose menu option 4) - Take2 (to choose Menu Option 2)..... I assume that is correct?

 

 

Looks like I just couldnt see the wood for the trees. I was thinking it was really complicated and it seems to actually be quite a simple task.

 

 

Ding. Penny drops

 

 

Thanks for the help EagleWing

 

SD

[sIGPIC]sigpic55726_5.gif[/sIGPIC]

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...