Ability to use the same button for radio X push-to-talk and radio X comms menu

[fisadev]

Let's take the radio 1 from the hornet: right now, we can map a button to transmit with it, which opens a menu of comm messages to send with that radio. The new voice feature will also require a mapping to use as push-to-talk with that radio 1, similar to how we have a key mapped in SRS to do that.

Many people (me included) use the same button for both: if I press a certain button in my throttle, it opens the comms menu for that radio (menu on DCS), and if I keep holding it, it transmits voice over that radio (ptt on SRS). That makes sense: that's the "radio 1" button. Any comms via radio 1 are done with that single button, as you would in the real hornet.

If the new voice feature requires a different mapping for the radio 1 compared to the mapping that shows the menu, then we will need 2 buttons for each radio we use, and that's quite problematic. Most throttles won't have enough buttons to duplicate the radio mappings. And even if we have enough buttons, it also makes less sense and is more cumbersome: we would need to use a different "radio X" button depending if we want to talk to humans or to bots.

So please, let us use the same button if we want to  (not mandatory, because of course there will be people who prefer to use separated mappings).

Edited December 17, 2021 by fisadev

[Northstar98]

+1 and this is essentially what I requested (at least in part) here.

[Baldrick33]

As a work around it can be done using something like Joystick Gremlin and a Tempo option.

Short press: Comms Menu

Long press: Push to Talk

They would be seen by DCS as two separate buttons to map.

[SharpeXB]

The trouble with using joystick plug-ins is that the whole point of DCS having built-in comms is to avoid having to use 3rd party software. So now we’re back to that.

[Baldrick33]

2 hours ago, SharpeXB said:

The trouble with using joystick plug-ins is that the whole point of DCS having built-in comms is to avoid having to use 3rd party software. So now we’re back to that.

Agreed but at least there is a way around it. Alternatively use the in built modifier but it isn't as elegant a solution. If DCS could allow short and long presses of buttons to input mappings that would be better (clearly it can distinguish between them as it does in the implementation of TMS, DMS etc in the A-10) but that might not be a quick fix.

[splash]

+1.

[_Hoss]

On 12/18/2021 at 3:53 AM, Baldrick33 said:

As a work around it can be done using something like Joystick Gremlin and a Tempo option.

Short press: Comms Menu

Long press: Push to Talk

They would be seen by DCS as two separate buttons to map.

That's the way I have it set up with TARGET script, works great.

[NWGJulian]

+1

this. exactly this!

in addition, i want my voice ptt buttons on the module keybindings, not on "general".

because on the f16 i use a 4way hat UP and DOWN, on the f18 its LEFT and RIGHT, and on the hind i actually use the trigger first and second detent.