Hollywood_315

@Strike Thumbs up mate! Good that you got it fixed, we'll add that link to the FAQ page. Cheers

Never heard that 45 sec thing before. Try with other missions, it's likely some mission-specific (i.e. ME) snag. For dialog references look on page 34 of the manual. Grtz

@Slayer, Anthony The plugin install is linked to MS Windows. If you copied your folder around to a different machine, delete the Config and Database subfolders and restart VA. Drive locations etc. are irrelevant but the reg entries must be valid for the auto-installer to work: use the Custom Folder option and disable other apps in export.lua to test if needed. @Snacks Yes VAICOM PRO can send commands that are not in the menu. Lots, in fact. It uses a dedicated system to hook directly in to the DCS core and bypass the menu system altogether. This is why the plugin can deal with complex dynamically shifting states such as e.g. for (multiple) ATC and JTAC recipients, which cannot be done with regular VA profiles. Getting an answer in a dialog depends on the DCS core state i.e. if certain conditions are met such as being lined up to the runway, having passed previous calls, etc.

@emc Try with not clicking around with your mouse during Training Mode. Just enable the MSVR listening, and then use your keyboard up/down keys to step through the keywords list as described on page 30. PM me if you get stuck. Grtz

@B2Blain You may want to spend a bit more time with the plugin User Manual, link in first post of this thread. Detailed installation and TX PTT config guides are in there. You'll need to have loaded the correct VA profile to use the plugin. No DCS mod is involved. PM me if you get stuck. @Jack Try slowing your pace and wait for the recipient to be recognized before finishing the command. See page 15 of the manual. @strike All good, thanks for updating. @emc You may see this in debug mode if you incidentally press the Reload button. Either way these messages are harmless. Cheers

Hi there Use right mouse click to rotate the dial. In case your module is not recognized inspect the lua install path in debug mode. Use custom folder option to point to your DCS World location if needed. Grtz Sent from my SM-G960F using Tapatalk

@Strike Funny. I'm assuming your logs don't show anything specific. Blinking has been reproducible only when RadioCommandDialogsPanel.lua is not properly installed. Check that file specifically: i.e. delete it and verify it gets replaced automatically on VA restart. Confirm your Windows account has sufficient admin rights (UAC) to write to the DCS folders, disable antivirus if needed. In Saved Games check that files are updated in the DCS.openbeta folder.

All the best for 2019 guys.. promises to be a really great year for DCS! :thumbup: Your training data is stored deep inside Windows: unless you re-install Windows you do not lose it. Loudness of the plugin PTT squelch sound hasn't changed. For VR, make sure your HMD is set as Windows default audio device so that all Windows audio is fed to your headphones. For using VAICOM PRO you need to have VA's licensed version. A RIO dialog extension is high on the priority list, preparations have already started. Stay tuned! Grtz

Ok roger, seems the 'Status' alias for interrogate was not added. I'll see what i can find, in the meantime you can just add it manually in the keywords editor. Thanks

@eric AOCS responds with a status summary of all unit categories. Deep Interrogate must be enabled in preferences. Grtz

@B2Blain Old profiles don't work with the plugin, you need to load the specific universal .vap profile that is generated by the plugin. See install notes / user manual. @cabzi Looks like your keyword database may have become corrupted somehow. Clear keywords using the Reset tab and restart VA.

Not really, this is basic VA stuff not related to the plugin. Suggest to thoroughly test your joystick devices in Windows control panel first. Make sure you have a vanilla VA 1.7.3 install. Try disconnect (-) and reconnect in VA (+), disabling hat switches. See what happens with another (e.g. gamepad) device. Check your TARGET or other apps (e.g. Norton) are not interfering with proper functioning. Hope it helps, if no joy you may want to refer to VA forums https://forum.voiceattack.com/smf/ Grtz

+++ release update 2.5.7 +++ Plugin update 2.5.7 features improved MP compatibility, new advanced recipient handling logic for Easy Comms OFF. Also new ATCs for Persian Gulf (Lavan Island, Kish, Sas Al Nakheel, Abu Dhabi), and several minor code tweaks and improvements. Existing users update automatically. And, as a special Christmas bonus: a new Air Operations Control Station extension (default callsign 'Crystal Palace') is now included. AOCS will provide you with mission briefing data as well as detailed coalition units status information including BRAA and contact frequencies. Use with the Briefing and Interrogate / Status commands, more info on User Manual page 16. Happy Holidays!

@chaser Make sure the VAICOM PRO profile is loaded and VA keyboard shortcuts are enabled (keyboard icon).

@Shack Intent to Refuel is already part of the command set: alias 'Approaching for Refuel'. Check the keyword reference tables in the manual. Use the Keyword Editor if you want to change an alias.

@jo For license key questions you can contact info@vaicompro.com https://www.vaicompro.com/support.html @Alligin You need the registered version of VA and it needs to runs as administrator. Inspect the Compatibility tab of your VA shortcut. Files and subfolders are automatically created by the plugin on first launch. Grtz

Hey DE, It's a rotating knob: right-click to rotate clockwise, left-click for counter clockwise Cheers

@lah It's a problem within the DCS module. @sydy You have a lua install problem, make sure VA runs as admin, try setting the DCS path with the custom folder option and check the manual and FAQ page for some more hints.https://www.vaicompro.com/faq.html

@lah https://forums.eagle.ru/showpost.php?p=3693385&postcount=1216 @chaser run VA as admin.

@sydy Cheers mate, enjoy the product! @Fisherman Assuming you're on 2.5.6 there are no known instabilities with VA atm. Unless Windows event logs point specifically to the plugin these are likely caused by something else e.g. an audio driver. @targs Have a look here https://www.vaicompro.com/faq.html @strike Flashing menu indicates you have a lua install problem. Carefully inspect your lua (page 33), remove the files to be sure and have them automatically be rebuilt after VA restart. Run VA as admin and check your Windows UAC account has sufficient R/W rights. @Don Thanks for the heads-up, we'll have a look. @milko The click in the MiG21 is strictly speaking a fault in the DCS module: it produces a sound for a push button that is already depressed. You could flag it as an issue but firmly in the Minor category.

Sure, VA allows you to export your profile for back-up, also export/import of individual commands. Always a good idea to have a backup copy somewhere. Check VA's Help PDF.

@slicker The VA profile and any added custom commands are not changed by plugin updates. @Don The plugin scans the currently loaded VA profile to check if all database keywords are in there. For non-VAICOM profiles this is obviously not the case and you can ignore the message. @steve VAICOM PRO 2.5.6 can be used with any VA version. Grtz Sent from my SM-G960F using Tapatalk

Found it.. fixed for next update. Grtz

Well just use voice commands, that is what it's for :D Thanks for the report, will see what I can reproduce and if there's a snag there we'll get it sorted out.

Thanks Phil. OK in that case what you're experiecing is most likely mission-design specific, i.e. a problem in DCS itself. ATC's can have both unit names and unit callsigns assigned and I've seen some examples of mission design where inadvertently an airfield name gets assigned as callsign to another airfield. You get the picture: that would cause the symptoms you're describing. Suggest to test with some other missions, PM inbound.