Hollywood_315

@sze5003 First, the log shows you are using a disabled PTT key: 'PTT Key not in use: check configuration.' You need to check your TX mapping in the profile and on the PTT config page (e.g. Multi to Single). Second, there is an imported F10 keyword 'copy' that causes doubles with an existing keyword (i.e. Copy as reply statement). Resolve this conflict by resetting your database by using the RESET tab. Note that JTAC flows do not use the F10 menu at all: suggest to do your JTAC training with regular missions that do not rely on the Other menu. @Engine The options are stored immediately when you change them. If on your rig they are not saved somehow you need to carefully inspect your setup i.e. plugin install folder, folders R/W access, UAC settings, account privileges, VA running as admin.. I like the idea of the chatter link to power, of course you could start by assigning your power switch button to the Chatter command in the profile.

@Locutos, Mojo For importing F10 menu items first enable the feature and then fly the mission. The new keywords are added in the database. Press reload if needed to refresh the list. Then edit the new keywords as required and use the finish step to update the VA profile. Now when you fly the mission you can use the voice commands. PM me if more help needed with this. @cathaltli The low volume is intentional (background level). Implementing a foreground level feature would not be straightforward but I can put it on the list of things to look into. For now recommended to tweak the relative audio balance with DCS slider(s) to your preference. @BlacleyCole There's one here send me a PM if you need more help. Grtz

@Mojo PM inbound @Locutos Chatter sounds are processed to settle in at background level (ie discernible but not attracting attention) when DCS master level is set to around 50%. Some cockpits are noisier than others so you may need to work the various audio levels a bit to get the right balance. Make sure to check the relative levels in Windows Audio Mixer. @Frusheen Due to technical reasons Cargo flows are not supported in the initial VAICOM PRO release. Feature is planned (not committed yet) to be included in a later update.

@Fisherman From the screenshot it appears you have enabled VA listening in Training Mode, via some PTT or otherwise. That way things will not work properly. In Training Mode you need to keep VA listening disabled and only use the blue round mic icon in the speech recognition window. Enable blue mic when starting the training, disable again when done. @GIJoe Should work fine, use auto install. @Mojo The log points to a code error in your Speech.lua file. You'll need to clear all existing VAICOM PRO code at the end of that file starting with the comments block. Then restart VA and it should automatically restore the proper lua code. Confirm this and then try again.

PMs sent. Thanks Verstuurd vanaf mijn SM-G935F met Tapatalk

OK cuervo thanks for updating. That's correct for openbeta at the moment. These will update later i.e. after full DCS migration to 2.5 release. No need to change anything though, as only the registry paths are referenced and as such these numbers themselves are not relevant to the plugin.

That's funny. I updated 1.5OB to 2.5OB and after a VA restart all continued to work as normal without any issue. As far as the pugin is concerned the 2.5OB update is just an update so it will automatically restore the lua code after restart if the path didn't change. So unless there is something else in play here a reinstall should not be needed (which wouldn't affect Windows recognition profile btw). Do make sure to use the latest plugin dll from the website. Did you change install path? Can you enable debug mode have a look at the VA log on startup and perhaps scan your DCS.log for any funny messages there.

Hey cuervo Try these steps 1) Close DCS 2) Restart VoiceAttack 3) Start DCS. This will restore an automatic install after an update. If you had a manual install re-apply the steps from the User Manual. You can check install path in the VA log window on startup with debug mode enabled. Send me a PM if more help needed.

Hey Fisherman Just to come back on your questions Actually Select doesn't work like that. With Select you set a conversation to a specific recipient in that recipient category. So, if you select Soganlug as your current ATC recipient this has no effect on which unit you have selected as e.g. your AWACS recipient (or JTAC, Tanker etc.) and you can call those anytime without involving Select. Also all Flight recipients can be called instantly at any time without using Select at all. Just speaking for myself here I get all Caucasus airfields recognized just using training mode (even Novorssiysk although admittedly that took some effort) with the exception of 'Beslan' somehow. No idea why but I must be saying it wrong. At some point I added that one to the Windows Speech Dictionary and now that one works for me also. To check: in VA settings make sure to double check that (un)recognized speech delay is set to 0ms. Also you can play with the Command Weight option: set it to 85 or higher and see what difference it makes: it acts as a bias towards keywords and can help in some cases. Hope this clarifies, just catch me on PM anytime if more questions.

Observe the pause between recipient and command: User Manual page 15. Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey Stulee. The install drive does not matter, it runs on any drive. We may need to inspect DCS.log for any issues on your machine. PM inbound. Grtz

