Greyman

As it has a command of its own, 'Scan Sector, Angels [0..14,5] [at;for;] [0.30,5]' it doesn't need to also be in the 'when i say' list of the main Vaicom Pro command collection. You therefore just need to make sure that you have a 'Scan Sector...' entry, like the one i have stated above, in your list of VA commands Edit: This should be imported from the VAICOM PRO AIRIO.vap profile, as per my first post.

It appears that you might have two choices. Either set the VoiceAttack option to start automatically when Windows loads, which would mean that it would be always loaded and ready to go, or create a batch file that loads VoiceAttack and then DCS World. If you choose the latter, then you would need to amend your current DCS shortcut to call the batch (.bat) file, instead of the exe that it will currently point to. Don't forget to start VA in admin mode though.

It appears that the latest manual has an inconsistency, between the screen print at the top of page 44 and the text that goes with it. The text suggests that there should be 6 AIRIO commands in the extensions whereas the screen print only shows 4. This screen print might have been amended recently, as i don't recall this inconsistency when i installed AIRIO, just a couple of weeks ago, but that might just be my crap memory. If i were you, i'd import the 'VAICOM PRO AIRIO.vap' profile and make sure that you have copied all of the extension commands to the main VAICOM Pro profile, as per the instructions. You shouldn't ever need to create your own AIRIO commands.

Then can we take it that the "last update", in the OP, refers to the last update of DCS and not the last update of Vaicom Pro?

I suspect that as Vaicom does NOT navigate via the menus, the commands are not recorded as part of the track, which means that they will not be played back. The DCS track system, in short, effectively records the starting position and then applies a recorded set of commands that the pilot had given, during the session, to figure out how the aircraft should behave when the track is replayed.

If you have any overclocks applied to your PC, maybe try disabling them temporarily, to see if the issues still occur. It might not fix your issues, but at least it would rule it out as a possible cause.

Are you sure you don't have any other apps running in the background that might be intercepting your hotkey presses or taking undue control of your mic? Maybe have a check of task manager, to see if there are any unexpected apps running and maybe temporarily remove any that you don't absolutely need, before trying again. Programs like Asus Sonic Studio have caused me some issues in the past, albeit not necessarily with VA. It must be something pretty obscure, with just a few peeps getting it.

Maybe try a reset of the lua files, using the appropriate checkbox on the reset tab, might do the trick??

Just as a 'by the way', it looks like Heatblur are going to eventually be allowing more current menu-only commands to be accessed via control bindings, which might make life more straightforward, depending on which commands you might be struggling to get across and which ones they might be allowing bindings for.

I'm guessing a bit, but do you have the 'Use custom DCS path' set, on the Config tab? If you do, have you selected the path in the field to the right of that checkbox? The error/warning messages appear to be expecting a string and getting an empty/null value.

Have you looked among the missions for the F18 or the F14, as unless I'm mistaken, the Supercarrier never had any of its own.

Let us know how you get on, as this does seem like an odd one. I've never had any loading issues like this with the Tomcat, apart from perhaps loading it with a 2-way switch set to enable active pause and then watching the carrier sail from underneath the aircraft. :)

Do you have the DCS option to synchronise controls set? If it is set, the aircraft should adopt all of your control settings on loading, which is probably what you need. I'm guessing it is clear, forcing you to move your axis controls, after loading, to get to the state you want.

Just as a suggestion, maybe try "approaching for refuel" and "complete and rejoin" for the two examples you have given.

Great news

As @Svsmokey said earlier, if your 2d DCS window sits above the windows taskbar, when you use your mouse to change a control, possibly low down in the cockpit, you might inadvertently move the focus away from DCS. McAfee also has a tendency to steal focus, when it gives you one of its countless renewal reminders, about 3 months in advance of expiry. :)

Also, you can specifically state the DCS window as the target for VoiceAttack, instead of the active window.

Well it popped up for me yesterday, when I had clicked the yellow-highlighted FINISH button, so unless something has changed since then, I don't know what is going on,

It's good to hear that you've cracked it. Now get back to concentrating on flying that Tomcat :)

have you tried resetting the lua files via the reset tab?

I've just purchased the F14 Tomcat and have been having lots of fun, in a sort of masochistic sense, up until now, trying to learn to fly it onspeed. Despite my apparent ineptitude at flying onspeed however, i do still appear to be able to get down on the deck in a single piece, which should at least provide the LSO with an easier target for their less-than-complementary comments. I just need to practise more and git gud. I'm loving it. Thank you.

Having just experienced very similar, if not the same, symptoms, I have apparently sorted it by resetting the lua code, on the reset tab. Maybe give it a try, if you are still looking for a solution.

By George, I think I've got it. It looks like resetting the lua code has done the trick, as i can now get the command recognised, with a log that looks just like yours.. Most odd Thanks for all of your help

I'm saying "two five two", but as you say, there are no spaces between the digits as there is with your log. I'd assumed that as being a symptom of the unrecognised reporting.

Well, I've just checked through the instructions for installing both VP and AIRIO and do not appear to have missed anything. I have also reset the keywords, with no apparent change to my issue. Is there anything else that might prevent what looks like a perfectly valid command from being recognised?