keybinding in UI Layer to navigate radio menu

[fabio.dangelo]

It would be very convenient to have the ability to set buttons to scroll and select the Radio command menu instead of function keys.

By using three buttons on the HOTAS two to go up and down and one to select the single item you could use the same HAT as the radio but using modifier buttons.

This function in my opinion is essential in VR.

 

[prancibald]

Yes!  Especially when trying to land a carrier AND do proper communications with the carrier, it can be tough.

[MAXsenna]

19 hours ago, prancibald said:

Yes!  Especially when trying to land a carrier AND do proper communications with the carrier, it can be tough.

Any reason you don't use your voice?  

[fabio.dangelo]

53 minuti fa, MAXsenna ha scritto:

Any reason you don't use your voice?  

Yes! Vaicom doesn't always recognize my commands or I don't remember exactly what to say.

I am an early purchaser of Vaicom always paying for every single addon.

I use it a lot but there are situations that I just can't solve with my voice

[Maverick87Shaka]

This is an interesting feature request, and not only for VR players!
Even for "standard" flat screen user like me, it could be interesting have something usable from hotas.

And coming back to Vaicom/Voice attack and other software... the main problem to me is the fact that I always fly in multiplayer, it's always tricky mute VOIP for commands, unmute as you finish etc. Imagine if everyone in the voice channel start speak to their computer! Ahahaha it will be a mess
I found it useful only in single player, that I don't really use so much to be honest.


 

[MAXsenna]

Yes! Vaicom doesn't always recognize my commands or I don't remember exactly what to say.
I am an early purchaser of Vaicom always paying for every single addon.
I use it a lot but there are situations that I just can't solve with my voice

Yeah, that's the issue for us non natives, but the question was primarily for prancibald, since he at least lives in the US.

Sent from my MAR-LX1A using Tapatalk

[MAXsenna]

This is an interesting feature request, and not only for VR players!
Even for "standard" flat screen user like me, it could be interesting have something usable from hotas.

And coming back to Vaicom/Voice attack and other software... the main problem to me is the fact that I always fly in multiplayer, it's always tricky mute VOIP for commands, unmute as you finish etc. Imagine if everyone in the voice channel start speak to their computer! Ahahaha it will be a mess
I found it useful only in single player, that I don't really use so much to be honest.


 

In VAICOM press the REL/HOT "light" in the control panel, and you can issue ordinary VoiceAttack commands without pressing a TX. Or just use TX5/6.
As for not transmitting to the AI ATC. Just assign a different button for VAICOM than VoIP/SRS. Or even better, in the future. If we could block the players voice globally, I don't see the issue at all, because in the real world anyone would hear you on the same frequency anyway.

Sent from my MAR-LX1A using Tapatalk

[dankmaster]

50 minutes ago, Maverick87Shaka said:

it's always tricky mute VOIP for commands, unmute as you finish etc.

Yes it is.  Instead of this, I have a button on my throttle that is bound to "Joystick Button Recognition" in VA hotkeys options.  This way, it only listens for commands when the button is pressed down and then no worries about random radio communication activating a VA command or forgetting to mute my radio when I issue a command to VA.

[prancibald]

On 7/10/2023 at 8:26 AM, MAXsenna said:

Any reason you don't use your voice?  

If I'm playing multiplayer, I definitely use my voice to announce I'm landing, but to get the carrier to place units in a queue for landing, I think they have to go through the communications menu, no?

 

I also don't have voice attack or vaicom or anything like that.

[MAXsenna]

If I'm playing multiplayer, I definitely use my voice to announce I'm landing, but to get the carrier to place units in a queue for landing, I think they have to go through the communications menu, no?
 
I also don't have voice attack or vaicom or anything like that.

Yeah, if you don't use VAICOM, you need to use the menu.

Sent from my MAR-LX1A using Tapatalk

[Casablanca]

On 7/4/2023 at 4:14 PM, fabio.dangelo said:

It would be very convenient to have the ability to set buttons to scroll and select the Radio command menu instead of function keys.

