sgilewicz

Started Voice Attack/Vaicom Pro and was informed that Vaicom update was available. I selected "yes" to update now. Now when I launch Voice Attack/Vaicom Pro, I get: The multiple instances of Vaicom Pro plugin is perplexing and when I try to launch the GUI (LCTRL, LALT, C) Voice Attack closes. Any suggestions? Thanks!

Looks great! I'm on the last mission of Wolfpack 1 and it's been a blast. Hoping that DCS' new save-game capability will be applicable to your campaigns (I'll actually spend more time flying if I'm not worried about real life "interruptions"!). Anyway, I'll be buying on day 1. Thanks!

Noticed that installed VAICOM PRO version was the old 2.9.9 version. Checked the Voice Attack Apps folder and sure enough it was referencing VAICOM PRO 2.9.9 (I believe this was because the old VAICOM PRO profile was not deleted from Voice Attack prior to updating to 3.0.0). Uninstalled VAICOM PRO 2.9.9 using Windows Program manager, removed the VAICOM PRO profile from Voice Attack, then dropped the latest version into the Voice Attack Apps folder. Voila it now works and allows me to launch the VAICOM PRO config gui. Problem solved!

Hoping this is an easy question. I upgraded Voice Attack to v2.1.5 (paid for of course!), enabled plugin support and set VAICOM PRO for DCS World as my startup profile. Next, I downloaded the latest VAICOM PRO zip file and extracted it to the Voice Attack apps folder. The problem began when I attempted to open the VAICOM PRO gui to "finish' the command set. Each time I press Ctrl-Alt-C Voice Attack closes. Before I do the uninstall/reinstall dance, does anyone have some suggestions regarding what I may have omitted or screwed up? Many thanks in advance!

Marked as "Solved" and verified that "piggyback" profile commands execute with or without PTT in DCS. What a community! You guys rock!

Ding! Ding! Ding! We have a winner! Enabling Rel/Hot did the trick. Vaicom commands work with PTT while global profiles execute with just speech in VA and DCS. This setting was obviously enabled in my prior build but I'll be danged if I remember setting it (default setting maybe?). Just for my edification, what does the Rel/Hot actually do? It appears to allow non-Vaicom profiles to execute without PTT while still requiring PTT for Vaicom. Can't thank y'all enough. Now I can re-immerse into Reflected's Wolfpack campaign! Virtual beers to everyone!

@MAXsenna What you posted re: piggy backing was already being done (sorry, I didn't understand what you suggested. It sounded like adding the commands directly into Vaicom from the global profiles). As you can see below, this is how I'm currently set (any other ideas?) and thanks again:

Thanks gentlemen: @MAXsenna "Don't add them as global profiles, piggy back them into the VAICOM profile directly. You know how?" I do not! Please share. I was exploring if new commands could be added directly but have come up no joy to date @sthompson "There is a check box there labeled "Exclude Global Profiles." Make sure it isn't checked. If it is checked, that is the problem." The box is unchecked and should allow global profiles "Also, I'm assuming that the commands are NOT in your VAICOM PRO profile since if they are then the version in the VAICOM PRO profile takes precedence over the global profile command." You assume correctly sir!

About one month ago, I did a new pc build and reinstalled Voice Attack and Vaicom Pro. I imported 3 small profiles specific to individual aircraft (P-47, A-10C and F/A-18C). Vaicom Pro commands work perfectly across all three aircraft modules but the global profiles are recognized in Voice Attack but are not executed in DCS. Prior to the new build I had no issue with global profiles executing with Vaicom Pro. I'm sure I have overlooked something during the VA/Vaicom setup/configuration but after a month of tearing my hair out, I have come begging! Attached is a screen shot of my VA/Vaicom setup. Any suggested directions are most welcome. Enjoy your weekend!

THANK YOU Max!!! Saying "Options" while holding PTT was the missing piece. really appreciate your stopping by and providing illumination!

Okay. I understand, and that is consistent with how comms have worked throughout Wolfpack. The issue is when I execute PTT either via keyboard (RAlt \) or via Voice Attack (Vaicom) no menu appears to with which to launch F10. If I issue "PTT call radio menu" via keyboard or Voice Attack in any quick or single mission, the menu pops up and does so across modules. Perplexing...

PTT has worked just fine and yes, I have noticed that the comms menu is available on the ground. It is, however, also available on Inbound to ATC. What really brought this topic up was the Mission 10 trigger that causes Whippet Red 4 to call in engine trouble and a message pops up indicating 2 new commands available in the F10 menu. Since the comms menu is not available at this point in the mission, what does the player do to access these new commands? I tried PTT and issued an RTB to my #4 but no response was received and he proceeded on and made it through the mission. Not a real big deal but a perplexing one. Again, thanks for the incredible work you have done with so much attention to detail!

As the title says, it appears that the command menu is unavailable at certain points in missions. For example, I just completed Mission 10 and on the way to the RV my #4 reported engine trouble and I saw a message indicating that 2 new command were available in the F10 menu allowing me to order him RTB or stay with the flight. I was not able to bring up the menu either by mapped button or by keyboard directly. I also tried using the RTB command in Vaicom Pro but no joy. I have noticed similar instances in previous missions where sometimes the command is available and then unavailable later. Any thoughts/recommendations? All in all this campaign has been a great experience and has forced me to really learn engine management! The Jug is NOT for the faint of heart but is truly a beast if flown right. Thanks so much for your work!

Yaaay! Reflected, I took your advice, disabled the trim mod (trim is definitely more challenging without it but...) and ran DCS Repair. No engine shutdown and I flew for over 1:45 hours. I got 2 190s but crashed looking at my kneeboard trying to navigate home. Doh! Anyway, it was a blast and I'll be jumping into this campaign every chance I get. Thank you sir for the work AND the support. Virtual beer hoisted to you

I appreciate the feedback and it's good to know that a mission trigger isn't involved. I do have one unofficial mod that slows the trim adjustment rate. I can disable that and see what happens. Since this happens after about a half hour of flight time would you guys be willing to look at a trk file and comment on what may be happening if shutdown occurs even after mod disabling. Flying this over and over for this long with no indication of the problem source just isn't an option. That said I acknowledge that it's probably something on my end so I'd like to get myself sorted out. Truly appreciate your responses and the incredible work put into creating this campaign, Reflected.