F15E Radio communication after 2.9 update

[KP_Ghost]

Radio comms with default atc "/" are not working in the strike eagle. I tried to communicate when trying to do air refueling and ATC after update. Tried to replicate on other modules but comms are working correctly (FA18C and F16C). 

[draconus]

Default "/" (comms menu) was never meant for radio (unless you use easy comms or FC3 modules) - only for ground crew comms.

Use proper push-to-talk binds for radio comms.

Edited October 20, 2023 by draconus

[KP_Ghost]

Didnt find the words at that moment easy comms!"/"  thanks. Has done this "mission red flag  1 by sedlo" before and it was working correclty pre 2.9 for air fueling.

[Despayre]

I had the same issue after the update... Using "\" brings up the menu, but it doesn't work. Now I've found that I have to bind  "MIC switch FWD (Call Radio 1 Menu)" to bring up the menu. Never needed that keybind before, would have been nice if it was mentioned somewhere...

[KoleTang]

My "\" does bring up the comms menu but when I do an "F5 - Tanker" and then an "F1-Intent" to refuel I get a strange behavior.  The tanker frequency should be 251.000 and the cockpit shows 251.000.  But when the F1 key is pressed it changes the cockpit frequency to 251.001 and the tanker never responds.  This worked before 2.9 and if I fly the same mission with the hornet or viper it works fine.  I have attached the mission.

F-15E_Tanker_KC-135.miz

[KP_Ghost]

@KoleTangThe easy comm "/" for the strike eagle doesn't work for now, map the following controls to your HOTAS : mic switch 1 and 2  it will call each correspondent radio menu. But remember to tune your freq.

Edited October 22, 2023 by KP_Ghost

[KoleTang]

@KP_Ghost thanks for the response.  I do have my frequencies tuned.  I was trying to point out that the comms menu is changing the frequency slightly.  251.000 to 251.001.  Just as feedback to help the devs.

[Se1ko]

In the F-15E I am finding that when you use the radio call menu (1 or 2) radio command to bring up the appropriate menu the radio selected keys itself until you select a radio call.

For example, I select Call Radio 1 Menu (Mic Switch FWD) to make a call to the tower from the menu. When I do that, the UFC shows Radio 1 is keyed and stays on with the "T" displaying even before I have selected a call using the function keys. It is not until I have selected an F-key function and the transmission is made that the radio will un-key itself and the "T" disappears.

This is in contrast to the F-16, where if I select radio call menu (1 or 2) to bring up the call menu, the radio will not key its self until the radio call has been selected from the menu, where it then keys the radio, makes the transmission, then un-keys itself, which is what I would expect from the radio call menu function.

In short, it seems that the F-15 radio logic is keying the microphone the moment you select the radio call menu and does not un-key until you have selected a radio call and transmitted it.

Would this not be a problem when using voice chat and you are holding the radio in transmit?

Edited October 29, 2023 by Se1ko

[Recluse]

On 10/29/2023 at 5:13 AM, Se1ko said:

In the F-15E I am finding that when you use the radio call menu (1 or 2) radio command to bring up the appropriate menu the radio selected keys itself until you select a radio call.

For example, I select Call Radio 1 Menu (Mic Switch FWD) to make a call to the tower from the menu. When I do that, the UFC shows Radio 1 is keyed and stays on with the "T" displaying even before I have selected a call using the function keys. It is not until I have selected an F-key function and the transmission is made that the radio will un-key itself and the "T" disappears.

This is in contrast to the F-16, where if I select radio call menu (1 or 2) to bring up the call menu, the radio will not key its self until the radio call has been selected from the menu, where it then keys the radio, makes the transmission, then un-keys itself, which is what I would expect from the radio call menu function.

In short, it seems that the F-15 radio logic is keying the microphone the moment you select the radio call menu and does not un-key until you have selected a radio call and transmitted it.

Would this not be a problem when using voice chat and you are holding the radio in transmit?

 

The VOIP PTT commands  are (and must be) different binds from the Radio PTT so it really wouldn't matter.

[Se1ko]

On 11/3/2023 at 4:34 AM, Recluse said:

The VOIP PTT commands  are (and must be) different binds from the Radio PTT so it really wouldn't matter.

I think you're missing the point. I am not talking about the VOIP or the Radio PTT button.

When I bring up the communication menu in the F-15 using the appropriate button for the radio I want to use, the radio itself is keyed into transmit and stays that way. It is not until i select a command from the menu and the call is made that it unkeys itself. So the radio is keyed the entire time from start to finish.

What should be happening (and happens on the F-16C) is that I press the Radio call menu  for the radio I want, select the call I want to make from the communication menu, the radio then keys into transmit and makes the call, then the radio unkeys and no longer transmits. The radio only keys itself when making the transmission of the selected menu option, which is what I would reasonably expect, not continuously transmit from just selecting the communication menu.

Edited November 4, 2023 by Se1ko

[Recluse]

Right I understood, but you were saying that the continuous transmit when you call the radio menu might mess up the VOICE CHAT, and I was saying it WOULDN'T because the keys are different so you are not keying the Voice Chat with the Radio Menu button

 

But for what it is worth, I can confirm your observation about the continuous T when calling up the Radio menu. The Hornet works the same way as you describe the F16C,  where the transmit symbology only happens when selecting a menu item, so I do think this might be a bug.

Edited November 4, 2023 by Recluse

[Se1ko]

1 hour ago, Recluse said:

Right I understood, but you were saying that the continuous transmit when you call the radio menu might mess up the VOICE CHAT, and I was saying it WOULDN'T because the keys are different so you are not keying the Voice Chat with the Radio Menu button

 

But for what it is worth, I can confirm your observation about the continuous T when calling up the Radio menu. The Hornet works the same way as you describe the F16C,  where the transmit symbology only happens when selecting a menu item, so I do think this might be a bug.

 

I don't know that it does or doesn't affect voice chat, I would hope not, however as there are a lot of problems with voice chat in its early stages I think its something that needs to be looked into. Making the assumption that because its different key binds it won't affect voice chat is something I personally wouldnt hang my hat on at this time.

Whats to say that while the transmitter is keyed you can't hear whats being sent to you due to some problem with the comms logic?

What it does bring to light is that there is no commonality between modules as to how the radio communications menu works and ED and its partners perhaps need to come to an agreed standard of how it works in the future.

To my mind I would of thought the functionality for such a baseline feature of DCS World should of been standardised across all modules and module makers before the changes occurred in 2.9.

Going forward I would love to see the implementation of the short press/long press of the radio button on a controller (like a stick abstraction) to be able to either bring up a comms menu or transmit over VOIP, rather than have all these key binds to deal with.

Edited November 4, 2023 by Se1ko

[Recluse]

Well, I just tried it and I can confirm that the continuous transmit of the AI Radio Menu DOES NOT AFFECT TRANSMIT ON VOIP, as indicated by the Transmit indicator on the VOIP panel.

I agree with the SHORT and LONG press.  It is implemented  in the special options for the Mirage2000 and I have used it successfully with SRS