http://bugs.winehq.org/show_bug.cgi?id=59214 Bug ID: 59214 Summary: Keysym translation breaks key bindings in most video games for Dvorak users Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs@list.winehq.org Reporter: burneddi@protonmail.com Distribution: --- Created attachment 80110 --> http://bugs.winehq.org/attachment.cgi?id=80110 workaround for the issue Most video games try to bind keys by positions (virtual keycodes) rather than by keysyms. This means the keybindings will be layout-agnostic as long as the user is using a standard physical keyboard -- so e.g. WASD movement will still happen on where the WASD keys would be on QWERTY even if the user's layout is AZERTY or Dvorak. The way Wine remaps vkeys for Dvorak layouts breaks this, resulting in the default controls in most games being unusable and the user having to rebind every key manually (so e.g. WASD in the settings menu becomes ,AOE). I can't imagine translating vkeys like this is actually correct or desireable behaviour. I don't have a Windows machine or the Windows know-how to test this right now, but I'm pretty sure on Windows a Dvorak layout will still be sending standard QWERTY keycodes, making Wine's behaviour incorrect. I've attached a patch that I use to work around this problem by just disabling the Dvorak-specific vkey layout translation. With this patch keyboard binds in games work as expected, and it doesn't break typing into text fields because input into those uses keysyms rather than keycodes. It's not production-ready (I just commented out the dvorak vkey table) but should help illustrate the problem. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.