Re: Anti-gaming Behaviour of Keyboard Driver
- From: JoseC.Rodriguez@xxxxxxxxx
- Date: Tue, 20 May 2008 02:38:48 -0700 (PDT)
On May 19, 12:40 pm, "Dmitryi & Elf" <sidhecha...@xxxxxxxxxxxxxx>
wrote:
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.
Uhm...in my case I don't think it's the same issue. For some reason I
can't strafe backwards; this is, the combination of backpedal+strafe
works, but it doesn't get any more input, so I can't jump. I thought
it was a limitation of my keyboard...
--
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: Dmitryi & Elf
- 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
- Re: Anti-gaming Behaviour of Keyboard Driver
- From: Dmitryi & Elf
- Anti-gaming Behaviour of Keyboard Driver
- Prev by Date: openoffice java problem in sid
- Next by Date: Re: problems installing openoffice.org in etch
- Previous by thread: Re: Anti-gaming Behaviour of Keyboard Driver
- Next by thread: Re: Anti-gaming Behaviour of Keyboard Driver
- Index(es):
Relevant Pages
|