Hollywood_315

@Tundra If you have an existing install you can just replace the existing VAICOMPRO.dll with the new one from the download.

Hi mobua Yes there's one or two multiplayer servers out there that use special custom F10 menus with lua-illegal characters (such as $). This used to cause a hard VA crash but with plugin 2.5.4 that has been fixed. However on these MP servers you will see (default). It's on the list to look into a more permanent solution for this. P.S. As a sidenote the MP server must have Player Export enabled for tools like VAICOM, Simshaker, etc. to work in the first place. Grtz

@bonedust Keyboard shortcuts have to be enabled in VA (the keyboard icon) and the VAICOM PRO profile must be loaded. @redtail Chatter now links to radio power. Enable chatter and go through a ramp startup sequence: you'll hear chatter come alive as soon as the radios are powered on. Sent from my SM-G960F using Tapatalk

Thanks Smokey thumbs up mate :thumbup:

+++ Chatter Themes 2.5.2 update +++ Chatter lovers! Chatter Themepack 2.5.2 can now be downloaded: https://www.vaicompro.com/downloads.html This has +9dB increased loudness. For those who like things a tad louder :) All the best Hollywood

Hey Starkiller. Some ideas. For chatter use the DCS master slider to get the audio balance right (and use Hear like in Helmet). Configuring 6 TX keys is not needed, normally 3 or less is enough (or just map to a single). For recognition check the VA options (command weight, delay), use the correct keywords i.e. from the reference tables. Speak SLOWLY in the beginning, leave pause between recipient and command (manual p15). Feel free to PM, others may have more suggestions. Grtz Hollywood Sent from my SM-G960F using Tapatalk

@biga You don't seem to have any issue. The DCS.log showed all is OK and once you reset the luas the Interphone menu was gone. So no action needed. PM me if you have a specific question. @mibo Multipart, lower left in the VA edit window

Hey Cat As @Greyman points out in post #877 this is a known graphics bug in VoiceAttack: the 'When I Say' field shows blank but the content is actually there. Just follow the steps i.e. Crtl-A, Delete, Ctrl-V, and all will work normally.

@m4ti140 OK I won't keep repeating myself here. Read the last few posts of this thread for the suggested course of action - thoroughly clean up your lua - get the latest plugin build from the website. - restart VA.

Hey Biga Can you be specific. Which plugin build, which DCS version(s), which module(s), easy comms on or off, etc. Inspect your lua code carefully and remove any old code blocks. Run in debug mode, have a look at DCS.log and if any suspect entries there provide a link. Thanks

Try resizing the VA window to a normal size and then click on the taksbar icon.

+++ Garmin NS340 notes +++ Thanks @greyman @all A compatibility issue with the Garmin NS340 is solved in the latest plugin build 2.5.4 (180815-01): https://www.vaicompro.com/downloads.html If you have 2.5.4 already installed, clear you existing lua first before installing this new build. With this fix you should no longer have plugin connection issues ('default') when you're using the Garmin NS340 module (thanks @Gunnergolly!). However when you have the Garmin installed be aware that the NS340 can do some funny stuff with your radio assignments depending on the aircraft module and this may interfere with VAICOM functionality. Interestingly enough this can be the case even when you have the aircraft module deselected in the DCS Special / NS430 options (notably with the Harrier, which loses COMM2). Typically the Garmin adds a VHF FM (3) radio on slot 3 to your config, but this is then not the same device as your aircraft native FM radio. So be aware of this. Disabling the Garmin module in the Module Manager resolves all issues in any case. Grtz

@Sanatog PM sent. Likely some left-behind 2.5.3 code block in one of the lua files: try removing and it will restore after VA restart. Sent from my SM-G960F using Tapatalk

Hey alien Thanks, appreciated! The Engage command issued to your wingmen will use the SPI reference by default, so you do not have to specify this explicitly. Of course you can add appendices like '..from the SouthEast with GBU's' etc. to be more specific. If you go through the Reference Tables in the User Manual you'll see there's also additional stuff that you can deploy as separate tactical commands during your engagement such as 'Reference my SPI', 'Fence In' and ' Ray Target', etc. Check it out and have fun.:pilotfly:

