Negative Acceleration..
•
16 Dec 2006, 15:16
•
Journals
Right so here are my mouse settings etc..
Mouse: logitech mx518
Hz: 500
Windows sensitivity is default (6th notch)
Mousefix.reg is already in use
and mmforce
1600dpi
/cl_mouseaccel = 0
and i get a hella of a lot of negative accel, NO i dont want to use 400 dpi or anything other then 1600, but their must be some way to at least reduce the crazy amounts of negative accel i get with 1600, cos i kno i can..i jus need to use some programs or tweak some settings, but i dno which and what to do?
So any help would be gr8ly appreciated, cheers :)
Mouse: logitech mx518
Hz: 500
Windows sensitivity is default (6th notch)
Mousefix.reg is already in use
and mmforce
1600dpi
/cl_mouseaccel = 0
and i get a hella of a lot of negative accel, NO i dont want to use 400 dpi or anything other then 1600, but their must be some way to at least reduce the crazy amounts of negative accel i get with 1600, cos i kno i can..i jus need to use some programs or tweak some settings, but i dno which and what to do?
So any help would be gr8ly appreciated, cheers :)
i don't think there's a program or tweak to fix that
Btw solutions: higher resolution, higher ET sens/lower windows sens, lower dpi, higher fps
maybe something else also :/
accelfix.exe
1000 Hz
r_mode 4 or 6 max.
steady fps, few (like 5) more then your displayrefreshrate. (120 Hz + 125 fps) (85Hz + 90 fps)
NO mf_init/mforce
NO accelfix.reg
NO setpoint drivers!
I'm no guru but this is how I think it should be.
just change to 400 and test ur sensivity and play with it for a while, it sux in the beginning but after a day or 2 u'll get used to it
gl tho :)
Should do the trick
You sure youre getting negative accel? sounds like placebo tbh...
The ESR mouse benchmarking shows that mx518 at factory settings will go to 2.03m/s without negative accel, so you're either imagining it or your mouse sensor is broken somehow.
There are two kinds of neg accel. The one sujoy is talking about is your mouse not able to track very fast movements. The one he is prolly talking about is Q3 being overloaded with data (high dpi? low resolution? low mouserate?). Both have the same result. When moving the mouse slowly all the movements are translated correctly onto your screen. When you do it very fast some of the data is either lost by your mouse or by the q3 engine wich doesnt support direct input.
nice try though :P