Request: Inhibit Jester menu when typing a "command" outside of Jester menu

Hello HB team!

Please inhibit the behavior that the "Jester menu" pops up and then quickly disappears whenever a "Command X" button ( X = 1 to 8 ) is pressed but the Jester menu was not selected to be visible before.

There is (obviously) no reason for the Jester menu to pop up by simply pressing a "Command X" button.

This can be seen in the video: https://www.youtube.com/watch?v=A94TJgu-jsk

.) In the first seconds I am simply pressing "Command" buttons 1 to 8.

.) Then I open the menu and toogle it to the second page, and leave it with a third press.

.) Then I press the "Command" buttons 1 to 8 again.

.) Then I open it again, and close it with the "Close menu" key.

.) Then again I press the "Command" buttons 1 to 8 again.

The behavior is always the same. The menu pops up, and immediately disappears.

There is a "Close menu" keybinding which works fine.

Also cycling the "Toogle menu" keybinding works fine.

Thanks for reading and kind regards,

TOViper

edit: title

Unfortunately this effect is still there: Pressing one on the command button without having the Jester menu open does some interaction with Jester.

Are there plans to change the Jester menu strategy? I heard some changes might happen in the near future?

Thanks for the report, but just to understand: why are you pressing the command buttons, when the Jester menu is closed? Mapped otherwise for something else or as direct commands for Jester?

It seems very circumstancial, and a rather minor cosmetic issue, not sure if really worth the effort, or if swither did not even make it on purpose like that as a feedback function. But I might be misunderstanding your point, too. Does it happens if you map the 1 to 8 keys with something else, too?

Thanks for the report, but just to understand: why are you pressing the command buttons, when the Jester menu is closed? Mapped otherwise for something else or as direct commands for Jester? It seems very circumstancial, and a rather minor cosmetic issue, not sure if really worth the effort, or if swither did not even make it on purpose like that as a feedback function. But I might be misunderstanding your point, too. Does it happens if you map the 1 to 8 keys with something else, too?

Good morning Mike, and thanks for coming into my world :)

Indeed, pressing Jester "command buttons" is mostly accidentally.

Why is this you ask ... easy thing, but writing is hard ... so let me give a try:

For VR flying I have assigned "Command 1" with NUM 8, "Command 2" with NUM 9, "Command 3 with NUM 6", and so on (clockwise like the Jester menu dial). Nice and handy. NUM ENTER activates the Jester menu.

The NUM block - and this is an important part - is very handy to reach and hard to confuse while in VR ...

When I switch to normal screen flying the other day (no VR), I accidentally use the NUM block for the viewing commands (NUM 4 would be VIEW LEFT SLOW, NUM 8 would be VIEW UP SLOW). So this means he receives Commands (whichever ... I dont know ... the ones from the first menu level?). And THIS circumstance made me write a thread for asking the devs (becaus I think it was not intentionally designed like it is). :smartass:

Answering your second question:

I didn't assign other keys than NUM X for the "command buttons" so far.

For finding out I will try this with other buttons, but I would never use other buttons to be honest.

Why? Same thing: The NUM block is definitely the best choice in terms of usability in VR, and it fits perfectly to the arrangement of the Jester menu dial!

Will report back soon on this specific question!

Regarding your comment:

If it was a "feedback function" (what's that?) ... then directly pressing one of the command buttons would have a nice advantage:

Activating Jester menu would not be necessary, but then selecting commands would be a "good guess" ... maybe commanding Jester to switch off the radar while MiG-29 is within 20 miles ... :D

Feedback function as in that the player knows that he pressed a command. But dunno if swither intended that, I have to ask him. I'll put down a tracker, but it's a minor issue, so it will drop down the list a bit. We'll take a look at some point though, Jester menu will get most attention when we add lantirn. In any case, thanks for letting us know.

Thanks Mike, I will do some further tests today to feed the tracker with usefule information. I assume there will be major changes in the future, so it might be helpful for you.

You might have already noticed another thread about the "Command X" selections https://forums.eagle.ru/showthread.php?t=268460

Kind regards,

TOViper

Hello Mike,

I did some tests today. I can do this with other keys for the "Command X" commandoes, like LCTRL+6 (the default combo) as well.

It is not always behaving the same way. Sometimes, when entering a mission (alone on Caucasus), it is not possible to "overrule" it, but very often it is.

You may try it out on your own, simply place an F-14B on the map, fly it from the front seat, and then press any of the "Command" buttons. Jester will then perform the command, which is in the first "level" when one would activate "Jester menu". Simple and easy to do ...

OB 2.5.6.45915

Kind regards,

TOViper