Low fps causes negative acceleration in source engine games. Use less dpi, faster overall sensitivity or get more frames per second. It uses DirectInput but has a small buffer which is only sampled once per frame. So you can see how getting less than say 75fps could suck hard. Another solution is to use razer sensitivity and reduce the cpi of the mouse. It should carry over in-game since razer sensitivity acts before the desktop level I believe.

Thank you very much Antigen. I've posted this same topic on CAL forums, GotFrag forums, as well as on ESR. I've had an initial misconception with the Razer DeathAdder. I always thought it had negative acceleration in any game, but now I know I was wrong.

After using it to make a final test in Nexius with mforce (to force DirectInput), I found that the mouse tracked my movements with excellent precision and I could not get any negative acceleration. However, on TF2 I always got negative acceleration, but I do have a low fps that is lower than 55 fps (highest is 50 fps in server).

I revoke my past criticisms about the Razer DeathAdder. It worked wonders in Nexius and I'm sure it will work wonders in TF2 once I save enough money for a new computer.....hopefully by the end of August....-_-;;

Just out of curiosity, how do you know that TF2 uses DirectInput using a small buffer?

because I used to play source and encountered problems with the deathadder's high DPI and high inch per second combination.

Anyone using this ?

http://razerblueprints.net/index.php/componen...ic,5245.0/

...The latter one ("mf_hybrid.dll") however is a bit different.
As the filename already suggests, it combines the two methods DirectInput and Set/GetCursorPos to benefit from both solution's advantages (DirectInput's reliability and Set/GetCursorPos' responsiveness).
As long as the cursor is unable to reach the screen's border(s), its position delta will be used to determine mouse movement.
But when the cursor reaches the border(s), DirectInput snaps in to bypass this limitation.
This method is primarily useful for those, who consider DirectInput's mouse access delayed, but do not want to experience possible "negative acceleration".

Me myself used "mf_hybrid" for Q³ engine based games. It worked very well. (even with Cod4)
However anir/aion (the author) claimed a few times (like 1 year after its release) its not recommendable to use MouseForce and he shouldn't have released it at all. He never cleared that up.