Hollywood_315

Yes you select the custom DCS folder option, click SET to locate your DCS World program folder and restart VA. If you have issues try deleting / renaming the export.lua file in Saved Games.

You need to observe a small pause between receipient and command: look on page 15 of the manual.

@mdee You could try if pressing the Reload button on the Keywords Editor tab resets the message. @Ben With the latest plugin build (2.5.5 181105-01) you can use the custom DCS path option to directly locate your Steam DCS World folder. In other news: this build also has an offline mute option for Chatter, meaning that when this option is selected you will hear chatter only when a mission is running in DCS. Existing users will receive this new build automatically. Grtz

@steve He may want to verify if VA is running as admin and/or get the latest plugin build from the website directly. Mods are not on the list of supported modules: depending on how it was constructed a mod may work with VAICOM PRO, but there's no guarantee beforehand. Perhaps others have tried with this one. @Ed It's more that the plugin doesn't offer that voice command by default, enable the Extended Command Set to use it across all modules. @bodecker @Biga From the website FAQ page : @Kirin Allright, thanks for updating.

@Muskoka OK. So, again to conclude, none of this has to do with VAICOM PRO. You would have had the same experience with L39 and ATC if you had used the comms menus instead of the plugin. The documentation presumes basic understanding of DCS general functionality. Thanks

OK thanks for clarifying. I think you're referring to defining radio presets in the Mission Editor. Several aircraft type (such as WWII fighters and others) have a fixed preset-based radio system, so the frequencies that can be used during the mission are determined during mission build for these aircraft. Other aircraft don't have fixed presets but instead can be freely tuned during mission time. This is simply the way these aircraft module radio systems work in DCS, again has nothing to do with the plugin. If you are frustrated about the way DCS is designed thats's fine but in that case I'd really appreciate if you start a separate thread about that and direct your complaints to ED to avoid things getting mixed up here.

Hey Muskoka You seem pretty confused, however VAICOM PRO has nothing to do with all this. It doesn't work at all like you describe, and users don't have to manually set up anything. The plugin automatically reads all ATCs in the mission, including their callsigns, frequencies, regardless of how they were set up. Your posts here are a bit hard to follow for myself but they seem to point to a lack of understanding of ATC flows. On the manual page 34 there's something about that i.e. which commands should be issued in which order during takeoff, navigation and approach/landing stages. You have to issue the right command at the appropriate time in order to get a response from the tower. Needless to say you also need to have the radio tuned correctly. Suggest to spend some more time learning. Grtz

Some PM's inbound. Grtz

@Muakoka OK seems you are trying to use a legacy DCS install i.e. 2.1 openalpha. The plugin auto-installer supports current versions i.e. 2.5 and 2.5 OpenBeta. Install paths are read from registry, so if you manually renamed or moved things around, lua files can end up in the wrong places. Check if the folder for 2.5 in your log (i.e. on G:) is correct. In this thread from post #805 onwards there are some suggestions to fix. Sent from my SM-G960F using Tapatalk

For people curious about RIO functionality: it has my attention..:D

Hey Whiskey Looks like your lua code is somehow not all properly in place. Things will depend on how you have moved your DCS install to another drive. The plugin looks for path entry in Windows Registry but apparently it cannot find a valid entry there. BTW doesn't matter which harddrives are used. Short of a DCS re-install (which would fix your registry) I suggest to enable the custom parent folder option as a workaround, put the base folder in there using backslash notation e.g. 'E:\Mystuff\' if your install path is 'E:\Mystuff\DCS World'. Check it out and PM me if you get stuck.

@Nickentik OK thanks for the heads up. @Morten DCS 1.5 is no longer current and the auto-installer will not recognize it. You could e.g. use the custom parent folder option, or install the luas manually.

@KC When using the custom folder option with auto-install, make sure to specify the full parent folder path for the DCS World program folder using backslash notation e.g. 'E:\steamapps\'. Sent from my SM-G960F using Tapatalk

