Greyman

Yes, i now understand, but whether and when it can be done is a question, that I guess only Hollywood_315 will be able to answer.

For Case 1, there is a fair amount of text that describes the communications and when they should take place. For Case 2 and Case 3, the respective diagrams include indications of when to make the various calls over ATC. Maybe take another look

Will it possibly provide at least a starting heading for a Harpoon, as ships might be easier to spot on the radar?

Thanks and it looks like it was worth me checking. :)

Sorry if this one has already been asked and answered, but looking at the diagram for a Case II recovery, from the SC manual, which is apparently a mixture of a Case III holding pattern and a Case I approach, it isn't clear what the speed should be at the start of the Case I phase. In a normal Case I, the speed requirement leading up to the break is 350kts, yet the descent from the holding stack, in a Case II recovery, is at 250kts. Should the break be started at 250kts, or should the aircraft be accelerated to 350kts before the break? My guess is the former, but I thought I'd check.

Unless the launching aircraft identifier is added, as a prefix/suffix to the station number, unseen to the pilot.

Vaicom Pro already automatically selects the most appropriate PTT buttons for each aircraft. For example, the Hornet just uses 2 of the PTT buttons (forward and down for radio 1 and radio 2 respectively on a WH HOTAS). The other PTT buttons are disabled. For the example above, are you suggesting that this might be changed so that you would be able to press different buttons for the two radios, than you might for any other aircraft with the same 2 PTT mappings or would you be happy with the aircraft specific defaults that VP already selects?

maybe check out nvidia's AI noise reduction software. it should be available to your RTX GPU. Apparently, it's really effective for cancelling out the background noise for mics

\o/\o/ Nice one \o/\o/ Now get to something relatively easy. AAR and Case 1, 2 and 3 recoveries in the Navy jet of your choice should be a breeze now. :) Good job gurus

Unless you fly in a very quiet room and don't "grunt" like i do when in the heat of battle, a hot mic might throw up some unwanted and apparently random commands. The Nvidia noise cancelling utility, on the RTX cards might offer some help on this, or at least i hope it does.

when you tried VSPX, did you reset all of the necessary settings, to make sure that you are not stuck somewhere between the two modes? From the manual:- Switching Between Modes To change between Default and VSPX modes, follow these steps: • In Preferences, (de)select VSPX option: you will see a pop-up. Press OK. • Follow the FINISH steps in the keywords editor to update your VA profile, • In VoiceAttack options put these settings as follows: Unrecognized Speech Delay VSPX OFF: 0ms. VSPX ON: 600-1000ms: 700ms recommended. Done. The green light on the editor page shows whether VSPX is activated.

If you load something like notepad, alongside speech recognition, and say the Chinese version of "Batumi", does it appear as text in notepad?

and maybe block "GTECH" in speech recognition, as that might be a word that you never want to use anyway.

If it's the request for aerial refueling that you want to add an alias to, then you need to add the alias to "approaching for refuel", but if you use a word that is already used for another command, then VA is very likely to choose that command before using your alias.

That's probably because "request refuel", as sthompson says, has already been allocated for asking the ground crew to refuel you, with Weight on Wheels, making this unworkable when at say 20,000ft. Maybe try "fill her up", "do you give stamps?" or probably something a little more sensible. :)

Here's another one. Do you have the 2 sliders at the bottom right of the CONFIG tab set to match your standalone and stable environment?

Sorry for clutching at straws a little, but better than not checking it and then finding out way later. :)

Could it be that there is an audio issue here as well as or even instead of an apparent disconnect between DCS and VP. Maybe check that your default windows output device and comms device are set correctly and maybe check the audio tab on your VA/VP settings

LOL, and here's me thinking that hornblower793 was just an alias for Hollywood_315 ;p

TX1-TX4 all relate to radios, different ones for different modules, that will only work when the radios are powered on, usually when the aircraft has been started up. TX5 and TX6 however, will work whether or not there is any power to the radios, so best to use one of these for the ground crew.

"Request takeoff" can be a bit of a funny one, as it appears to be context sensitive and so, when it is not the time for that command, DCS will appear to be ignoring you. Maybe try "request taxi to runway" or even "request startup" to get the ball running or taxi to the threshold of the runway before saying "request takeoff".

Maybe try adding the Chinese version of "Batumi" to the speech recognition dictionary, along with your pronunciation. Recognition should be pretty good.

It would appear that the "see you at 10" call is not required in low visibility conditions, which probably makes sense

Maybe go to Sound settings in windows and look at the device properties for your mic. There should be a test button, so press that and make some noise to see if it is working. Also, check that the mic in question is set as the default comms device

\o/\o/\o/ good to hear