if you get huge FPS drops when you shoot (when rocketjumping, for example), sometimes quake doesn't realise you have already let go of the button.
Try lowering your visual settings such as picmip (set it higher in this case), and try playing after that.
Can't think of anything else, hope someone with better knowledge shows up.

@ gaiia,
i got 125 fps steady all the time , got a good computer and bad graphics settings :) but thx anyway.

Picmip doesn't actually help fps that much:D

Not on modern day computers anyway.

Does it work with in_mouse "-1" ?

I had that problem with a razer copperhead and since i changed to a deathadder it works perfectly. I guess it's a mouse problem :/

Edit : shlaeNg must be right, i didn't use cnq3.exe when i had this problem.

Kaloos,
it didn't work:(

Lower polling rate
Use cnq3 exe

shlaeNg,
i tried cnq3, now it works :) but now all my settings are getting back to what they was before i started using cnq3 :O for example, i change my sensitivity to 1.3, after 10min it's back to 2. and the samething happens with names,controls etc

you have to save settings through console (²) :
\writeconfig q3config.cfg

i open console and i write /writeconfig q3config.cfg, then i press enter, and i write /sensitivity 1.3, then i press enter again and what do i do next ? sry i dunno shit about these things :>

well i tried to just restart the game and then /exec q3config.cfg and it exec'd but still my sens wasn't as i would have been :((

You have to make all your changes before you do /writeconfig q3config.cfg

ahaaa :D ! haha, i'll try it out :p thx

YEY it worked :) thx y'all

quake3.exe can't handle 500 or 1000 Hz, as schlaeng says use cnq3.exe. www.challenge-tv.com

quake3.exe

Mine can!:D

Mine too, but only because I renamed CNQ3 to quake3.exe :D

In quakeworld one can adjust the size on the direct input buffer, why doesnt q3/cpma have this? defult value is way to low for 1000hz high dpi mouses.
Also non-direct input is fixed in qw also, no possibilitys of hiting the edge off screen with movecursor/getcoursorpos.

Because direct input buffer is OS specific and I think it's still attempted to make cnq3 cross-os.

No, qw doesn't have that.... ezQuake does though (and maybe some other builds).

Looking at the ezQuake code though, it looks like someone has made it so that it dynamically bumps up the buffer size as soon as it sees overflows, which is maybe a good way forward (although that isn't enabled by default)

However, cnq3 has already bumped the default buffersize from 16 up to 64, which is why it doesn't need to be raised in cnq3 (while the default in ezQuake is still 16, at least in the svn snapshot I have). So why make it an option when it does not need to be? Its just another cvar for people to get wrong.

As for non-DX, I see no sign of a solution to the clipping issue in ezQuake - other than it also supporting raw mouse input via WM_INPUT, which means that it cannot be run on Win2k (without recompiling to disable support for that).

I have one problem. I made my own config and when i want change my crosshair color doesnt work. CH_CROSSHAIRCOLOR ( i try with numbers and letters, then i try over menus and options and doesnt work. Can somebody help me cuz i dont now what to do.

rtfm

no need to thank me.