Comms no longer work in F-18 or F-16. I'm at a loss.

[oldmanflan]

This is a strange one that I simply cannot figure out, no matter how much I mess with it. As of 2 days ago, I can no longer contact tankers or air bases and get a response in either the F-18 or F-16. It worked perfectly fine in each jet, up until yesterday. Changing frequencies in the jets using normal procedures (outlined below) successfully lock those frequencies in the cockpit comms displays and even change my SRS frequency as desired, allowing me to hear other players. So the procedures appear to be working as usual. But I get no responses from tankers/air bases anymore.

 

F-18 Procedure:

1) Click the Comm 1 dial to turn it on

2) Turn the comm 1 dial to "M"

3) Punch in my desired frequency to contact a tanker (256.000 for instance) and hit Enter. The frequency sticks on the display and changes my SRS to 256.000.

4) Hit "R-Alt" and "backslash" and use the function keys to contact the tanker (F6 - FX - F1)

 

F-16 Procedure:

1) Click the Comm 1 button

2) Punch in 256.00 and hit enter.

3) SRS is now changed to 256.000 and when I check the Comm 1 frequency it's solid on 256.00

4) Hit "backslash" and use the function keys to contact the tanker (F6 - FX - F1)

 

 

Both of the above scenarios previously allowed me to contact the appropriate tanker or air base on the channel (256.000 in this example). But now I cannot get a response from anyone.

 

At this point I'm worried there is something messed up with my game install as I know the procedures are not changed from when they worked.

 

Anyway, I know this is a weird one and I hope my post makes sense. I'm looking for any help/recommendations as this issue is pretty much making the game unplayable for me.

Edited November 20, 2019 by oldmanflan

[Frederf]

Don't use backslash. Use the keys appropriate to the control in the respective cockpit control which speaks over that radio. The phrase "AN/ARC-186" should appear for example in the F-16 above the F1. ... line.

[oldmanflan]

Don't use backslash. Use the keys appropriate to the control in the respective cockpit control which speaks over that radio. The phrase "AN/ARC-186" should appear for example in the F-16 above the F1. ... line.

 

Interesting. Thanks for the input. I hope this resolves it. I'll try in a bit. But, is this new from a recent update? The procedures outlined above worked perfectly fine for all AA refueling and air base inbound notifications prior to yesterday. Not sure when this changed.

[naizarak]

the server you're playing on probably has easy comms disabled

[oldmanflan]

the server you're playing on probably has easy comms disabled

 

Hmm... I'll check that. It's the same server I always use so if that's the case then they just changed that setting. It also didn't work on another server I tested but didn't think to look to see if "Easy Comms" was enabled.

[Wolf359]

I'm experiencing similar issues in stand-alone mode - not on the servers. And this is since the update. Can't contact ATC for start up, etc. I found that I have to be partially started - right engine - and key in the frequency before I can get the clearance to start up. This wasn't the case before the update. I even tried having the ground crew connect external power first. Same result. This is in the F-18.

[oldmanflan]

I've tried everything. Including ensuring the server I'm on has Easy Comms enabled, as well as playing a simple single player campaign. I've even re-watched tutorials to ensure I'm not just completely forgeting something simple all the sudden. Regardless of my efforts, comms won't work, despite using the same methods that worked 100% of the time, up until a couple of days ago.

 

I'm now convinced that a bug has been introduced into the game or something has gone awry with my game install (which I haven't touched). I'll hold off until the next update (scheduled for 11/27) and see if that resolves it. Otherwise I'll try to install the game from scratch.

 

Assuming this is a bug, I've got to say that, at least for me, this is definitely a game breaker as it eliminates half the fun. Hopefully it gets resolved soon.

Edited November 20, 2019 by oldmanflan

[=475FG= Dawger]

Check your client game play settings

 

[oldmanflan]

Check your client game play settings

 

Thanks for the input. I assume you mean making sure 'Radio Assists' and 'Easy Communication' are both toggled on, correct?

 

I just double checked and both of those are turned on.

[=475FG= Dawger]

