Hollywood_315

@Arakahn Great stuff! +rep inbound. Obviously this will be permafixed in plugin 2.5.4 version. @Sanatog To test it will be interesting to check if with these missions there's a difference in behaviour between calling a specific recipient unit e.g. 'Chalice,...Request Picture' vs. e.g. just 'Request Picture' which reverts to the default/selected recipient unit in the category. @Bucks Haven't seen that before but perhaps others have, your Windows Application log may shed some light. @mobua The plugin gets the DCS install path from Windows registry. If you installed DCS on C: orginally and then later moved it to another drive manually you can get this situation. You can do one of these things 1) change the registry entry to the correct install path 2) put the folder path where you placed DCS in the Include Custom Path field in the plugin config window e.g. 'G:/Games/' 3) install lua files manually (p33). Sent from my SM-G960F using Tapatalk

Ok so to summarize status the plugin works normally with all modules in 2.5 and 2.5OB both with easy comms on and off. - Exception FA-18C in OB with easy comms off, caused by the change to the Hornet comms system. It 's being looked into, use easy comms on for now as workaround. - Potentially a bug with Multi-to-Single, to be further investigated. Cheers Sent from my SM-G960F using Tapatalk

PM sent. Sent from my SM-G960F using Tapatalk

Thanks all @greyman It will depend on your speech timing. If you leave sufficient micropause Two will be recognized as the recipient else it will revert to the default i.e. Flight. You can practise with Audio Hints to get used to the rhythm. @Sanatog OK so if I understand correctly things work normally just as long as you don't use the M2S option. That would be a separate issue. You could try disabling Operate Dial to see if it makes a difference. @Luke Sounds good thanks for updating. Re the red line you need to update your VA profile using the FINISH steps, see manual. @Arakahn They need to be both the same number and refer to the Hornet's Intercom device ID. To know what this has now become (was 38 before) you'd need to dig into the cockpit scripts devices lua in the Hornet mod folder. But given the SRS numbers I've seen 37 and 41 would be inspired choices to try a quick test with. Sent from my SM-G960F using Tapatalk

I cannot test myself atm. Though not impossible it seems unlikely that comms changes were made by ED other than to the FA-18C module. To confirm this, users who have things working normally for other modules in OB are requested to report. As general guidance if you experience issues after a DCS update the plugin auto-restores lua code but only if 'install files manually' is not checked. Always test with easy comms on first. Carefully inspect your lua files (p33), remove any code blocks from previous versions and/or do a DCS repair if needed. Double check VA runs as admin, look at lua integrity on startup in debug mode and in case issues remain check your DCS.log for clues. Hope this is helpful. Grtz Hollywood Verstuurd vanaf mijn SM-G960F met Tapatalk

Thanks for this Brun. There seems to be a change in device numbering i.e. 38/39/40.. If in VAICOMPRO.export.lua you find the line refering to the Hornet PerformClickableAction command you may have some success by changing the number used there. Grtz @Bear looks like you need to just complete the command with correct keywords e.g 'Two...Radio Check' or 'Darkstar...Request Picture'. Have a look at the reference tables and send me a PM if you need more help. Verstuurd vanaf mijn SM-G960F met Tapatalk

Hey guys. Thanks for pointing out the FA-18C issue. It seems ED made another change to the Hornet comms system. Since I'm away I cannot verify details and address the problem at this time. If easy comms ON does work I suggest to use that as a workaround for the moment. If it doesn't, then perhaps lua savvy users can do some tests to come up with a fix, I'm available on PM to answer specific questions. Cheers Hollywood Verstuurd vanaf mijn SM-G960F met Tapatalk

OK thanks for flagging, this hasn't been raised as an issue by other Huey users. Will have a look at some point. If you're very keen about it you can manipulate the profile to have both stages trigger the single TX node for SEL/AUTO. The menu headers do not influence their functionality.

@Highway Turns out this is not an easy thing to fix, but it's on the todo list. @m4ti140 For 1) you can use the exposed variables to tweak your VA profle, see last page of the manual. This is a PRO feature. For 2) you could make use of the Single to Multi mapping which maps out the individual radios separately including intercom (also a PRO feature). Need help with this just send me a PM. Re 3) you can assign any key(s) / button(s) you like to the TX nodes by editing the VA profile. Two updates in the 'known issues' category: *) Most users will know this already but the Instant Select feature does not work for the F-5E Tiger II. This is because of the specific way the radio was modelled in this module. The Select command can be used to switch recipient in a category. *) There are some reports of users with the Elite Dangerous plugin EDDI having issues with keywords training mode. Disabling EDDI solves this. It's being looked into. Grtz :joystick:

