by Fuddl » Thu May 15, 2008 11:58 pm
i've seen probably the same problem on a friend's notebook for the first time about a year ago and it's still present (i'm talking of debian sid here, so the problem survived many versions of different software). the notebook was a core duo thingy, with a nvidia gpu.
we managed to show off the problem as far:
in the menu, we could - only sometimes, not fully reproducibly - move the mouse to the right and nothing happened with the mouse cursor on the screen. a few seconds later we moved the mouse up, but on the screen the mouse cursor moved first to the right (which apperantly was the previous movement of the mouse) and the upward movement of the mouse cursor appeared delayed on the screen.
so, the input data from the mouse wasn't dropped, but somewhat blocked and delayed.
the same thing happened in another game, sauerbraten, too, but it did not happen in all games. as far as i can remember it did not appear in quake4.
a year ago, we managed to work around that problem, but neither my friend nor me can remember what we did, sorry!!! :( (i can remember what did NOT fix it: the gl_finish-thing, telling SDL to not use the DGA mouse input data and to different linux kernel versions)