Hollywood_315

@warrene Thanks for flagging. Fixed, will be in next update. @Fercyful My spanish is not great unfortunately, sorry! :cry: Not sure how I can improve on the manual there, but normally it's all pretty straightforward. Only two things to be mindful of: a) Commands need to be collapsed in VA: b) The ' when I say' field can look empty, but that can be ignored: content is actually there.

Only when new keywords are added: in that case you'll be prompted to do the FINISH steps. Grtz

Plugin updates. Sent from my SM-G960F using Tapatalk

No worries - automatic from now on :)

Hey Mojo. VA 1.7.2? Running as admin? Plugin 2.5.5? Manual lua install off? Running any other apps? Anything in dcs.log? Cheers.

@steve Yep, that's in the manual. @Zyll Yes the plugin deals with any freq/mod set in the mission editor. System works the same in MP and SP mode. If you want to check it out, just grab the free version from the website and run some tests with it in SP.

Hey Baron. Not clear which problem you mean exactly, anyway @moggel had his things fixed by updating to 2.5.5. Make sure to use the automatic installer i.e. disable the manual lua install option. Also check post #945 by greyman. EDIT: solved by re-install.

@filthyman Yeah now that you mention it lol. I like the idea.

You got an answer at post #933. So did you update to 2.5.5? The effect is not reproduceable here. Also there's no relation between the BCN blink rate and data exchange frequency, so unclear atm how there would be a link to the plugin. Suggest to also check other mods you may have installed, perhaps there is some kind of conflict. Grtz Sent from my SM-G960F using Tapatalk

@dpj463 Try again using backslash. BTW the plugin also reads the Steam base path from registry so you could check if that path is valid. PM me if you get stuck. @SCU Cheers, sounds good. It's funny how everyone seems to have their own preference for clicks, I should do a themepack lol. You can disable the squelch sound in preferences, should you have your own favorite sounds you can add .wav playback to the TX commands directly in the VA profile. @Kunterbunt Thanks for the update mate, enjoy :thumbup:

Assuming you run VA as admin: if your DCS install is not detected then there is a problem with the ED path entry in Windows Registry. You can have a look at post #805 and after for some ideas on workarounds for that. Make sure to have the latest plugin version 2.5.5 and if you use the custom folder option fill in only the parent folder in the field: if your install path is "D:\Mystuff\DCS World" then fill in "D:\Mystuff\".

@greyman Re: JESTER project I'm well aware of it (but then, who isn't lol) and it certainly sounds like interesting stuff. Adding standard DirectX sends to the VA profile may not be so straightforward if Heatblur build something on a dynamic GUI system where commands can have unpredictable positions/shortcuts based on context etc. A VAICOM PRO-type direct interface based on UDP is in general more powerful for speech recognition, especially when things can get dynamic and the dialogs with the AI interactive. So far I've only seen a mockup screenshot or two of their planned GUI, a bit hard to tell yet what things will exactly look like in action. At first glance it does look like a natural fit to build a RIO dialog expansion pack for VAICOM PRO, open to talk to people about it, but no idea atm if such a project would fit into e.g. Heatblurs plans. Technically it should be doable, will just depend on how much of an API/entry points can be opened up. So let's stay tuned. Cheers

Thanks@greyman @Kunterbunt On FINISH the clipboard string is exported also to keywords.txt file in the Export subfolder. First time I hear of an empty copy buffer btw. Suggest to remove your database subfolder, update plugin dll to latest version 2.5.5, restart VA. For instant calls to new recipients e.g. Stennis enable the Instant Select function in preferences. Grtz

Yes that's correct, v4 refers to the interface, nothing to do with the plugin version.

+++ Release update 2.5.5 +++ Greetings all, VAICOM PRO plugin version 2.5.5 can now be downloaded: https://www.vaicompro.com/downloads.html This version includes an automatic plugin updater, so this should be the last time you have to download and install an update yourself :D Existing installations: replace your VAICOMPRO.dll with the new one from the download, restart VA, done. Changelog: - Updated beacon function with bugfix for easy comms off, - Added automatic plugin updater, - Revised F10 menu import function with fixes, - Revised lua code handling for more robustness, - Better Garmin NS430 tolerance, - Improved compatibility for various MP servers. Enjoy! Hollywood

That points to a problem with your lua install: have a look in the five lua files mentioned on manual page 33, try removing all VAICOM PRO code blocks and restart VA.

@Laithar The correct airfield name must be used and recognized: if the airfield name is not recognized in your command the system will default to the currently selected ATC, which means the nearest tower if none was selected previously. So the trick is to make sure that the recipient name is properly set before completing the call. Leave a small pause e.g. "Batumi,..(small pause)..Inbound". @Immel The beacon has to do with the data communication between DCS and the plugin. Your blinking on replay may point to an installation problem, but that should resolve itself anyway when plugin 2.5.5 becomes available in a few days. Plugin 2.5.5 features an automatic updater so people will no longer have to worry about downloading and installing plugin updates themselves.

Funny enough switching off the pilot voice can actually be a workaround for this bug in some cases, so you could give that a go. Sent from my SM-G960F using Tapatalk

Hey Spider Replace your vaicompro.dll with the latest download from the website (2.5.4) and try again. Make sure VA is running as administrator (check the Compatibility tab in VA's shortcut properties). The plugin uses Windows registry to automatically determine the DCS install paths. DCS version updates over time have not always kept the Windows Registry entries valid: have a look at post #805 and onwards for some useful ideas on workarounds for that.

@redtail Perhaps related to the new beacon (BCN) function that serves as a data interface heartbeat. I'm looking into a potential bug atm where in certain circumstances (JTAC, ATC,..) it seems this can interfere with easy comms off. Working on a solution and will come back on it. Thanks

Hey Spider VA generates this error at your startup This prevents the plugin from launching normally. You'll need to check your Windows control panel for speech reconition and make sure that a working mic device is set up for it. Once that error is out of the way VA should boot OK and the plugin auto-installer can do the rest. BTW your plugin version is not the latest, get 2.5.4 here https://www.vaicompro.com/downloads.html @tailfin :thumbup:

Hey guys. Not a bug in current version, it's just the standard recipe again: get the latest plugin version, and CAREFULLY inspect the five lua files from manual page 33 if you get no response in DCS. Remove all VAICOM code blocks ( there could be doubles left from previous installs) and restart VA. Alternatively remove the lua files completely and run a DCS repair. Redtail got his chatter fixed, also using the above steps. Sent from my SM-G960F using Tapatalk

Looks like you may need to reset your lua code. PM inbound. Sent from my SM-G960F using Tapatalk

@Rum The new keywords should be added normally and the FINISH button will light up. Can you send me a link to your VAICOMPRO.log via PM and we'll have a look thanks. @redtail Well that's funny. You did have the Chatter function switched on before you entered the mission? Because it doesn't do that by itself (unless you have 'start chatter automatically on plugin startup' switched on). Also just to check: running the Garmin NS340 by any chance? Can you try ramp start with another module e.g. A-10C and catch me on PM. Cheers mate.

@redtail The Chatter function must be on in the plugin, in the Hornet the UFC must be powered on, to switch on a radio turn its COMM knob clockwise (this is not part of the auto sequence). Chatter starts when a radio is active. To check: when switched on, the radio color will change from dark to light grey on the PTT page and when you press its PTT key you hear the squelch sound.