Greyman

Thanks for that @lxsapper I did follow that part of the installation instructions and my profile looks just like your screen dump. I also have the extended command set checkbox checked on the preferences tab, but i will go back through the instructions and see if i might have missed something.

That's awesome thanks. As my issue appeared to be that i was getting a "." instead of "decimal", i have tried saying "radio tune 252 literal decimal numeral 5" and that appears to insert a correctly formatted frequency into the VA log. However, it is still marked in yellow as unrecognised. There might be something else going on, perhaps in my settings, that is making this such a PITA. See screenie of my VA Log below Edit: btw, how do your radio tune commands appear in the VA Log? As "radio tune 132.55" or "radio tune 132 decimal 55" for example.

252 decimal 5, for example, doesn't have any "0"s or "O"'s included Should i need to say "Radio Tune 2 5 2 decimal 5 O" then, as that doesn't appear to work either. I just get "Radio Tune 252.5 O" or "Radio Tune 252.50" depending on length of pause before saying "O"

zero is registered just fine, along with all of the other digits. The problem is that the full sentence, "radio tune 252.5" is not being recognised and apparently couldn't be unless it is formatted as "radio tune 252 decimal 5". The problem appears to be that MS speech recognition will not create a sentence in that format, as it insists on forcing the ".". I have tried leaving pauses, in various places, but that just results in VP thinking that i have finished and not recognising what i have said. Saying the command quickly just results in the xxx.x format being applied.

I don't have a problem with it registering the words "radio tune", but it appears to be marking them as "unrecognised" due to the format of the numbers that follow, which always come out as "xxx.x" and not the "xxx decimal x" that VP appears to require. I've added "decimal" to the speech recognition dictionary ad it registers that on its own, but speech recognition always seems to be converting it to a "." when in a number sequence. I've also tried other words, to replace "decimal", that shouldn't be converted to a ".", but MS speech recognition still does.

https://forums.eagle.ru/showthread.php?t=242134 is also a great mod, especially if, like me, you play in vr and have a crap memory. it lets you retain the 9lines, or anything else for that matter, on screen

Maybe try this :- https://www.digitalcombatsimulator.com/en/files/3304451/

Do you have 'Allow Options" checked on the Preferences tab?

I have just purchased the AIRIO extension and like a lot of peeps on here, I am really struggling with getting 'Radio Tune' recognised, apparently due to the sensitivity of the Windows Speech Recognition software to floating point numbers. If you leave a pause between "radio tune" and the first digits, the command is unrecognised. If you leave a pause after the first 3 digits (the integer part), the command is unrecognised. If you don't pause anywhere, you get something like "Radio Tune 252.5" and that is unrecognised. I have tested my pronunciation with notepad and MS Speech Recognition and although i can get something like "radio change 252 decimal five", that is by leaving the sorts of pauses that cause VoiceAttack/Vaicom to end its recognition and declare it as unrecognised. It sounds like some users have managed to find a way to work around this sensitivity, and I'd be really interested to watch a video of them doing so, but surely this shouldn't be so hard. Why isn't it possible to just feed a frequency to DCS, in the format "252.5", as this is really easy to get recognised, and if it isn't why can't Vaicom just reformat it, replacing the "." with " decimal " before doing so? Maybe just forget the decimal on input and assume that it will always follow the 3rd number?

Probably Thanks I have been using DCS for years and have never even noticed that view, let alone used it. I guess i must have blindly pressed alt f1 when searching for ctrl 1, with my headset on. ;)

Does anyone know how to get the cockpit graphics back, in the DCS F1 view, as mine disappeared after making a selection on the Jester wheel? I fly in VR and although the shadow of the aircraft was clearly visible on the tarmac, i was apparently floating above the runway.

I try to reduce the times i have to look out from under my VR headset, so will be trying "Plan A" and not using the radial menu at all, but should my pronunciation go off a bit, courtesy of a beer or three, the 'take x' option will be next

Will we be able to select the jester wheel options with voice, via take 1, take 2 etc. or will we need to use the CTR & num combos? Edit: never mind, i've just RTFM and found that it's the former. :)

https://www.digitalcombatsimulator.com/en/files/2400126/ - there may be others, in the user files, but i stopped searching after finding this one.

maybe. I'll do some manual tuning, taking care not to use the select command, and see if i get any joy. Maybe its something to do with the "tune on select" option, which i have checked ??? Edit: still the same, even without using "select".

I've never used Easy Comms, so your setup must differ somehow from mine and the others here that are experiencing this apparent inconsistency.

I've just tried the P51 near Kobuletti and found the following. 1. Nearest, Select and Kobuletti, Select are greeted correctly with a soft beep, after the first word, and a louder beep, after "Select. 2. "Inbound" is received with a beep, but nothing comes back from DCS, until i press the PTT button again. This behaviour appears to repeat, even after I have shut down VA and DCS and applied the usual update steps. There must be something different about the P51, as this doesn't happen in the F18 or F14. Edit: oh and i was pretty close, within 4nm, to Kobuletti when i stated Inbound

Just started a trial and selected the very first training mission. the aircraft does not appear to be connected to the deck of the carrier, as it just slides off the back, staying at the same altitude, as the carrier moves ahead. Looks like a bit of mission editing might be necessary? Edit: this is in OB by the way. Edit2: My bad. It looks like I have a TM Warthog Throttle switch set to active pause, from the last trial, and this was keeping the aircraft in this state when the mission started. Looked odd, but now it's all good. Sorry.

'Weight on Wheels' i.e. when you are on the ground or on a carrier.

remember there was an OB update yesterday, so make sure you have taken the usual steps, as that might explain the delay on comms. do the commands get sent when you press the PTT button one or two times after you've spoken?

Asus Sonic Studio can be a PIA too

Maybe there will be some inspiration for you, in the video at this link:-

In short, the second one. Although Vaicom (please note the spelling) is focused on the voice control of radio comms, if you want to control other aspects of the aircraft, like flaps, gear, etc, VoiceAttack does allow you to daisy-chain another profile(s).

From the VA log, is "startup" not being recognised with a sufficient confidence level or is it being misinterpreted as another word(s)? Either way, maybe try opening the MS speech recognition dictionary and adding an entry for "startup" along with a recording of your pronunciation of the word. Alternatively, is it recognising the word "startup" and VP/DCS does not appear to be responding as it should? If this is the case, then it may be that the AIRIO commands are still to be copied into the Vaicom profile, using the Finish steps. Go to the Editor tab on the config dialog (ctrl-alt-c) and press the finish button, which will probably be highlighted in yellow. That will bring up a dialogue that will tell you what to do to to complete the process.

Symptom AIRIO commands not recognized / executed Cause AIRIO dll not installed Remedy Download from website Cause AIRIO not enabled Remedy Enable AIRIO (EX tab), restart VA and DCS Cause Keywords not updated in VA profile Remedy Apply FINISH steps Just to make sure that you had seen the FAQ, the above looks like it will provide at least a good start towards a solution. If none of the above works, if you could post a VA log in a new thread on the VP subforum, that would provide some clues as to whether VA is not recognising your spoken commands or whether there is a break somewhere between VP and DCS, once it has recognised the command.