@Fisherman TacView has been tested to work alongside VAICOM PRO. Having said that there have been users with older TacView version installs causing a malfunctioning export.lua, thus blocking VAICOM PRO. TacView has signaled some problems with current DCS versions themselves http://dogsofwarvu.com/forum/index.php/topic,5645.new.html so that may be related. Send me a PM if you want me to have a closer look. @VampireOne Looks like an interesting project. Can you elaborate some use case scenarios i.e. what do you think could be achieved by an integration between VAICOM PRO and a MOOSE scripting environment.

@Duce :thumbup: @Bucks There's quite a few options there depending on how you want to do it. On my Warthog Throttle (without TARGET) the DIS/ENG shows up as DirectX key 26 with press-and hold function. So most straightforward may be to just map TX5 press/release to this button in the profile and see what happens. Grtz

+++ speech profile backup tool +++ General tip: If you invested time in training your voice recognition and your quite happy with the results you may want to have the option to back-up and restore your Windows speech recognition profile. Courtesy of http://www.voiceattack.com check out this helpful little Profile Manager tool: http://www.voiceattack.com/filesend.aspx?id=SpProfileMgr.zip This way you can also migrate your profile to another PC if needed at some point. Cheers Hollywood

@Hknine9 Your lua code requires repairing. Carefully follow the steps of post #156, also adding a DCS Repair after step 2. Have a look and I'll catch you on PM.

Yes only the plugin .dll needs to be replaced.

Thanks all for the nice messages, really appreciated :) Update: with the great help of a small but determined team of Sherlocks I managed to hunt down the bug that a few users reported regarding PTT refresh. Turns out this had to do with the Chatter.dll not being installed. Latest build on the website is now fixed for this. Existing installs especially without Chatter are advised to update the plugin to this latest version: https://www.vaicompro.com/downloads.html @Spetz, @Nickentik, @wingshigh.h +rep inbound!

Hey Sobe yes to update the plugin simply copy and replace the dll with latest version. To also update the lua files on an existing install follow instructions in post #156 i.e. remove the old VAICOM PRO lua code first by using p33 as reference: in each lua file the VAICOM PRO code chunck starts with a comments block, remove this comments block and all following code until the end of the file and save. Do this for the 4 lua files. Then restart VA and the auto-install will place the new lua code by itself. Hope this clarifies. Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey Combat this install stuff may get more simple in a few weeks when we will (yes! finally!) only have a single DCS 2.5 version to deal with. I'll be looking into how uninstall/update routine can be more automated. PM inbound regarding the restart question. Cheers. Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey Combat To update the plugin including the lua files the following steps are recommended 1) Download and install latest plugin build from the website. 2) Remove old lua file contents by backtracking manual install steps from page 33 3) Restart VA with debug mode enabled. Do not enable custom folders. 4) After VA restart inspect the debug log to see if auto-install was successful. Perform manual lua files install (p33) if required. 5) Switch off debug mode when done. Please have a look and if more help needed catch me on PM Grtz Verstuurd vanaf mijn SM-G935F met Tapatalk

Thanks for the logs I'm looking into the issue and will come back with an update. [EDIT] SOLVED: A faulty TacView install was blocking proper export.lua execution. Thanks for updating :beer:

Thanks for the log Spetz, it doesn't show issues. Investigations continue. [EDIT] SOLVED https://forums.eagle.ru/showpost.php...&postcount=168 Cheers

@Mojo Per above I may have reproduced something, need to identify what could be causing it. Will be diving further into it and report back with an update. [uPDATE] SOLVED https://forums.eagle.ru/showpost.php?p=3349473&postcount=168 @Brixmis good suggestion, you can do both using the Keywords Editor. In the default list there are no "soundalikes" but it can work to add them for tricky keywords. Results can vary but for JTAC I've had quite reasonable success with 'Jay Tack' myself also.

Hi @Nickentik The DCS log doesn't show problems. The VAICOM PRO log indicates your auto-install for 1.5 did not finish normally. Undo the manual install for 1.5 by refering to manual page 33. In config window clear the Custom Folders fields. Then get the latest plugin build from the website, restart, and try again. Catch me on PM if you need more help after that. @Spetz, all I seem to have reproduced an instance where in very specific cases the PTT refresh can stop working and VA restart is required. I couldn't reproduce this before. Looks like this may be related to your issue. I will be investigating this more and come back on it.

This is actually normal behaviour if the Instant Select option is not selected. Your dialog is set to Batumi and you need to use (Instant) Select to switch recipient. Please read the User Manual on the use of the Select command. PM me if you get stuck. Verstuurd vanaf mijn SM-G935F met Tapatalk