By using three buttons on the HOTAS two to go up and down and one to select the single item you could use the same HAT as the radio but using modifier buttons.

This function in my opinion is essential in VR.

 

You won't believe me, but I came here just to ask for that, I was shocked to see you already asked for it

My proposition is slightly different from yours as I wanted 4 buttons;

RIGHT > for opening the menu or "clicking" on Items,

LEFT < for going back in the menu or to close it if the highest level is reached,

UP/DOWN to .. well, to go up and down ...

It can be very easy to implement and would greatly improve our experience in VR and even in 2D

Edited July 12, 2023 by Casablanca

[MAXsenna]

You won't believe me, but I came here just to ask for that, I was shocked to see you already asked for it
My proposition is slightly different from yours as I wanted 4 buttons;
RIGHT > for opening the menu or "clicking" on Items,
LEFT < for going back in the menu or to close it if the highest level is reached,
UP/DOWN to .. well, to go up and down ...
It can be very easy to implement and would greatly improve our experience in VR and even in 2D

Oh, I believe you!
What's very interesting, is that soooo many users have been requesting this exact feature for years and years!
Even I, who use VAICOM with VoiceAttack, and don't need it all, would welcome such implementation with open arms.
So please moderators, unless there is a better feature/alternative incoming in a George/Petersson kind of menu.
Please let this happen! It's time!

Cheers!

Sent from my MAR-LX1A using Tapatalk

[dankmaster]

Having keybinds for the menu options would also be great.

Some of them already have it like Request launch, salute, hornet ball, rearm menu...

[MAXsenna]

Having keybinds for the menu options would also be great.
Some of them already have it like Request launch, salute, hornet ball, rearm menu...

Yeah, a lot of "shortcuts" could be part of the UI Layer or at least a "Radio layer", that's equal across all modules.

Sent from my MAR-LX1A using Tapatalk

[fabio.dangelo]

7 ore fa, Casablanca ha scritto:

My proposition is slightly different from yours as I wanted 4 buttons;

...

yes I had thought about it, but in the end having only three buttons allows you to use the warthog's hat with many modules without having to make strange combinations. forward and backward open the two radios (like in real life) while up and down and press you use it to navigate and select menu items.

[Casablanca]

8 hours ago, MAXsenna said:

Oh, I believe you!
What's very interesting, is that soooo many users have been requesting this exact feature for years and years!
Even I, who use VAICOM with VoiceAttack, and don't need it all, would welcome such implementation with open arms.
So please moderators, unless there is a better feature/alternative incoming in a George/Petersson kind of menu.
Please let this happen! It's time!

Cheers!

Sent from my MAR-LX1A using Tapatalk
 

Maybe if we came altogether in the same post will make it more visible, but ED doesn't appear to be very interested in this wishlist

[MAXsenna]

Maybe if we came altogether in the same post will make it more visible, but ED doesn't appear to be very interested in this wishlist

Yes, if we get enough responses, or maybe OP can even change the post to a poll? Not sure if that's possible.
I did re-read all your posts, and I would like to add a proposal.
To save buttons/hats I suggest that it should be implemented like the George and Petrovich menu.
With this I mean that you designate a hat, like the the trim hat, for navigating the menu, (or more hats, depending on how many grips etc. you have), but it will only work after you invoke the menu by pressing a PTT, and revert back to the default functions after the menu selection has been executed.
This will save some keybinds, like you mentioned @fabio.dangelo

Cheers!

Sent from my MAR-LX1A using Tapatalk

[fabio.dangelo]

1 ora fa, Casablanca ha scritto:

Maybe if we came altogether in the same post will make it more visible, but ED doesn't appear to be very interested in this wishlist

I don't think so, several times in the past I know of requests that came to us that were later implemented.
I personally talked about the Leap and sure it took time but eventually an implementation of it (maybe not perfect) was there.
This implementation I don't think is complex and I think if people show interest it could come (maybe not in the next OB but definitely within the year)

[fabio.dangelo]

