hornblower793

Did you use to have a stable build of DCS installed (I am guessing so from the fact that you have a DCS folder). I wouldn't expect it to be having any impact, but might be worth renaming it and retrying Also, have you tried with different airframes / missions?

I can't answer your second question because I don't use SRS but the answer to the first one is that it comes up as a bookmarked page within the existing kneeboard so your existing commands will work as well

I can confirm it works fine for me with Texaco1 and Texaco2 on 251.600 and 251.650 and just using Approaching for Refuel. Both tankers can be called

In your first post you said that you followed the trouble-shooting steps - has this included the following? 1. Deleting Export.lua in your saved games scripts folder and letting Vaicom recreate it 2. Running Vaicom with debug on to see if there are any additional clues shown in the log file Also, could you confirm that there is only one DCS.openbeta folder in Saved Games If you go into the Vaicom config > Editor tab how many commands are shown as present? If you then click the test button does this give a message in the log that the Profile matches the database (this may take a bit of time to appear depending on the number of commands you have)? Also, do you run additional add-ons such as SRS?

Are you running easy comms on or off? Your log shows that you are getting responses from ATC for both the Taxi to runway command and for takeoff I know that you had to make several requests to take off but that is a function of the DCS ATC at the moment (I get the same). If you stop at the holding point short of the runway it will not trigger a response and I get the same until I am on the runway which is why you have the last two entries together. The first is because you are on the runway so it is not clear, the second is because you are on the runway for takeoff (it is a DCS quirk). Did you hear responses to either of these requests / get text in the top left of the screen unless you have turned screen text off in the Vaicom options? I then notice you got no response to the inbound calls - I have just hopped in the same mission and did get a response to my first Inbound call straight after takeoff but need to know whether you heard the responses from ATC which are showing in the log

If you don't have AIRIO it might be worth downloading it and putting the DLL in the Extensions directory under Vaicompro (you don't need to register it). if this doesn't fix anything (or you already have AIRIO) could you turn Vaicom debug on, try the Take commands in game and then post the Vaicom log here

If your commands are not being recognised have you done voice training (page 39 of the manual)? This can take some time but will make a huge difference If the Finish button is yellow then it is always a good idea to press it and follow the steps that are given in the message that appears. Away from PC - sent using Tapatalk

Glad it is working Away from PC - sent using Tapatalk

Which version of Vaicom are you using? There was an issue with the Take commands not working before the last update if you didn't have AIRIO installed. if you are on Vaicom 5.22 then upgrade to 5.23 to remove this

As @sthompson said, the issue appears to be with your Vaicom database (the screenshot of the Editor tab shows 0 commands in the database). If you click on the command phrase dropdown, are there any entries in the list? I think you need to reset your keyword database as follows: 1. Go to the Vaicom Reset tab, select Keywords (and nothing else) and then hit Master Zero 2. Go to the Editor tab and check that there are now a few hundred commands counted (box at the top left of the screen) 3. Click on the FINISH button and follow the steps to sync with the VA profile If this doesn't do anything, you may also want to reset the Profile on the Reset page

Once in the cockpit of a plane, if you open the Vaicom config PTT tab does it show you the correct module? Also, could you start up VA / Vaicom with the Vaicom debug option turned on and post a copy of the log file here <Voiceattack install directory>/Apps/VAICOMPRO/Logs - it might help diagnose the issue

I do, but haven't really flown it for some time (been focussed on others). Last time I flew it Jester did tune for me because you are changing the 'when i say' part of the command, so creating an alias. Page 43 of the manual explains the commands. You can either copy one of these and then change it, or edit the command and change the words. I will be on my PC later and can provide a step by step guide then if needed Away from PC - sent using Tapatalk

Which mission are you trying, and which carrier are you trying to land on (i.e. Is it a Supercarrier or the Stennis)

Radio tune is not in the keywords list in Vaicom, but should be in a separate section in the VA profile list along with Tacan tune and a few others. I can never get Tune recognised reliable (like you Microsoft thinks I am saying 2) so I created a version of the command in the VA profile that is Radio Freak and then the numbers and decimal point. I also use 'oh' instead of zero and dot instead of decimal

This came up some months ago for a Helios issue sounding the same https://forums.eagle.ru/forum/english/dcs-world-topics/input-and-output/vaicom/281469-vp-jester-wheel-while-using-helios if @Hollywood_315 doesn't respond here I would either PM him or drop an e-mail to support@vaicompro.com and he will be able to resolve

When you are talking about the radio staying dark what exactly are you referring to - is it on the PTT tab of the Vaicom config or in the cockpit? From your description I would guess it is the F-18. If so, and it is the radio on the UFC you are talking about then this is DCS controlled. Vaicom should show you the frequency you are using on the config PTT tab when you have a TX button pressed

The buttons at the bottom left of the kneeboard are a new DCS feature along with the ability to resize the kneeboard. They came in the OB update on Wednesday

It probably isn't waiting. I have been looking at my logs more over the past few days and I also get that if I continue to hold the TX button down after a command has completed successfully Away from PC - sent using Tapatalk

Glad to hear it is working:thumbup:

No idea at all, but you are also pulling in a lot of F10 commands (you can always use the Options command while in flight to view the DCS comms menu and then use Take 1, Take 2 etc to select entries from it for mission specific commands). I think it is probably worth trying a reset of Vaicom - this won't remove speech training you have done but might remove any custom commands you have added so backup the list first and then: 1. Turn off Import F10 Menu from the Preferences tab and Auto-import new modules from the Config tab 2. Use the Reset tab to clear and reset the keywords database (do not check any other options on this tab) - you can always try steps 3 to 6 first without this step and see if it resolves the issue for you without a full reset 3. Export the profile from the Vaicom config (Export button on the Editor tab) 4. Import this profile into VA 5. Go back to Vaicom config Editor tab, click on the FINISH button and follow the steps 6. Close down VA and restart and see whether the log messages have gone 7. Try DCS You can then turn back on the Import options if you wish

I have just changed the values of the Bingo call up and down in both the A and the B and got Joker calls each time

Could you try running without this module in and see if it makes a difference. Also, do you have the NS430 addon as I know @Hollywood_315 has stated there are compatibility issues with this

OK - do you have debug turned on in Vaicom - if not, please could you turn this on. Once on, please could you close VA, restart it and then post the Vaicom log file here. This file can be found in <VoiceAttack install directory>\Apps\VAICOMPRO\Logs

All - while we will try to help all users, this thread is now very long and it is easy to miss things. Vaicom now has its own sub-forum and it is easier for us to identify new requests for help if you could look through / search the existing threads to see if there is already the same or a similar issue reported. If there is then please add to the thread if any suggested fixes do not work for you. If your issue is not already covered please start a new thread with a meaningful title

Once you are in the cockpit at the start of a mission, use LCTRL+LALT+C to bring up the Vaicom config screen - does this show the correct module, PTT mapping and state for Easy Communication?