Thanks for the input. I assume you mean making sure 'Radio Assists' and 'Easy Communication' are both toggled on, correct?

 

I just double checked and both of those are turned on.

 

Yes. That is what I meant. i will test on my server and see if i can duplicate your issue.

[oldmanflan]

Yes. That is what I meant. i will test on my server and see if i can duplicate your issue.

 

I truly appreciate the help!

[=475FG= Dawger]

Just tested and have no issues using \ to bring up the comms menu.

[oldmanflan]

Just tested and have no issues using \ to bring up the comms menu.

 

Ugh, now I'm thinking there is something wrong with my game install.

 

Thanks for looking into it on your end.

Edited November 20, 2019 by oldmanflan

[=475FG= Dawger]

Rebind the comms menu to a different key and see if it works.

[Frederf]

The '\' key brings up a comms menu but not the radio comms menu. For example in the F-16 the following is seen at the top of the screen in white text (control options control name in bold):

 

Communication menu

INTERCOM

Main

F1. Flight...

 

Transmit Switch - UHF

UHF Radio AN/ARC-164

Main

F1. Flight...

 

Transmit Switch - VHF

VHF Radio AN/ARC-222

Main

F1. Flight...

 

If you use the INTERCOM device you're basically speaking into the local airplane. The only people that would hear you are: the D seat rear pilot, ground crew plugged in with ground telephone, tanker with connection through boom, and ground crew which can hear you with canopy open and engine off.

[Wolf359]

Just to be very clear, he's not the only one with this issue. Unfortunately, it's a bit intermittent. I will be sitting on the ground, cold and dark, battery on, press \ and comms menu comes up. Tried talking to ground crew. Nothing. When I CAN contact ground crew I tried having them connect external power, then tried contacting ATC. Nothing. Started right engine, keyed in the frequency for ATC, can contact them. Request startup - it's a bit after-the-fact at this point. From here all is good until I am in the air - departing ATC frequency is assigned to com1, and destination ATC assigned to com2. I press \ and get nothing - no menu, nothing. Tried re-keying the frequencies and still got nothing.

 

When I get home tonight I will test again and test if VoiceAttack has any effect on this.

 

Forgot to mention: my issue is with the F-18. I haven't tested in the Viper yet.

Edited November 21, 2019 by Wolf333

[oldmanflan]

Welp, after wasting a ton of time and energy, I resolved the issue and realized that Frederf was right the entire time. While both his comments were informative and much appreciated, they still didn't contain the clear answer and didn't make sense to me until I found the solution elsewhere and then pieced together what he has been trying to clarify for us.

 

Solution:

When he says that in order to use the radio comms menu while airborne, you have to hit (R-ALT + \) to get the proper VHF comms menu to pop up and (R-CTRL + \) to get the proper UHF comms menu to pop up. Just hitting \ on it's own, while airborne, doesn't cut it.

 

I've tested this in both the F-16 and F-18 and can confirm that adding R-ALT or R-CTRL to the mix completely solves the problem. I now get responses from the tankers and air bases again.

 

 

Just to be very clear, he's not the only one with this issue. Unfortunately, it's a bit intermittent. I will be sitting on the ground, cold and dark, battery on, press \ and comms menu comes up. Tried talking to ground crew. Nothing. When I CAN contact ground crew I tried having them connect external power, then tried contacting ATC. Nothing. Started right engine, keyed in the frequency for ATC, can contact them. Request startup - it's a bit after-the-fact at this point. From here all is good until I am in the air - departing ATC frequency is assigned to com1, and destination ATC assigned to com2. I press \ and get nothing - no menu, nothing. Tried re-keying the frequencies and still got nothing.

 

When I get home tonight I will test again and test if VoiceAttack has any effect on this.

 

Forgot to mention: my issue is with the F-18. I haven't tested in the Viper yet.

 

I can't say this solves your issue for comms on the ground. But it should definitely solve your issues with comms in the air.

Edited November 21, 2019 by oldmanflan

[Wolf359]

Speaking of comms, is there any way to lengthen the timeout for being logged into the forum. My log in times out before I can complete a post.