@SilentGunner13 You may want to check and clear some of your keybinds in DCS config. @Sanatog Not sure about that one, have you tried to call 'Flight,.. Select' ? Check if the frequency/radio changes. If there are more than one freq/mod associated with a recipient it may pick the default. @mdee Doesn't look too happy, but if all works fine then no worries. @Tricky It should work with easy comms on or off, no special setting needed. You can check on the PTT page if the setting is correctly recognized and try with a different MP server to test. @Nanny Thanks for updating. Re: SRS Yes could be that setting, perhaps test a bit more with that. @IchDien @rb05033 I'll see what I can do with that one on a next update i.e. 2.5.4.

@hipp55 The log shows your Sonic Studio app is conflicting with VA, try disabling it.

@rephiled There is no F-18 specific profile for VAICOM PRO. You need to import the 'VAICOM PRO for DCS World.vap' profile as explained in the installation instructions. The plugin uses only this single profile that covers all DCS modules including the FA-18C. Can you check again the instructions in the manual and refer to my PM if you need more help. Grtz

@Quax OK sure. So here's the summary You can add as many of your own voice commands to the VA profile as you like, e.g. to raise/lower the gear and other non-comms stuff. VAICOM PRO's exposed variables are there to, if you want, make your own added voice commands act differently depending on the active module, easy comms mode, dcs version,.. You need to use a TX node for PTT when you use your added voice commands. This will make sure the variables are synchronized. TX6 (AUX) is recommended. To test with this, edit the VA profile and add a new logwrite (Other-> Advanced-> Write a Value to the Event Log) to the TX6 Press command. In the value field paste the complete token name including the brackets e.g. {TXT:vaicompro.serverdata.currentserver.dcsversion}. Now, with a DCS mission running, if you press the TX6 key you will see an entry popping up in the log with value '2.5.0' or '2.5.2'. You can proceed from there to add your own advanced commands in VA using Conditonial Blocks ('If {TXT:vaicompro.playerdata.currentmodule.name} equals A-10C',.. etc.). Hope this is helpful. @rephiled Which profile are you trying to import? PM inbound.

@hipp55 VoiceAttack must be running as administrator and VA Plugin Support must be enabled. Check the Install Notes. @Quax Works fine here. Can you check again and if you have a specific issue send me a PM thanks.

@Brun Assuming VA runs correctly as admin and your Windows account has sufficient UAC admin rights, this may be a problem with your export.lua. Try deleting it and restart VA. If issues remain inspect DCS.log for clues and disable other apps as required to test. PM me if you need additional help. @Mojo By editing the VA profile you should be able to easily add a spacebar Keypress to the TX3 Press command. Have a look and let me know how it goes.

@Colmillo In future updates you will be able to delete individual imported items. For now you can clear the keyword database using the Reset page. Grtz

@Knight At the bottom right after Plugin Support Enabled is a line relating to *chatter* that shouldn't be there. Can't read what it says atm because of the red circle in front of it. It looks though as if you have some press-and-hold button inadvertently triggering chatter during initialize. Try disabling joystick input (the gamepad icon) and restart VA. Then edit the profile and change the chatter button. If that doesn't fix it catch me on PM and we'll get it sorted. EDIT: Solved. @tom_vn All cloud-hosted stuff, download works ok here. Perhaps some temp hikkup: suggest to try again.

Hey Nanny Interesting, never heard that one before. Let's see what we can find out. The log looks just fine except that the line Current profile string does not match database suggests you need to update your VA profile by following the FINISH steps in the editor. Probably unrelated but can you do that first and then test again. I'll catch you on PM with a few more questions. Grtz

@filthymanc Seems to be some peculiar MS Windows snag, this link may be helpful: https://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/speech-alternatives-panel-comes-up-every-time/985becaa-a14d-4741-a16b-485026081b08

@Colmillo just replace your existing dll with the newly downloaded one and restart VA. @FF good idea, will be adding latest build ref to post #2.

Now fixed for FA-18C cold start, Easy Comms ON and OFF. Use the latest plugin dll from https://www.vaicompro.com/downloads.html @archer Cheers

Enable debug mode and check the VA log window on startup. Verstuurd vanaf mijn SM-G960F met Tapatalk

I cannot reproduce any difference between config window or closed myself. Make sure you are using latest plugin build i.e. 180609-03. However regarding Cold and Dark mission I did find there is currently a snag with the FA-18C when starting cold on the ramp With Easy Comms ON: talking to crew in a cold bird does not work properly at this time. With Easy Comms OFF: before you start talking to the crew switch on the battery first and things will work OK. I'll look into this and come back with a fix. @archer seems you're using the wrong radio, try using VHF instead. Grtz

@Colmillo Try again please with the latest dll from the website https://www.vaicompro.com/downloads.html

@Neal Plugin 2.5.3 has been tested to work in conjunction with SSA. Simtools however is not on the compatibilty list, looks like perhaps this may be causing your issue. PM Sent. @Colmillo Thanks I'll have a look to see if I can reproduce. UPDATE: Now fixed in latest build, replace your current plugin dll with the latest one https://www.vaicompro.com/downloads.html Grtz