Greyman

Well this is what my config window looks like and it was the knob on the left that i was talking about, so if your screen looks like this, then you will need to have at least 2 PTT buttons assigned, to allow you to use both of the radios.

i wouldn't have thought so. as the Hornet uses TX1 and TX2 you should already have it available. If you look at the PTT page on the VAICOM config dialogue, for either aircraft, you should see that TX1 and TX2 are being used, as they both have now emboldened text describing the radio that they link to. Also, looking at your log again, it looks like VA is still listening to your MIC, even after it has said that listening is suspended. However, i am fairly sure that the statements it recognises in that mode will not be processed by VAICOM, which is probably why the press and release actions in VA are so important. There might be a logical explanation for this, but i'm afraid that i don't know what it is and what the fix might be. Hopefully, somebody else might know. Edit: ah, do you have SNGL selected on the 4-position knob on the PTT tab? Mine is set to NORM, which effectively allocates one dedicated switch per radio, whereas, if i understand it correctly, the SNGL mode allows you to use one PTT to control all of your radios. If that is how you have it set, then you can disregard my advice about using TX2

@Hollywood_315 - thanks for the latest update. it appears to have fixed the display/sound issues with the VHF radio on the Viper. As ED have yet to issue another update, i am taking it that you found your own way around it. nice one.

Yup, that looks more like my log and DCS still doesn't respond? Edit: Wait a minute though, i've just spotted a couple of differences that might explain your issue. You are using TX1 and although your setup might be different to mine, on my PTT display, the TX1 PTT selects the VHF radio. As the frequencies provided are UHF frequencies, you need to press TX2. That one is more likely to be the cause, but there is something else that looks a little odd, and that is that my commands, remembering that the log works bottom to top, are all fully enclosed within a press / release "bracket" for the PTT button. For example :- 14:18:59 - Joystick : 'Transmit TX2 release' 14:18:58 - TX2 | UHF Radio AN/ARC-164: [ Tanker ],[ ],[ ] Intent to Refuel [ ] [ ] 14:18:58 - Recognized : 'approaching for refuel' (Confidence 93) 14:18:56 - Listening resumed 14:18:56 - Joystick : 'Transmit TX2 press' yours, on the other hand, appear to be ordered slightly differently, in that your press and release "brackets" appear to be the other way round. I'd try using TX2 first and if that doesn't work, or if Hollywood doesn't come up with the actual solution, you might want to look at how you have defined the press and release actions in Voice Attack. I know that you say the Hornet works, which would indicate that there shouldn't be a problem with those actions, but your log does look a little odd. maybe just hold onto the PTT button for a little longer?

and this discussion is contributing what exactly?

No worries, but there must be something that you can do to get this working, as it definitely works for me. Looking at your VA log, there is something that looks different to mine and that is the fact that you appear to have both TX buttons pressed at the same time and although I know you say that you have disabled one of the channels, this might still be confusing VAICOM. Have you tried just using the button associated with the UHF radio?

@Pokeraccio has generously put this together and the download contains a pdf as well as kneeboard files that you can view whilst in the cockpit. https://www.digitalcombatsimulator.com/en/files/3305957/ It's really useful and should answer your question

The tanker will only reply if the radio associated with the PTT button that you pressed has been set with the correct frequency for that tanker. If you are convinced that you have set the right frequency, usually on the UHF radio (Comm 1), then make sure that it is the associated PTT button that you are pressing when you speak. By the way the numbers on the PTT buttons doesn't match the comm numbers, so you would need to press PTT 2 to speak on comm 1.

could it be that as you are dropping the bomb at the target waypoint and the target itself is closer to you than that waypoint, the bomb is not able to see the laser and is flying over the target? That might explain the apparent intermittent nature of the issue, as that would be affected by the direction of approach.

