Tweet
There is this proquake command line option i just found out about, -dinput. It's supposed to stop the windows xp mouse acceleration. it sounds like it could help my aim..... do you guys use it, know about it, recommend it, etc?
-
-
THERE'S NOTHING WRONG WITH your aim, i played u last night!!!!
-dinput carries direct input settings to quake. Sometimes its better, sometimes its worse. It used to be better for me when i got WinXP, then i got a new mouse and it's not so good. Though, I hear there is a registery setting to disable the acceleration in XP for good. Either way, try -dinput and without. I myself find when i am in a surprise situation i end up over aiming, where I used to be able to "flick" my mouse and 180 pretty easy. I guess i am rusty. (damn all night coding endeavors!)
btw on my logitech 518mx and winxp mouse settings left ALL at default, my sensitivity is set at 2! 
-
Try these instead -noforcemaccel -noforcemparmsComment
-
Wow thanks cataklysque... Those made the glpro aim much more accurate.. Its almost like DP aim now!Comment
-
what exactly do those do cata?Comment
-
thanks for the help guys. i'm not sure i noticed much difference with those commands cata. nor did i think there was any problem with my aim b4, as rook said; i just thought that maybe it was something bad I had adjusted to over the years, and could improve my aim by adding -dinput. but yeah it did feel weird. i'm gonna stick with -noforcemaccel -noforcemparmsComment
-
-noforcemaccel
Description: Disable the forcing of mouse acceleration on startup.
-noforcemspd
Description: Disable the forcing of mouse speed on startup.
-noforcemparms
Description: Disable the forcing of mouse parameters on startup.
* note: noforcemparms turns off both acceleration and speedComment
-
thanks rook! but i dont understand something--what does it mean to disable speed? sounds like it would stop mouse from moving at all lolComment
Comment