Keyboard input misinterpreted in Controls

In both assigning and searching for input, keyboard input is misinterpreted.

Shift-Left is supposed to be to pan left, and this worked in the previous version. It no longer works in 10.10.7.0.

When pressing Shift-Left on the physical keyboard (the arrows keys), it shows Shift-Num4 during settings. Pressing the left arrow only (without shift) shows “left” correctly.

I’ve tested this with 2 different keyboards (Logitech G512 and generic wireless keyboard).

In addition (maybe unrelated), while ctrl-Space is supposed reset the cockpit camera and is interpreted correctly, it does not, and seems to switch to landing view.

Now whey i use shift left arrow or right arrow it is actually steering my aircraft.

Reported yesterday to zendesk.

obraz

1 Like

This issue remains in 1.10.8.0

There is more to it. Also Ctrl-Shift-Insert is recognized by the program as Ctrl-Shift-Num0. Tried it with 2 different keyboards.

1 Like

This has to be fixed ASAP!

1 Like

I use a default keyboard profile copy which i set active, and when i asign a key to a button on the joystick, i delete this key from the default keyboard copy to be clear off double progamming to accidently touch the key on the keyboard.
The originaliteit default is for reference might i get lost in proggramming buttons, or if they may change keys with updates like you have mentioned.

This is not the problem… the problem is that is the keyboard buttons you press are interpreted incorrectly, regardless of what you have set in your mapping. They have not updated the defaults, they have introduced a bug, where using a modifier key (like Alt, Shift, Ctrl) in combination with arrow keys, is not shown or acted on correctly.

I reported this to ZenDesk days ago and already got the reply from devs that this will be fixed with upcoming patch.

Yes… but which one? :slight_smile:

I believe and hope the next one, but who knows… :wink:
Anyway, I’ve remapped all my combinations to left/right ALT, so I’m no more suffering from this bug…

I just found this bug and started troubleshooting. Did some searches and found this thread… and today is January 20, 2021 :flushed:

1 Like

This has been reported 3 months ago and sweeped under the rug. When will it be fixed?

Did you report it to Zendesk and get a “bug report received” email back from them??
Regards

Yes, it’s been reported, the same day I posted here.

1 Like