In the viewport, holding down the right mouse button prevents the use of the "w", "a", "s", and "d" keys for movement.

Summary

In the UE5.8 viewport, holding down the right mouse button does not allow using the “wasd” movement keys, but it is possible to control rotation with the mouse. I don’t know what was done to cause this issue. It suddenly appeared (possibly due to some editing operation, reverting to the selection state, and then it stopped working). Has anyone encountered this? Is there a way to restore it?

What Type of Bug are you experiencing?

Editor

Steps to Reproduce

Perhaps it’s because after operating in terrain mode for a while and switching to selection mode, it doesn’t work anymore, and I’m not 100% sure

Expected Result

Can it be recovered?

Observed Result

Can it be recovered?

Affects Versions

5.8

Platform(s)

Windows

I had a very similar problem and it turned out not to be an engine bug on my end — my desktop environment was swallowing the keys before they ever reached Unreal. Posting the details in case it helps anyone here.

Setup: Fedora Linux, KDE Plasma 6.7 (Wayland session), Unreal Engine 5.8.2.

Symptom: With RMB held in the level viewport, the camera would not move in some directions. Mouse look worked normally. W (forward) and Q (down) worked; S, A, D and E did nothing.

What narrowed it down:

  • The affected keys were exactly the ones that have accented variants on a German keyboard layout (s→ß, a→ä/à/á, e→é/è/ë, d→đ). W and Q have none, and those were the two that worked.
  • E worked fine as the Rotate Mode shortcut (a short tap) but never for navigation (held down).
  • Holding one of the dead keys sometimes made a small character-picker popup appear in the top-left corner of the screen, offering ß and other characters when holding S.

Cause: Plasma 6.7 added a press-and-hold popup for alternate characters and diacritics, similar to mobile keyboards. It lives in the plasma-keyboard module. Because holding RMB + a movement key is by definition a long press, the compositor grabbed the key for the picker instead of passing it through to the editor window. Short taps were unaffected, which is why E still triggered Rotate Mode.

Fix: System Settings → Keyboard → Virtual Keyboard → turn it off. All six navigation directions worked instantly afterwards.

Worth checking even on Windows: open any text field, press and hold A, S, D or E for a second, and see whether a character picker appears. In my case Unreal was not involved at all in this failure mode, so if some input utility, IME or keyboard tool on your system does long-press character selection, it would produce identical behaviour.