Decouple radio F10 “other” menu from Communications

[Hairdo1-1]

Please decouple the f10 radio menu option from the comms menus. This (as far as I know) is used exclusively to for triggers and scripts so there is no reason to have it associated with the COMs menu. Please make it a separate menu with a dedicated key binding that does not have anything to do with what radio I’m using, frequency I’m on, or if my radio is even on. 

[Maverick87Shaka]

That's why it's listed as Other in the F10 menu.

To be honest, I don't see any reason to move Other options outside the communication menu, even because it's often used to interact with JTAC, "virtual command center" and so on, so definitely it's worth have it under communication menu.

with default integrated ATC and other feature, I barely see all the menu populated, so didn't get why it should be moved away if it's not occupying a valuable slot that can be used for other stuff.
 

[SharpeXB]

I don’t think adding another key bind is worth the trouble. 

[rob10]

2 hours ago, Hairdo1-1 said:

Please make it a separate menu with a dedicated key binding that does not have anything to do with what radio I’m using, frequency I’m on, or if my radio is even on. 

Unless the trigger/script it's using requires the radio to be in a specific state (i.e. a specific freq), it currently doesn't care what radio/freq/on/off status is.  A lot of the stuff that it gets used for IS radio related, so to me it makes sense to leave it there.