Hollywood_315

@Phil73805 You may have missed the answer I provided earlier, so copying: @Skipper Not reproduceable: for reference the following has been tested to run together in parallel DCS 2.5.3.24436, SSA 1.3.2.1 w/ SoundModule 2.8, SRS 1.5.5.0 (server+client), VA 1.7.4, VAICOM PRO 2.5.6, TacView 1.7.4. Any order in export.lua. You may want to inspect your SRS (luas) and other apps installs. @strike277 Blinking menus mean you have a lua install problem. Use the custom folder option to point to your DCS World location, use the ob flag for openbeta. Thanks

Heya Don Make sure commands in VA are consolidated Grtz

@Biga Yeah it seems the message sometimes doesn't get properly reset. Will be looked into, for now just ignore it if your database is already up-to-date. @BaLrOg OK in the default database there is already an alias 'Mission', also 'Group': delete or rename and see how you get on then.

@dburne The FINISH step is part of the procedure to update your keywords database: details in the manual. @mmcintosh Thanks for updating. See previous post (#1264), feel free to send a PM if you need additional help. @BaLrOg For the import menus there is no iteration depth limit in practical terms. The imported commands are added to the database starting with ACTION keyword initially. Using the keywords editor you can then edit these commands further. @epolta Mods are not supported by the plugin, although depending on how they were designed some mods may still work. @Nodak Thanks for that tip on Sonic Suite, I've had similar reports previously where audio driver tools can interfere with proper recognition. Indeed recommended to turn off all such tools and rely only on Windows standard functions. @Mule The appendices for weapons directives and attack direction can be used for the DCS modules that support them. Not all DCS modules support attack direction cues but e.g. the A-10C does. You need to have the 'Use Appendices' option enabled in plugin preferences. @Tom Look for the Playtime commands to check in with JTAC: more details in the Reference sections in the manual. :joystick:

+++ VA 1.7.3 update procedure +++ @all To re-confirm the update procedure for VA 1.7.3 is as follows 1) Have VA 1.7.3 installed first (clean, i.e. do not make any dll changes), 2) Then install the latest plugin build. The plugin updater includes a reminder to update VA first. With the current hotfix there can still be occasional ctd on VA startup. A permafix for that is being tested atm and will be part of next plugin update. Cheers

Hey there - if you previously changed the vajs.dll using the link in post #1237 you need to revert it back to the original VAJS.dll that comes with the regular VA 1.7.3 install. Also here https://drive.google.com/drive/folders/1KPPOzt4fpg-UEK7YQEbGe1s8sukFqDSy?usp=sharing Hope that helps. Grtz.

Thanks @slicker that's good to hear. Would be helpful to get some more similar confirmations. CTD issues seem related to updating the plugin before having updated VA to 1.7.3. For people still experiencing issues after migrating: try with replacing your vaicompro.dll with the one from this link and PM me with results. https://drive.google.com/drive/folders/1KPPOzt4fpg-UEK7YQEbGe1s8sukFqDSy?usp=sharing Thanks

Thanks will have a look to see what I can reproduce. Update VA first is recommended. EDIT if you experience crashes after 1.7.3 update : *) Find this folder: Users\<yourname>\AppData\Roaming\VoiceAttack *) Remove the VoiceAttack.dat file *) After VA has loaded, re-import the profile VAICOMPRO for DCS World.vap

@Zyll Yep they're a great bunch, always very helpful. @t1mb0b Probably need to re-enable plugin support in VA options.

@Nightstorm OK that is a bug to report to VoiceAttack Support directly https://voiceattack.com/SMF/index.php?board=3.0 It appears to be related to new VA joystick functions. What you could try as workaround is disable plugin support, re-configure your joysticks in VA, and then enable plugin support again. UPDATE: The VoiceAttack guys, swift as ever, have come up with the suggestion below. All users if you are experiencing issues with VA 1.7.3 can you let me know please how this works for you so I can report back to the VA team. Many thanks EDIT: Snag has been identified, plugin update is on its way with hotfix for 1.7.3. Grtz