Hey Milli the log looks fine. From the screenshot it appears you are running a specific desktop theme (Windows 7?). If you reset to the default theme I expect things should be back to normal.

Hey Gunner let's check some details - I'll send you a PM.

+++ Release update 2.5.4 +++ Hi Guys, Good news! Plugin version 2.5.4 can now be downloaded from the website. https://www.vaicompro.com/downloads.html Existing users: This update does not affect your license data or speech recognition profile. Replace your existing VAICOMPRO.dll with the new one and restart VA. You will be prompted to go through the FINISH steps to update your profile with new keywords. In this version - Fix for FA-18C Hornet comms device change 13 - Yak-52 support for Easy Communication ON and OFF - New ATCs added for Persian Gulf map - Keyword editor: imported F10 menu / ATC aliases can now be deleted - Improved Options function - COMM radio device swap for the Harrier - For non-FC3 aircraft: Chatter now based on radio powered on - Improved data interface with new lua code(auto-updates) - Various bugfixes. The lua code will update automatically. In case you experience issues: inspect the lua files (page 33) making sure all pre-2.5.4 code blocks have been properly removed. Happy flying! Hollywood

@mobua PM received, thanks. @Dooley Sounds good cheers @biga @blkspade I cannot reproduce, all seems to work fine here. Will run some more tests.

@waynard There is no such known issue. Check your config and refer to post #2 for the OB fix for the Hornet. PM me if you need more help. @mobua Check Buckeye's report in post #818 on the Dynamic DCS MP server. This is under investigation. If yours is a different server can you look in your Windows Application log (my computer, manage..) for a red cross entry related to VA and PM me with a copy/paste of the entry detail lines. @Tundra Sounds good - cheers mate @Dooley Have a look at post #805 onwards for various suggestions. Sent from my SM-G960F using Tapatalk

@pjgs Refer to the link in post #2. Grtz Sent from my SM-G960F using Tapatalk

@mibo The plugin reads the DCS World install path from Windows Registry. If this doesn't match your actual location, e.g. because you moved things around manually, look up at post #805 onward for alternative options. To access the config window carefully follow the installation instructions: you need to import the correct profile first and VA keyboard shortcuts must be enabled. @arturo PM sent @Firebird Assuming this is with easy comms ON. The 38->13 device change for the Hornet applies to OpenBeta atm, although I expect it to propagate to Release version also at some point. Normal behaviour here is that the nearest active tanker unit gets auto-selected by the plugin at mission entry, the same way it does for all other categories like ATCs, JTACs, etc. So for your example you'd expect this to be Texaco unit. Since it worked normally before this could be some mission-specific snag. You could try enabling debug mode and see what VAICOMPRO.log has to say. Also you could try testing with another mission and see if you can reproduce the effect there. PM me if you need more help - thanks. Sent from my SM-G960F using Tapatalk

@Blackspade Try setting the Instant Select option to ON in preferences and leave sufficient pause between recipient callsign and command (see manual p15). Re the Hornet look at post #793. @Evilfisher Yes Stennis Tarawa Nearest Carrier etc. you can all use for recipient in your calls, see reference tables in the back of the User Manual. You can enable the 'auto-import new theater' function to import newly added ships and ATCs to the keyword database. @Bucks PM sent. @Brun @GIJoe Good suggestions guys - thumbs up! [emoji106] Sent from my SM-G960F using Tapatalk

@Strike The Config window initially opens top left on the desktop and remembers position after that. @ownShip Audio balance for chatter is set with the DCS master slider, 50% recommended. @skins The install path is read from the Windows registry, check post #805 onwards. Install your lua code manually if required (manual page 33). Grtz Sent from my SM-G960F using Tapatalk

@Sanatog PM sent, your lua integrity counter shows 4/5 may need some attention. Sent from my SM-G960F using Tapatalk

Strange. Just to confirm this is with M2S with Easy Comms OFF and for those missions you mentioned. As e.g. Defend Camp Yankee works normally: looking in ME what is the (comms) difference with these other missions, also e.g. were they created in different DCS version. Can you run in debug mode and PM me a link to your VAICOMPRO.log please thanks. Sent from my SM-G960F using Tapatalk