@lapster, KidCharlemagne Use the plugins automatic installer, if you edited the lua files try running a DCS Repair first. @rb05033 That will be the causing it. Try removing the database and config subfolders and then restart. @Tundra Sure, in the profile you could e.g. add a keypress to the TX press/release commands to mute/unmute Discord.

There has been no change to the DCS comms files structure. Use the automatic installer, switch on debug mode and if no errors are shown on startup and the correct DCS install path is shown you'll need to inspect your export.lua there's most likely some other app preventing proper execution. DCS.log can provide clues. Sent from my SM-G960F using Tapatalk

@sobe Well normally it's good that you don't see menu's. If you want to look at the menu, press and keep holding PTT while calling 'Options'. @Bucks Yeah let me have another look a that. I believe there was some lua-illegal character thing going on. You should be able to at least connect normally now if Import F10 Menus is set to off. Grtz Sent from my SM-G960F using Tapatalk

update notes Couple of things to note regarding the revised radio handling in the latest build (180910-01). Subtle differences but good to be aware of (below assumes A-10C but same goes for all non-FC3 modules) 1) With Easy Comms ON, you now have wider tuning- and communications capabilities across radios beyond just the default options. For example in MULTI mode with Easy Comms ON try contacting an ATC using TX2 PTT for UHF radio. If the ATC has a transponder on UHF, the plugin will now select the frequency on UHF radio instead of trying to revert to default VHF AM. Similar if you'd have a JTAC engagement on VHF AM using easy comms, etc. 2) With Easy Comms OFF, you now have better response when using non-default radios in SNGL mode. If your AWACS for example is tuned on UHF or FM radio instead of default VHF AM, SEL/AUTO will now switch to the correct radio for the called recipient. With this the plugin should now provide correct response for all PTT mode / Easy Comms scenarios. Have fun checking it out. :joystick:

@RogueSqdn Check last page of the user manual @sobe Assign the joy buttons to the TX's in the VA profile. Do not use these same buttons in DCS config. @Biga TacView entry causes the issue, try with removing it from your export.lua and test again. EDIT make sure to run tacview latest version ie 1.7.2.

@alien Yes this is normal, the menu system reacts to dialog state changes in the same way as when not using the plugin. Menu suppression is done with the Disable Menus option: even with menus disabled you can still access them using the Options voice command.

@sobe You should have received the automatic update to build 180910-01. With NORM/MULTI mode in the Hornet TX1/TX2 are mapped to COMM1/2, so use those. Also inspect your keybinds in dcs config to make sure they don't trigger anything else. @Zyll Assuming Import F10 Menu is off not clear what the issue with that particular server is atm. Funny characters in the mission name could choke the json encoder so check that. Also look for any error messages in debug mode and go through your dcs.log perhaps there's a clue there. Sent from my SM-G960F using Tapatalk

@sobe Should be ok with today's update. Shortcut disabled = command doesn't use speech ie only key/button trigger. Sent from my SM-G960F using Tapatalk

@Pancake There's been no code change in the plugin's core call handling routines, so would seem related to a change on your setup. From the log it looks as if the PTT button is released before the command is finished: hold it until complete. Re registry entries: if the paths are off, lua files may end up in the wrong places. Use auto-install and check in debug mode if the paths are correct. @Zyll For MP the server must have Player Export enabled. If data connection does not come up ('----')you can try with disabling the Import F10 Menus option. @Jokese If you get no data connection in SP check the following 1) VA is latest (1.7.2) and running as administrator, 2) Try disabling other VA plugins, 3) Try running a DCS repair, 4) Some other app may be blocking proper export.lua execution: inspect the export.lua file in Saved Games and look in dcs.log for clues.

Hey Snacko In 2.5.5 that's already done. Cheers Sent from my SM-G960F using Tapatalk

Could be a bug, I'll see if I can reproduce something. Can be ignored in any case. You could try pressing Reload before the finish steps, that might clear the message, or do a db reset via the Reset tab.

Lolz... :D @smokey look here: EDIT: ah you found it already great @Nightstorm Thanks for the generous comment mate, appreciated :beer: