[Bug] UI going into Ctrl-Lock (for hunters)

by Difool | 28/01/2008 21:21:00

Difool

*Edit* The text below the line is the OP, and it's now clear that issue is either a legitimate Blizzard bug, or a driver/3rd party issue. In either case it affects a very small number of people. The larger issue, that this thread has become a placeholder for (and for which Uma had and has been driving) is with other UI issues around Kill Command - or other hunter actions - where auto attack stops working, esc stops working, feed pet fails, etc. The known workarounds for this are

1) relogging (reset does not work)
2) use specials to land a crit.

This is a serious issue, and hundreds (thousands) of people have been seeing it. Blizzard so far has recognized that the issue is out there but has not yet reported that they have been able to reproduce it.

I've made this edit simply because this thread has become a collection point for the real issue, and my OP here was more related to a separate issue, although I've also encountered the Auto-shot issue with Kill command.
----------------------v v Orig. Post v v---------------------------------------------------------------------
-----------------

something very hard to detect seems to be throwing Hunter UI's into Ctrl-lock, so that any UI action is the equivalent to holding down the Ctrl key.

To get out of it, just hit the ctrl key. But as easy as the "fix" is, the damage is already done. Tab target has already targeted a friendly. the Esc key has already closed your WOW to get to the Windows menu (in XP at least). You have not been able to loot, or use key-mapped shots, or worse, the action mapped to the "1" key has sent your pet into combat (Ctrl+1).

There are reports of this happening in this forum, and in the hunter forum, but they are often reporting the secondary effects. It took me almost a week to figure out what was happening. it showed up with the last patch.

It does seem to be happening only with hunters, so that points to something to do with KillCommand, or pets, or shot sequence macros. it seems to happen at random times, so I've not been able to see any correlation with any event.

I have one of my mouse buttons mapped to the keypress "1" (in the Logitech mouse utility). And it's easy to see when this bug has happened. Normally I press the mouse button an the action bar button mapped to the "1" key lights up. When the bug manifests itelf, petattack lights up on my pet bar instead. I hit Ctrl and it reverts. The killer is that this happens all the time, seemingly sometimes when I'm just moving around.

If it helps, Regular keyboard and driver. Windows XP. Logitech MX Revolution, with most buttons mapped to keyboard actions in the mouse utility. I use WOW keyboard bindings to map Wheel up and Wheel down to action bar items. I use both hunter macros (cast sequence with Kill Command, and the separated cast-cast macro, also with Kill command.

There have been a few improved kill command macros posted - I'll try those and try removing kill command altogether.

[ Post edited by Difool ]

by Hortus | 30/01/2008 18:48:32

Hortus

Hi everyone. I've seen a lot of posts about this here and on the WoW Europe forums.

First I'd like to make sure that I understand the issue being described...

When using Kill command your UI starts responding as if the CTRL key on your keyboard is stuck down. The only way to get the UI to respond correctly is to use Kill Command again.

Our UI specialist has tested this extensively and can not reproduce this problem. We would like to double verify that this is not caused by any sort of UI mod, can anyone confirm that this still happens with NO UI MODS INSTALLED? Also those of you who are experiencing this are you using the Mac or PC client?

Any information you can provide to help us identify and reproduce this issue will help us get it fixed.

by Hortus | 19/02/2008 17:29:40

Hortus

Hi everyone, after extensive testing we have identified this issue and we are working on a fix.

Bump! Recently Bumped Threads

 

Blizzard Announcement Recent Blizzard Announcements

 

We suggest