[quake2] Highly erratic mouse behavior

Brendan Burns brendanburns at comcast.net
Thu Mar 17 14:42:46 EST 2005

Its my experience (from fielding mouse problem reports from a lot of 
different people) that mouse issues are often weird system level 
interactions between X, the kernel and the graphics card.  Lots of 
different people running the same code see different mouse behavior.

One thing you might try is explicitly turning DGA of in your X server.  
That may help (or try turning it on, if it is already off...)

that last statement reminds me of a joke I heard recently:
Four engineers are in a car driving down the highway.  The car stalls 
and they stop it on the side of the road.  The mechanical engineer 
says, "its something with the engine, we've got to take it apart until 
we find the problem."  The chemical engineer says "no, its the gasoline 
that's bad."  The electrical engineer says "Its probably the battery."  
And the computer engineer says, "I think if we get out and then get 
back in it will work..."


On Mar 17, 2005, at 2:05 PM, Anders Storsveen wrote:

> Anyway I have mouse acceleration in quake3 too, but I can't find any 
> linux support maillinglists/forums. Anyone know anything?
> On Thu, 17 Mar 2005 12:49:51 +0100, Julien Langer <jlanger at zigweb.de> 
> wrote:
>> On Sa, 2005-03-12 at 17:35 +0100, Anders Storsveen wrote:
>>> I'm 100% sure that this problem is mouse accelleration related. I 
>>> have
>>> been whining about this for years now, linux
>>> seems to have mouse accelleration that is impossible to turn off... 
>>> It's
>>> like this in every game! I've posting
>>> around the net on this, and no one seems to figure it out.
>>> I've done xset m 0 0 and set the mouseaccel to 1x in kde. but nothing
>>> works.
>>> If you try to move the mouse very slowly you will get the following
>>> artifacts, in SDL you will get no or slow
>>> movment, and in glx you will get negative movment and if you speed 
>>> up a
>>> little you will get zero movment and then
>>> correct movment again. I'm definantly sure that this is some problem 
>>> with
>>> how X or some other backend handles mouse
>>> and mouse accelleration. I'm also betting that, in regular x with 
>>> mouse
>>> acceleration set to "off" there is still
>>> mouse acceleration, even though it is hard to detect.
>>> If someone made an app that compared raw mouse input to the length
>>> actually moved on the desktop I'm sure the
>>> length would change dependant on the speed, even though the physical
>>> length moved stays the same. But what I'm sure
>>> of is that mouse acceleration in the game is what this problem is, 
>>> it also
>>> affects other games including quake3!
>>> It's stupid to have to dualboot to windows to play games that are 
>>> native
>>> in linux and performes very well (and even
>>> better in the case of q3) in linux when compared to windows.
>> Hi,
>> I don't see such a behavior on my machine.
>> No matter how fast I move the mouse, the distance it covers is always
>> the same... in q2 and in q3.
>> And I have even enabled mouse acceleration in Gnome.
>> But it's true that there's no movement with SDLGL if the mouse is 
>> moved
>> very slow.
> -- 
> Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2377 bytes
Desc: not available
URL: <http://icculus.org/pipermail/quake2/attachments/20050317/905ce202/attachment.bin>

More information about the quake2 mailing list