I've done RedKite's mission a few times, loading up on fuel at each of the 3 tankers, by flying between them, in Texaco, Shell, Arco order, using Tacan to find the latter 2, so I know it works. However, I do just use the DED to set the TACAN up, as I am not aware how to use VAICOM for this purpose. Things to check are, perhaps obviously, the correct channel, including 'Y" has been set. Also, make sure that you have the eHSI in 'TCN' mode, usually with 2 presses of the centre button. It is worth noting that since the last DCS update, the distance to the tankers is no longer displayed, even on the X channel, which is how it should work. Apparently K135 tankers do not transmit range info or anything on the X channel As for selecting each of the tankers' radio frequency, it tend to use "Texaco Select", for example, and then "Request for Refuel", both while holding the TX2(COM1) PTT button. Btw, the mountains and range do interfere with radio comms, but no response should be replaced by a quiet/crackly reception and then a clearing message as you get closer and out of the shadow of mountains.

You do the turns, that @Mover says are done IRL, and it makes you feel like you are doing it right. However, I'd be amazed if that makes any difference, in DCS, to the point at which you suffer GLOC thereafter.

Perhaps check that those keys are not bound to a command that is higher in the DCS hierarchy, as I said in my post above. Any bindings in General or UI layer will override anything that you bind in the aircraft controls

i've had that message before, but i have never owned a trackIR. i'd just put it down to DCS mistaking my Rift for TrackIR, but as it didn't seem to have any other effect, i just ignored it and it went away eventually

Not at my PC atm, but as there is a control bindings hierarchy, where at least general and UI take precedence over any aircraft mappings, maybe check if you can bind the map control to something other than F10. I'd guess not, but maybe worth a look. Edit: it looks like you can display the F10 map with a key other than F10. who'd have thought it? Just go to the General tab, in the first drop down list on the Controls dialogue and search for "map". You should find a row for F10 Theater Map view, which will have F10 as its keyboard mapping. Just clear that and select another key or switch and your F10 binding in your aircraft should now work.

There is something odd going on though, as when I load one of the instant action takeoff missions, where you start pointing down the runway, I don't have any issues. I've even tried the take off with NWS off and on. As the issue only appears to happen when I've cold started, could it be something to do with not moving the flight controls around enough and "warming them up"?

Yup, I turn off the NWS at around 70kts, with my nose pointing straight down the centreline, and yet I still often need almost full rudder to stop the aircraft leaving the side of the runway before takeoff. My crosswind rudder pedals have a small deadzone and definitely do not leave that deadzone unless I tell them to. I'm not touching the pedals at all until the plane starts to veer away from the centreline.

To display the Comms menu, you will need to press the PTT button that is associated with the radio, that has the right frequency set, and say "options". The menu will disappear if you let go of the PTT button, so you need to hold it in until you have completed your selections. Edit: I think there might be other commands that open the menu further down the hierarchy, but I don't use those, so you will need to look them up. IIRC, "other" or "other options" opens the F10 options.

Being able to realistically handle all radio comms, in all aircraft, whilst in a VR headset and without having to navigate menus, via a speech recognition tool like VAICOM Pro. Priceless

They'd need Slartibartfast for the Fjords ;)

Would the "co-pilot" in a Tornado largely fill the same role as the RIO in an F14? If so, there might be an obvious candidate for developing this beauty. :)

Whilst i agree that VR should mimic RL as much as possible and that a virtual pilot should not be able to do anything that a RL pilot would not be able to do, it might not be a bad idea to remember that not everyone will have the same level of physical ability and very few will have the flexibility of a RL figher pilot, especially when they get to my age. :) A major benefit of VR is that it allows people to experience things that they cannot do in real life and i don't see the issue with providing something that might help. If it's an option, it won't stop people choosing not to use it and as long as it isn't abused in MP, then there shouldn't be an issue.

When selecting Sharjah for an inbound call and setting the frequency, on either radio, the pilot says Novorossiysk instead of Sharjah and the reply is from Novorossiysk. The runway information appears to be correct, it just appears to be getting mixed up with the airfield name.

probably yes and i guess that might be corrected, in the fullness of time, along with the display issue on the TX1(which should be TX2) button. However, in the meantime, as it all appears to work pretty well anyway, that shouldn't create any major issues.

cool. ill check that out now then

Go to axis tune and there is a checkbox that inverts the axis. I usually have to do this for toe brakes, if not always, but other pedals might be different.