Uh-1H FARP radio issue

Hi everyone,

I am having trouble with the mission I will attach below.

For some reason I don't get any audio when talking to the FARP. It seems like the commands are getting through because I get updates on the F10 menu. For example, if I ask for startup clearance the next time I go to the menu I get the option to ask for take-off clearance.

However, I don't hear my own voice or the voice of the controller coming back. I also don't see the subtitles for what would normally be said. I have 'easy comms' turned off.

The FARP is on UHF channel 2.

I can't shake the feeling that I am doing something wrong in the mission setup but I don't know what it could be.

Can anyone please help? It's driving me crazy!

Flight-0001 D04 0900H 20C CLD7-10 AT3600 WND14 FRM170 Troops Pickup and Dropoff.miz

Make sure that you set the radio to the proper frequency and the radio selector knob to the correct radio. That may seem absurd, but if you have the radio assist options on, you can successfully transmit to them without having set up correctly, you don't hear the response, though.

Thank you for the quick answer Kang! , I have the distribution panel rotary set to '2' and I've set the frequency in the UHF radio by using the presets AND manually.

Does the mission work for you?

I admit my earlier reply was a bit of a bolt out of the blue, because that is a problem I have once in a while. I tried the mission now and I don't seem to get any of the radio chatter. Neither the pilot nor the FARP response, just the response subtitle.

Thank you, it's good to see that it's not something particular to my system.

Now I hope someone out there has an answer!

Just tested and found the same problem. In fact, none of the ATC comms were audible on any of the radios regardless of recipient (FARP Perth, Gudauta, Sochi, you name it), but with the correct frequency tuned in, the comms menu indicated that the FARP had granted my startup request.

Sending commands to wingmen was audible on all radios, even if the wingman in question didn't even exist.

Looks like a problem that's not related to the mission itself, though further testing would have to show that. I don't have the time to do proper testing, but for now I just think the mission itself is not at fault. ;)

Thank you Yurgon!

Ok, I worked out the issue, I wasn't setting the aircraft callsign properly!