Prior to 10.5.6 if my system was in the dvorak layout the entire game of wow would obey the layout. I could assign keys in the keybindings based on the dvorak layout and everything worked as it should.

Now, after the 10.5.6 patch the game will accept Dvorak input in text fields such as the login window and chat, but the keybindings only correspond to QWERTY. I'm having to reconfigure my entire keybindings based on QWERTY, whereas the actual keypresses are dvorak should I type them in a chat pane.

For example, the standard movement keys for Dvorak are:
Forward: , (comma)
Backwards: O
Turn Left: A
Turn Right: E

Prior to 10.5.6 I could use that setup in the actual keybinding window and move my character. Upon logging in, I had to reset my keybindings so they SHOWED:
Forward: W
Backwards: S
Turn Left: A
Turn Right: D

But my keyboard layout systemwide is still Dvorak. I can still type appropriately, I just have to reset all my keybindings.

Anyone else notice this?

---

Q u o t e:
Anyone else notice this?

---

I wonder how many other players use Dvorak? Does Blizzard even test using it?

Did you check your Input Method settings after you did the 10.5.6 update?
The updater might have reset them.

I did check, and it was still set to Dvorak. I reset it to Dvorak too, just in case.

No, this is not an input method issue. I'm running into the same thing.

When playing the game in windowed mode (so that I can verify that the systemwide input method is -not- changing back and forth between US-EN and Dvorak, I notice the same result:

Single-key commands (such as 'r' to respond to a whisper, or '/' to initiate a text command or chat) are bound to their QWERTY equivalents, ignoring the system settings.

When the input focus is on a text field (login, chat) keys are responding the systemwide input method, which for me is Dvorak.

The result: I can press the '/' key on my keyboard twice, and the game captures two different characters: a slash to initiate the command text field, and then a 'z' which it inserts into the field. 'Z' is the Dvorak key bound to the QWERTY '/'. Same key twice in a row, two different characters captured.

This presents an enormous problem: going back and rebinding all of my keystrokes to QWERTY is insufficient - the game is changing its text input behavior dynamically, ignoring systemwide input management settings.

~Payle

---

Q u o t e:


I wonder how many other players use Dvorak? Does Blizzard even test using it?

---

Dvorak's similarity to a re-arranged QWERTY is coincidental... the issue exists using any non-QWERTY input method.

~Payle

I have the same problem. Good thing I logged in early before the raid.

Add me to the list of people that cannot play WoW with a keyboard anymore :p

Me, too...I buy WotLK, and two days later, my ability to play is basically shattered.

And I don't know what the guy above is talking about w.r.t. the / key and the Z key...on a dvorak keyboard, the '/' character is usually generated by hitting the key marked '[' on a qwerty keyboard...so every time I try to talk, I start taking a movie. Very annoying!

Also, I understand that since this happened when 10.5.6 was released, that it's probably more Apple's fault than Blizzard's, but it is a very very frustrating result. Please help!

You can pull your key bindings somewhat back together if you reset them to the defaults and start over.

Yes, I could re-bind every character in the entire warcraft universe, and then re-re-bind them in a week when this gets patched. While that's a lot of work, it would be worth it--but at this point, I am concerned about what else might have the wrong binding, and at what point I'm going to discover that and basically be screwed.

---

Q u o t e:
Me, too...I buy WotLK, and two days later, my ability to play is basically shattered.

And I don't know what the guy above is talking about w.r.t. the / key and the Z key...on a dvorak keyboard, the '/' character is usually generated by hitting the key marked '[' on a qwerty keyboard...so every time I try to talk, I start taking a movie. Very annoying!

Also, I understand that since this happened when 10.5.6 was released, that it's probably more Apple's fault than Blizzard's, but it is a very very frustrating result. Please help!

---

If you press the / key on a qwerty keyboard, you'll get a z.

Also, the same thing is happening to me. Is there a way to delete this update? Would it help?

This problem is worse than I originally thought. Not only are the keybindings broken, apparently they're now stored server-side. I play both at work and at home, and my WORK keybindings on PC are correct (ie., dvorak) but because I went ahead and updated the keybindings at home so I could play, they're TOTALLY wrong here on my PC.

Given that I play more at home, I guess I'm just going to ignore the game here at work for now, but this is a pretty irritating bug.

Aww that sucks because I tried to backup my good keybindings before I replaced them with funky QWERTY bindings.

Add me to the list of people affected by this. I play at home on Macs (don't even have Windows at home) and on Windows at work (don't have Macs at work). So I can't just switch to a qwerty-based key bindings configuration - it'll break playing at work.

I'm not sure if this is a Blizzard change or an Apple change, but Blizzard has helped me work with Apple about issues in the past... I hope Blizzard can help us address this and find a satisfactory resolution.

---

Q u o t e:


If you press the / key on a qwerty keyboard, you'll get a z.

Also, the same thing is happening to me. Is there a way to delete this update? Would it help?

---

Ha, sorry, I was thinking about people with a dvorak keyboard trying to hit /, and beginning to record a movie. But yes, in order to start chat on a dvorak keyboard, you need to hit 'z' instead of '/' because the dvorak 'z' is a qwerty '/', and WoW is now only looking at the qwerty version of a keypress.

---

Q u o t e:


I'm not sure if this is a Blizzard change or an Apple change,

---

It is certainly an Apple change. We know this is the case because the same version of WoW worked fine before the update to 10.5.6, and this bug was introduced immediately after said update. So, it is a change to the way Apple represents keycodes...which break the way WoW interprets them.

I actually am having a similar problem using Microsoft Word 2008--now when I hit command-b to boldface, I get a new window, because the dvorak 'b' is on the key marked 'n', and command-n is for 'new window.' More evidence that this is Apple's fault.

So, to answer the above-quoted question, "is there any way to revert," this post on Apple's site says that basically, no, you can't revert.
http://discussions.apple.com/thread.jspa?messageID=8639336
I am hoping hoping hoping that Apple fixes this soon, or that Blizzard in their wisdom comes out with a patch that will fix the effects of Apple's mess-up.

---

Q u o t e:
Add me to the list of people affected by this. I play at home on Macs (don't even have Windows at home) and on Windows at work (don't have Macs at work). So I can't just switch to a qwerty-based key bindings configuration - it'll break playing at work.

I'm not sure if this is a Blizzard change or an Apple change, but Blizzard has helped me work with Apple about issues in the past... I hope Blizzard can help us address this and find a satisfactory resolution.

---

I found a solution to this, incidentally.

/console synchronizeBindings 0

You can also put

set synchronizeBindings "0"

in your config.wtf or whatever it's called.

The old keybindings are saved in a file that's got .old at the end of it. I suggest modifying your config.wtf, then restoring the OLD settings (the good ones) on the windows machine. It worked for me. It's the best I can come up with for now.

Not sure if we're allowed to bump these types of threads, but I really want to find a solution for this.

---

Q u o t e:


I found a solution to this, incidentally.

/console synchronizeBindings 0

You can also put

set synchronizeBindings "0"

in your config.wtf or whatever it's called.

The old keybindings are saved in a file that's got .old at the end of it. I suggest modifying your config.wtf, then restoring the OLD settings (the good ones) on the windows machine. It worked for me. It's the best I can come up with for now.

---

This DOES work for me. I don't know if it fixes everything, but I can definitely move around and type correctly.

Thank you!!!