An Always Running (moving) bug

[MRRX]

<p>I am experiencing a non-stop-run bug.     I'll push a movement button or perhaps two.   Then, the character continues that movement until I once again push the button.   This can be backing up, turning, or running forward.    So if he gets stuck running, when I push the Forward key, he will stop.    If I let go of the Forward key, he'll run forwards.   Autorun is not active and doesn't affect the bug.</p><p>This happens a few times every day; the only workaround is to close the game completely and restart.    In the meantime I have to find a corner to run my character into or he'll run off cliffs, etc.</p><p>Any ideas appreciated.</p><p><a href="http://togameforlife.wordpress.com" target="_blank">togameforlife.wordpress.com</a></p>

[Therendil]

<p>I get that, but very very rarely. I more often spin around non-stop after keying a left or right turn. Since I have duplicated it with multiple keyboards on multiple systems, I think it's a bug in the client's basic input routines. I have been filing /bug reports on it for at least a year. Please /bug it whenever it happens. This is the first report I've heard of it happening frequently. If more people /bug it and it's happening more, they might try harder to fix it.</p>

[Baruche]

<p>I've had both the "spin" and "constant running" bug happening off and on for quite a while. I used to camp to desktop and restart the game to cure it, but I found an easier fix. Once I get in a safe spot, I "ALT-ENTER" to windowed mode, then minimize the window. When I maximize it again, the bug is gone and I can then "ALT-ENTER" back to full screen. Much better than logging out and back in, but the bug is still irritating nevertheless.</p>

[TSR-JoshuaM]

<p>What needs to be understood is that there are events tied to pressing a key AND releasing it.  These are not EQII specific, this is how the drivers for your keyboard/system operate.</p><p>When a key is pressed but the system does not receive the event to release that key, it gets stuck.  This can be emphasized, and reproduced, by holding a key down like shift and alt-tabbing or during a moment of graphical lag (FPS stutter etc).  Until you push that key again, the system cannot 'release it' because the program it was pushed in is no longer in focus.  When reproduced with arrow keys this can result in spinning and so on until you hit the stuck key again (so the system can properly receive the released key event).  </p><p>However, this doesnt explain the original posters issue, just the subsequent follow ups.  That sounds more like 3rd party software may be interfering but I would need more information.  Please open a support ticket and include your DXDIAG/MSINFO files so we can review your system and make recommendations on what may be causing the problem.</p>

[MRRX]

<p>I discovered that I could stop the bug in-game, twice.    With my character running (and turning), I went into the options menu, keyboard controls, and I removed some of the run keys listed there by default.    I don't use the numpad keys so I removed them.    The bug did not reoccur last night.   I'm hoping it won't re-occur.</p><p><a href="http://togameforlife.wordpress.com" target="_blank">togameforlife.wordpress.com</a></p>

[Therendil]

<p>Okay. I'll see what I can gather up. I need to point out that I have reproduced this bug on a Dell Keyboard (USB) a Logitech keyboard (wireless) and the keyboard on my Gateway laptop. The Logitech keyboard had also shown the issue on both systems. Now I suppose it's possible that Microsoft, Logitech, and Gateway all have the identical bug in their input routines, but I find it easier to believe that it's a latent race condition in the client input routines, especially since I do not see this issue in WoW, Rift, or <em>anywhere but in EQII</em>.</p><p>Good point about key_down and key_up being separate events. Same is true for mouse_down and mouse_up. You do have to make that distinction when reporting errors, and I'm not quite sure in this case which it is. Need to look into that some more.</p>

[Therendil]

<p>Hmmm. I do have multiple keys bound for movements. If I remember correctly, the issue triggers on the arrows or numpad keys. Need to try a few things there.</p>

[Sandyfoot]

<p>I've had this happen in the past, but not currently in EQ2.</p><p>The cause in my case was Norton Internet Security's pulse update and subsequent scan. It was caused by the "SONAR heuristic technology" that is used to check suspicious characteristics.</p><p>Viewing the logs of the security suite may indicate statistical information being collected and sent durring the times the odd keyboard behavior happens.</p>

[Therendil]

<p>Interesting. I have MS Security Essentials running with some real-time elements. I've turned off scanning of downloaded files, but left other heuristics going. I will try to include that stuff in my state analysis the next time the bug shows up, especially since it is common to all setups I have tested.</p><p>One of the painful lessons I learned ten years doing QA for driver guys trying to write new drivers for Win2K was just how easy it is for a thread to trip and fall if <em>anyone </em>makes a mistake.</p>