Re: Anti-gaming Behaviour of Keyboard Driver
- From: "Dmitryi & Elf" <sidhechapel@xxxxxxxxxxxxxx>
- Date: Mon, 19 May 2008 05:57:24 -0500
Actually the problem is more straightforward. Quake locks key input when [Control] is pressed. That key is bound to fire, so until the fire action is released, the game won't recognise any new keypresses. Looks like scancodes get modified with [Control], and the game can't recognise them as valid bindings.
A different key bound to +attack fixes it, but still, this is a bug in the three Quake ports installed.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: Anti-gaming Behaviour of Keyboard Driver
- From: JoseC . Rodriguez
- Re: Anti-gaming Behaviour of Keyboard Driver
- References:
- Anti-gaming Behaviour of Keyboard Driver
- From: Dmitryi & Elf
- Re: Anti-gaming Behaviour of Keyboard Driver
- From: Rens
- Anti-gaming Behaviour of Keyboard Driver
- Prev by Date: Re: Realtek ALC662 microphone on Etch?
- Next by Date: Squid for apt.
- Previous by thread: Re: Anti-gaming Behaviour of Keyboard Driver
- Next by thread: Re: Anti-gaming Behaviour of Keyboard Driver
- Index(es):