Probably you got a faulty USB port/controller or drivers issue. I'd start by checking those things out first.

Moving to a different USB port, which I assume is on a different controller, doubled the DPI to 400.

Hmmmm.

Are you sure your OS is patched correctly? Has the mousetest ever reported 1000Hz?

Yes, 1000Mhz reported consistently (by two different apps).

Enotus mousetest? I'm sure I saw it being discussed that that is really broken.

I've never been happy enough with SO many virus reports being claimed as false positives to run it here though.

stuttering - mouse surface issue?

Enotus mouse test has always been accurate for me, you just need a ruler with it.

I'm using the SS QcK mat, shouldn't be an issue with optical.

Oddly, the mouse works fine using my (wooden) desk in Windows, but in QL, the same surface causes severe issues (hardly any movement, and if it does move, very laggy).

What on earth could be causing that?

https://www.dropbox.com/s/0y9flaallw8r145/MouseTest.rar

When I used 1000 Hz on my SS Kinzu v2 i had small Fps drops when i moved the mouse. When i switched to 500hz i have almost stable 250 Fps.

Maybe you should check with cg_drawfps 1

Tested this last night, FPS is locked on at 250 far more using 500Mhz over 1000Mhz. Madness.

From reading what players have said, either here or on Oc.net, I don't use 1000Hz any more because it can cause more problems than the benefits it has over 500.
I got micro stuttering from using 1000Hz.

In enotus check the smoothness test, there are other apps to check this.
I found that higher polling rates have very inconsistent/choppy signaling, on my kana v2 on win 7 and 8.1.
I run 800dpi/250Hz now on the kana with a dirty crt @120 it feels as good as my WMO @ 500 like this.
so try a lower polling rate maybe.
btw enotus is clean once unpacked.

Thanks, will try 500Hz.

Got the exact same issue for 4-5 days now, using kinzu v2 400dpi@500hz :(

What operating system are you using? And which mouse drivers?

Win 7 64bit now, thought its win8.1 based, still the same shit :(
Tried diff pads (qck+/heavy/goliathus ctrl)
Using SSengine (latest)

Issue came out of nowhere :/

After Yakumo mentioning the surface I've ordered a QPad FX, a coated cloth, so we'll see if that helps.

Disappointing that the Win 7 install didn't fix it.

That .exe came with a bitcoin miner. Might wanna stop toggling.

you're saying he's part of a bitmining botnet?

I had some issues with mouse stuttering/freezing when I went to 500hz, but it went away when I changed the usb suspend settings in power options.

I'll try this, thanks. I assume it's in the Control Panel, and not the BIOS?

"I'm using Windows 8.1 with the 1000Mhz hack, Zowie FK and in_mouse 2."

why 1000 hz hack?

It's the registry edit that allows a polling rate above 125Hz. It's locked at that until you do it. 1000 just because that was the mouse default.

even if the mouse itself does 1000hz, win8.1 still needs a hack?

why are you editing the registry to do something the mouse itself does natively in hardware?

http://www.vortez.net/articles_pages/zowie_fk_review,5.html

See below comment.

Yes, otherwise it's always 125Hz.

in_mouse 2 (raw input) will give you the desired polling rate in game too, although the hack is worth doing as you can apply it system wide with one regedit entry.

What made you conclude that this software-free feature of the mouse, doesn't work?

I'm finding lots of discussion of the mouse and changing polling rate, but no mention of having to use additional hacks to use it, only the button combo when plugging it in, as Zowie advertise.

I never stated it didn't work, I listed the Win 8.1 hack as information which may have been useful to someone who had tried similar.

in_mouse 2 works with QL without touching any registry settings, but the OS itself benefits itself from the higher rate. It's also helpful to see any rate changes confirmed via mouse testing applications. Something you can't check in game.

My point is, it sounds to me like you've used a registry hack, to try and achieve something the mouse is supposed to do entirely on its own in hardware, irrespective of what game / game settings you use.

And you are having strange problems with it.

Reverse the registry hack and use the hz function of the mouse as intended.

I most certainly needed that clarification, completely misunderstood you :¬)

I'll try it - thanks.

Probably unrelated and not useful note:

timenudge is off when you're spectating, so if you normally use -20 or somet then spectating will appear more smooth.