News:

Come Chat with us live! Learn how HERE!

Main Menu

Keyboard Stickage

Started by Syntac, September 08, 2008, 10:42:50 PM

Syntac

Occasionally, when I press one of my strafe keys (Z and X), the game thinks it's pressed even after I release it. I then have to press it again to make it unstick.

Specs:
- Intel MacBook (second generation)
- Mac OS X 10.5 (Leopard)
- 2.2 GHz Intel Core 2 Duo processor
- 1 GB RAM

This happens in Nexuiz as well, but not in any other application. Perhaps it's a problem with the Q3 input system?

David

I believe its caused by packet loss, and the server doesn't get the message saying to stop moving.
cg_lagometer 1 and see what it says.
Any maps not in the MG repo?  Email me or come to irc.freenode.net/#mg.
--
My words are mine and mine alone.  I can't speak for anyone else, and there is no one who can speak for me.  If I ever make a post that gives the opinions or positions of other users or groups, then they will be clearly labeled as such.
I'm disappointed that people's past actions have forced me to state what should be obvious.
I am not a dev.  Nothing I say counts for anything.

Syntac

I don't notice anything different in the lagometer when stickage occurs. In Nexuiz, it even happens when I'm playing the single-player campaign — and in that case, there shouldn't be any packet loss.

UniqPhoeniX

Not sure if it's related, but it happens to me after I press alt+tab and then quickly switch back (alt+shift+tab) without letting go of alt (with windowed mode), and press alt (binded to sprint) while moving. But that also causes trem screen to freeze until I repress alt.

Lava Croft

I just want to note that Nexiuz is based on Darkplaces (Quake), and has little to nothing to do with Quake3.

+ OPTIMUS +

#5
[EDIT: i tought something is yes but its actually not yes]
success is the ability to go from failure to failure without losing your enthusiasm

+PICS+

Syntac

Quote from: Lava Croft on September 09, 2008, 08:44:21 AM
I just want to note that Nexiuz is based on Darkplaces (Quake), and has little to nothing to do with Quake3.
Okay, fair enough, but maybe it's just the Quake input system in general that's causing this.