ive reinstalled xp and now there is very noticeable negative accel. my old setup though bloated with broken software and registry etc, had perfect mouse.
my setup:
g5 setpoint 3.1.116
ati radeon x700 latest drivers (new 'control center' required .Net 2.0)
xp corporate
setpoint- game detection on, keep mouseaccel, keep mousespeed, speed slider on 3 mouseaccel none, dpi 2000, khalmnpr.exe and setpoint.exe in realtime priority
redistributable directx 9.0c (59mb) (i tried to download full (~120mb) from microsoft, but i couldnt validate. maybe they have crippled the free version?)

my old setup differences:
setpoint 3
ati radeon older drivers, control center didnt need .Net
xp professional
no .Net
directx 9.0b or c full version

how would that rule apply to the new TFT monitors.. wich are supposed to run qw at monitor's native resolution for best performance (even response).. ? i mean.. i've a 19'' wide screen TFT monitor and run qw on its native resolution - 1440 x 900 .. my mouse only got 1800dpi ( diamondback 3g ) .. so i guess i should be using 960 x 800 in order to get a bit closer to my mice dpi.. what should be the 'priority' on that case ?

If I recall correctly, I think you can look in 2^32 (4,294,967,296) directions from a single position, regardless of resolution.

so def's statement is bullshit? ;o

It's intended for introducing people into the setup and QW, I presume. It also depends on your sensitivity. Sujoy commented on this HERE. You want to take in consideration your fov (if you're using fov 120, it'll be screen res*3 instead of screen res*4 for the number of pixels in 360 degrees) and how "precise" you want your aiming. This is also just a general guideline, and there are plenty of people who use 400 dpi mice in high resolutions with relatively high sensitivities and have 0 issues, so preference is best.

Hence

Noticed the bolded part.

Edit: Sujoy even says "While 3D games don't need you to turn a whole pixel before the screen changes, this is a sensible way to work out when more DPI resolution stops being useful."

Feel same - SW more realtime game, than GL.

Solution to make GL closer by realtime to SW is disable pixel-interpolation in GL-driver, setup it on possible minimum (2x for my 8800 NVidia).

for me GL > SW when it comes to shafting

i have a really lousy shaft (esp on dmm4 maps) in SW (28-32%), but in GL average was something like 35-38%

RL and movement on the other hand feels muuuuuuch nicer in SW imo, thats why i switched back

Reppie, you have CRT?
Try disable pixel-interpolation, setup max_hz on monitor and cl_maxfps 1078 (77*14).
It gives movements in GL even smoother than in SW