As a matter of fact.
I would like this implemetation specific to each module, like you do for kneeboard or labels.
Also because the radio controls can be in different places depending on the module for example on the stick for almost every helicopter.
But I understand that such an implementation would become more complex to develop and would require adoption by each individual third party. (although they already do for the above mentioned sections related to kneeboard, light, view or labels)
I actually developed a script in autohotkey (module-specific) to do this navigation, but having it native in Core would be infinitely better.

I wonder if maybe some moderators like @BIGNEWY @NineLine, @Wags can tell us if they will consider it. 

[MAXsenna]

As a matter of fact.
I would like this implemetation specific to each module, like you do for kneeboard or labels.
Also because the radio controls can be in different places depending on the module for example on the stick for almost every helicopter.
But I understand that such an implementation would become more complex to develop and would require adoption by each individual third party. (although they already do for the above mentioned sections related to kneeboard, light, view or labels)
I actually developed a script in autohotkey (module-specific) to do this navigation, but having it native in Core would be infinitely better.
I wonder if maybe some moderators like @BIGNEWY @NineLine, @Wags can tell us if they will consider it. 

To be honest I find it ridiculous that some modules have different keybinds for equal features like the kneeboard. (But VAICOM solves this for me in VoiceAttack via exposed variables anyway ).
Core features like the kneeboard should all be part of the UI Layer of you ask me.
Also, this sort of what I propose. The radio menu now is "equal" in all modules, so I assume it's part of the SDK. Now if we do get a new system, it still can be invoked by different PTTs that are module specific.

Cheers!

Sent from my MAR-LX1A using Tapatalk

[fabio.dangelo]

I agree with you regarding kneeboard, labels, view, etc. 
(So much so that I use a "service" throttle where these things are mapped equally for all modules).
But maybe for radio navigation I would make that exception precisely because the controls might be in different places (almost all aircraft have radio controls on the Warthog's HAT, but for the F-14 I use the collie hat and for the Viper just the Cougar throttle, for helicopters I use the collective, so as you can understand the radio controls would have to be in many different places. 
However if in the end ED put them in the UI layer I would be fine with that anyway.

[MAXsenna]

I agree with you regarding kneeboard, labels, view, etc. 
(So much so that I use a "service" throttle where these things are mapped equally for all modules).
But maybe for radio navigation I would make that exception precisely because the controls might be in different places (almost all aircraft have radio controls on the Warthog's HAT, but for the F-14 I use the collie hat and for the Viper just the Cougar throttle, for helicopters I use the collective, so as you can understand the radio controls would have to be in many different places. 
However if in the end ED put them in the UI layer I would be fine with that anyway.

Ah, I see, and I agree if you could only bind one hat. I did "cover" that in my proposal though, as I suggested that you can add several hats/buttons for the navigation. As many as you like actually!
It would be very simple to just add a new hat. Only four "hat presses" for a new one.

Sent from my MAR-LX1A using Tapatalk

[fabio.dangelo]

I think that wouldn't work. a command binded  in the ui layer could not be associated with a single module because it would conflict. if you match all the hats of your hotas to this thing, there wouldn't be any left for module specific functions.

[MAXsenna]

I think that wouldn't work. a command binded  in the ui layer could not be associated with a single module because it would conflict. if you match all the hats of your hotas to this thing, there wouldn't be any left for module specific functions.

Apologies. You missed my point.
Absolutely, a button bound in the UI Layer will work in any module, that's why we get "more and more" conflicts as keybinds are moved to the UI Layer.
Do you have the Apache or Hind? There you can bind your trim hat to George/Petrovich as the "interface/command selector", but it will only work as this, when the George/Petrovich menu/overlay is open. When is not open, it works as a trimhat, or any other function you bound it to.
This can of course be done in a similar way for the radio menu. It's just coding after all.
ED has never responded to these request IIRC, might be that it's actually related to the new coming ATC features, and I have a feeling this is exactly the implementation they are going for.

Sent from my MAR-LX1A using Tapatalk

[fabio.dangelo]

Sorry I didn't understand your proposal.
It could work well!!!