All looking normal here for VA 1.7.3. Thanks.

Haha that's great guys...much appreciated. Thanks for the kind words and Happy Thanksgiving! Cheers :beer:

The plugin doesn't use profiles for individual aircraft: you'll need to read the documentation. Grtz Sent from my SM-G960F using Tapatalk

That's a VA beta version. Use the latest stable 1.7.2.

@Skipper Thanks for the update. Compatibility testing with third party apps is always done with their latest versions. For SRS this is currently 1.5.4/1.5.5 https://forums.eagle.ru/showthread.php?t=169387 This has been tested to run in combination with VAICOM PRO, SSA, and Tacview irrespective of their order in export.lua. @Leysard Well that's for your mission script designer to sort out :D At the very least each command needs to be unique with a unique actionindex assigned. So that could be something to get checked.

Which version of SRS are you using? Thanks Sent from my SM-G960F using Tapatalk

@WOPR Can you enable debug mode and send me a PM with link to your VAICOMPRO.log. Would be interested to see if you have are any errors reported on startup. EDIT If no startup errors shown, try closing all apps and running a DCS repair. Can you also let me know which other plugins and tools you are running and check DCS.log for errors thanks. @waistcat No hadn't heard of that one yet. Game audio stream management is done in DCS so not sure if the plugin is directly involved here. Can you check if you get the same effect if you issue a command using the comms menu thanks. @Coder Windows speech learning algorithm is a bit more sophisticated than that, it will essentially learn and adjust each time it is exposed to your voice. So the more training and the more you use it in flight, the better.

@slicker You can add your own keysend commands to the VA profile directly. There is a category 'Additional' for that, but you can put them in any category doesn't matter. VA keysend commands do not involve the plugin so they will not show up in the plugin dropdown list. @BaLrOg Thanks for the update mate, not quite sure what you had there but good you got things sorted. @CoderX71 You can edit using the keywords editor: some stuff about it in the manual. :joystick:

@Don If you want you can disable the PTT squelch sound in plugin preferences. You could then add your own WAV sounds directly to the TX press/release commands in the VA profile. Grtz

Hey guys some comments The "Version of VoiceAttack" message is a known issue/feature https://www.vaicompro.com/faq.html No need to switch profiles with VAICOM PRO, but if you do: restart VA. Nearest ATC: if you speak too fast, recognition may miss your intended ATC name. The system then defaults to the currently selected ATC, which is automatically set to the nearest tower at start of the mission. Try with slowing your pace, listening for the soft recipient confirmation blip before finishing the ATC command. @Cain Cheers mate, good to hear :thumbup: Thanks

@Shepherd If Options is enabled calling e.g. "Soganlug,..options" shows the menu, even when menus are set to disabled. You'll need to press-and-hold the PTT key. If the menu doesn't show confirm it does using the \ key, perhaps double-check your TX button setup. @Rangoon OK will have a look to see if I can reproduce. Normally with Easy Comms off the dial should move only when the switch is set to OPER. EDIT: Confirmed: MAN setting not working as advertised atm. Thanks for flagging, will be looked into for fix.

Thanks for the update. All normal. I'll have a look, if your db is up to date simply ignore the message.

EDIT: As said: Manual page 27/30. Also in VA options try increasing your command weight to 90-100 range.

Yeah I've had something similar with one of these Black Sea airfields myself too. You can use the Keywords Editor to add your pronunciation to the speech dictionary or change the keyword into something more phonetic like Baahtoomee *). Manual page 27/30. *) UK spelling.

Hey guys just to chime in There's some references to VAICOM version 2.5.3: please make sure to test only with latest version 2.5.5. This was tested to work in combination with SSA/SoundModule, TacView, and SimpleRadio, (not Helios), in any order in export.lua. Of course if there's a snag feel free to PM, happy to have a look. Cheers /Hollywood