Hello. After 4 months of suffering with crappy mouse/no mouse problems, I finally got myself a mx518. I have a few questions on how to optimize the thing to its fullest. Can setting it to 1000Hz physically damage my mouse/cpu? Which dpi (400/800/1600) is best? Should I use mouseware instead of setpoint? Tips on speed/acceleration? Is using all 8 buttons necessary?

Thanks and glad to be back.

hi, i've got the same mouse and i love it. I did the following things to optimize it for qw.

applied 500hz patch (1000hz is to high as it wil be 750hz average, which gives a lesser smooth feeling than 500hz)
use setpoint drivers since mouseware won't work. in setpoint disable all aceleration shit. use 1600 dpi. ive got my sensitivity set at the 4th point. uncheck game detection. use setpoint implementation for accel and speed. and finally add -dinput to your cmd line and remove all other mouse cmdline options.

*edit* i forgot to mention that i also use libusb-win32. it's a port from libusb. i forgot exactly what it did for my mouse but it was better than windows original driver http://libusb-win32.sourceforge.net/

that's it, gl

I would settle with 500Hz if i were you. I've read several threads on forums where people blame the deaths of their mice on the higher polling rates.

........

I cannot believe how good this feels at 500hz with no accel/smoothing! Excellent setup. Thank you so much

Anybody recommanding settings for rzwor diamondback?

Ok, ive gone kinda nuts with mouse settings recently, and i think ive gone as hard as i can go... ive been using the same settings now for only a few weeks, but all the tweaking seems to be paying off. I also have a mx518, so heres what ive learnt...

Personally, these settings give the best control/speed ratio:

- 1600dpi (der!)
- 1000hz
- default windows drivers (no setpoint) - remember to press the '+' button every time you boot into windows
- pointer speed set on 3 (2 notches up from the lowest setting)
- ezquake cmdline: -dinput -noforcemaccel
- sensitivity 3.5 (seems to be the sweet spot for these settings on my machine)

Its funny.. ive never had my desktop cursor move so slowly, but for the benefits im getting in quake, ill put up with it Its worth noting that the default setpoint cursor speed is, from memory, set on 3 also... so im thinking im on the right track. Also, fps/freq has an effect on how the mouse feels -- 77fps/77hz feels very different to 200fps/100hz (what im currently using in ezquake).

Everything else is minor.. To me, the best thing i ever did was reintroduce -dinput into my cmdline (i had read on this very forum that -dinput was bad, so i removed it.. bad idea). From there, i just screwed around with the windows pointer speed and quake sensitivity to get it right.


eek... might buy another 518 just in case ;p

I use 1000hz under winxp just fine whereas a friend of mine used 1000hz until i told him his mouse was lagging :/ Changing down to 500hz fixed that for him. Wierd.. maybe he has crappy usb hubs or something. I cant get 1000hz working under win2k either.

Anyway, good luck with it

try mouserate.exe to see what hz you really have. when i use 1000hz, i don't get a steady 1000hz. its changing from 750 to 1000. however 500hz is steady. a steady polling rate of 500hz gives a smoother feeling than an unsteady 1000hz.

hmm... When you say a 'steady rate', what do you mean exactly? in mouserate.exe, fast movements will register higher readings than slow ones, so im not sure where the inconsistency is.. i seem to get consistent readings for the motions im doing, but then again.. its polling so fast its probably impossible to tell ;p ill reboot after i post this and try 500hz + mouserate.exe and see if its any more er, consistent ;o

hehe, i see what you mean.. my fast movements register up and around 500hz nearly always, wheras before they would fall between ~850 - 1000. might give this a try now, thanks for the input vleech

Update: you were right, aim feels more consistent

My computer lags in glqw if I use 500hz . About 20% CPU usage if I wobble the cursor around on the desktop.