Are you sure it's mouse related? I kinda doubt...
I had microstutter issue @ 120hz when I bought my screen, you might be having the same or similar. ..
ATI gfx card?

Try 500hz for the WMO, I heard 1000hz is buggy.

not really onTopic but: on my DA3.5 one sidebutton is dead too and the 2nd begins to feel kinda loose. considering the rest of the mouse is still in good shape thats a shame.. seems like those buttons are just cheap junk D:

Actually this is what happened to mine. The side button closest to me has become loose and has like fallen halfway into the mouse. :|

EDIT: It's weird too because it just happened to be in that state one day when I came home from work. Seemed like someone threw it on the ground or something.

http://www.youtube.com/watch?v=gAYL5H46QnQ&ob=av3e


couldnt be helped.

i bet that wouldnt hurt the mouse itself but both sidebuttons would fall halfway inside instantly and loose all feedback - even before touching the ground :D

rzr, i am disappoint

Happens to me when I am on 125hz. Do what gillz says - from what I've seen most mice don't do stable 1000hz.

Mine is stable.

you have a nvidia card right? i have the same problem and i think its due to nvidia, someone told to downgrade to an older version but i can't remember witch one... would be awesome if it turns out it isn't due to nvidia and fixable though...

I have ati radeon

yea well, apologize if I misunderstand your problem, but you're talking about choppiness with rocksolid fps etc... so I'm thinking it's microstutter.

I have no experience with nvidia, but ati have this powersaving feature, which isn't something you can disable in a control panel easily. what happens is, since QL doesn't put any load whatsoever on your vidcard normally, clocks are being adjusted constantly and it causes the microstutter.

what you do is get any OC tool(i use official amd gpu clock tool, it's simple and works), and set fix clock values. for example on my hd5850 default clocks with powersaving at desktop are 400/900(much lower at lower refresh rates but 120hz requires higher to operate apparently), so I just set it to like 730/1000 which is close to the default 3D values. the point is that it overrides the powersaving feature.

yea it can be annoying to do this all the time but i got used to it.
I forgot it a couple of times in the past before playing and ofc noticed the occasisonal weird unsmoothness during game.

Happened on MS WMO and MS IME 3.0 at 125 hz for me as well. Setting port hz to 500 allowed to alleviate this problem to some extent, although it was still not as smooth as for example DA of Abyssus.

did the same for me when i accidentally unplugged my mouse and put it back. that made my mouse go from 500hz back to 125hz. then i applied the hidusb thingie again and it fixed it

same thing, wmo, 1000hz, maybe ill try 500hz :S sometimes it feels ok but often its choppy as fuck

difference between 1000 and 500hz is a whopping 1 ms, but 1000hz is usually unstable so you should always opt for 500.
you can use some apps to track mouse refresh rate, such as 'mousemovementrecorder'.

only with WMO? Can you list the other mice doing same ?

Actually all mice i use do it, its just my death adder did it very little.

overclock to 500hz....

Same thing happens on 500hz :/

I had a similar issue with the mx518 where I used 125hz and it felt choppy and then went to 500hz and felt a tiny bit inconsistant and the to 250hz where it was great , the only explanation I found was when I used a hz checker and it gave me fairly jumpy values at 500hz ( which is normal with most mice really ) and the at 250hz it would almost always be (220-250hz).

I had also problems with it on mx518, but it was lagging a in some moments on any refresh rate. I bought refurbished version of mx518 so I assumed this was the reason. Finally I gave this mouse to my brother and it works well for him, but he doesn't play Quake anymore.

See if the driver software is running twice or something... and check your memory usage in the task manager..

Driver software? wmo has no driver software. Unless you mean my razer DA.

I recommend setting your Hz to over 9000.

Try changing r_finish

OMG I enabled post processing and its fixed.....