Jump to content

Command Menu Next/Previous/Select/Return Items bindings stuck


Go to solution Solved by Flappie,

Recommended Posts

Posted

I assigned the Command Menu Next, Previous, Select and Return commands to a hat in my Warthog Hotas Joystick using a modifier on the stick itself.

The binding works perfectly well the first time I use it. From the second time on, the yellow selection remains stuck to the first command menu voice, neither  Next/Previous/Select/Return will work from that moment on.

Steps to reproduce:

  1. assign the Command Menu Next/Previous/Select/Return to a HOTAS hat with a modifier on the HOTAS (e.g. button 4 on the Warthog stick)
  2. bring up a radio command menu (e.g. UHF)
  3. navigate through the radio commands, select a voice (e.g. "ATC Ready to Taxi" or "Ground Crew Rearm & Refuel")
  4. bring up the same radio command menu a second time
  5. try to navigate to the radio commands

 

Thanks

Posted

Hi. I'm trying to reproduce your issue, but I cannot find such commands in the Controls panel. Can you please show them in a screenshot? Unless are you using an external software or mode?

---

Posted (edited)
23 minuti fa, Flappie ha scritto:

Hi. I'm trying to reproduce your issue, but I cannot find such commands in the Controls panel. Can you please show them in a screenshot? Unless are you using an external software or mode?

Hello Flappie, thank you for taking the time to read this.

In the attached image you can find the bindings I'm talking about.

image.png

Edited by OttoPus
  • Thanks 1
  • 3 weeks later...
Posted

Dear All, 

same issue here. I am not sure the community even knows about this feature, nobody seems to know it is there… 

this worked perfectly until the latest patch (last Thursday or Friday)

thanks for looking into it. 

Posted
2 hours ago, stag1978 said:

I am not sure the community even knows about this feature, nobody seems to know it is there… 

The feature came in 2.9 and it was mentioned in the patch notes. The bug was there from the start.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted

Hi, 

it worked perfectly before latest patch. If there was a bug, nowhere was reported. 
I could not find this in the patch notes, but maybe I was not careful enough 

  • 2 weeks later...
  • 1 month later...
  • 1 month later...
Posted

Very long track, showing the comms menu scroll/select working at ramp start, then after landing when I park and go to place chocks it is no longer responding. Double checked binds and the menu responds to my inputs, but the in-game menu does not.

I have not narrowed down whether this is triggered by duration of flight, or triggered by landing event.

Track: https://we.tl/t-BOAH47iPGm

Posted

Do you mean the binds like "Command Menu Next Item", "Command Menu Previous Item" and "Command Menu Select Item"? That was introduced in October 2023?

These are set-up under "Command Menu" in the controls option, you can also now rebind the F1-F12 options (which is fantastic), is this what you mean?

If so I have the exact same issue, but I literally only can have it work once. Then it doesn't work until mission restart, or going into the control option and clicking ok resets it as well.

Is this isn't what you mean I'll make a thread, but hopefully it is! I posted about it in October or so, really hope it will get resolved!

 

Posted
6 hours ago, Nealius said:

Very long track, showing the comms menu scroll/select working at ramp start, then after landing when I park and go to place chocks it is no longer responding. Double checked binds and the menu responds to my inputs, but the in-game menu does not.

I have not narrowed down whether this is triggered by duration of flight, or triggered by landing event.

Track: https://we.tl/t-BOAH47iPGm

A quick question Nealius, if you are referring to what I post above, are you using a modifier for the comms menu scroll binds I mention?

Posted (edited)

@StolenPen Yes, same behavior now that I reproduced in the Hornet as well. It works the first time but refuses to work after, and yes I do use a modifier. With limited HOTAS functions and the complexity of all our modules it's impossible to NOT use a modifier for such tertiary functions. At the same time, modifier works fine for other commands like VR zoom, ball call, tanker pre-contact, etc. Not sure why the modifier would cause a problem with the comms menu only.

Edited by Nealius
Posted
22 minutes ago, Nealius said:

@StolenPen Yes, same behavior now that I reproduced in the Hornet as well. It works the first time but refuses to work after, and yes I do use a modifier. With limited HOTAS functions and the complexity of all our modules it's impossible to NOT use a modifier for such tertiary functions. At the same time, modifier works fine for other commands like VR zoom, ball call, tanker pre-contact, etc. Not sure why the modifier would cause a problem with the comms menu only.

 

Great we're talking about the same thing and have the exact same issue. I have this issue and use modifiers, I also have the same for the F1-F12 rebind, works once then not again when using modifier. So it is clearly somehow broken by using a modifier. Just like you I can't bind these anywhere else and it clearly should be fixed to work with modifier, and hopefully can be simply.

 

Hopefully this gets reviewed and resolved but I tested it earlier and discussed with others with the same issue and it does seem likely down to the modifier. 

  • 2 weeks later...
  • 4 weeks later...
  • 4 weeks later...
Posted
12 hours ago, bephanten said:

same here. scroll and select only works once. then those keybinds do no function.

Are you also using modifiers for the binds? Seems to be down to that. Hopefully they can fix that fairly easily/quickly when they get to it. 

  • Like 1
Posted
13 hours ago, bephanten said:

Using Ctrl as a modifier. 

Makes sense, seems it is to do with modifier use so hopefully they can work out why and fix it. 

  • Like 1
Posted

One helpful comment, not using modifiers doesn't really matter as you can double bind keys with this, the key will do command menu if it is open and the normal binding if it is closed. Still worth them fixing this but in fairness modifiers aren't needed. Could still be helpful to avoid miss-clicking but there's a solution anyway.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...