500hz = 2 ms, 1000hz = 1 ms, yes it's sufficient. 125 = bad.
Why not just use 6/11 in windows?
For Abyssus, use v2.00 drivers, those work fine.

Why use drivers?

No reason not to. And setting sens.

No reason to use. Mousefix + hardware switches on the mouse.

dunno about the rest. but my abyssus tracks hell of alot more consistent @ 500hz

this. I have a paint-test I did with mine when I bought it, I might remember to post it again when I get off work.

But yeah, it was totally fucking unusable at 1000hz if I remember right, and 125 blew ass too.

so u can set the abysus to 500 hz as well, not just 125 or 1000?

there's a switch for only 125 and 1000 on the mouse. but you can always use traditional methods as well

http://www.esreality.com/post/2428604/re-usb-...pid2428604

what, i posted in more than 1 place to be sure i get an answer

6/11 win sens. - I don't think the 4/11 will necessarily harm it, but it's better to keep it on 6/11

1.27 is ok depending on how much cm/360 you have and play style. Perfect control isn't a huge factor when it comes to mouse accuracy.

500hz is sufficient - if your mouse isn't 1000hz by default or has the ability to change hz on the fly, most people just tune it up to 500hz.

500hz isn't stable even with the abyssus. Atleast it was on my pc.

What games do you play? If they have raw input like quakelive then all that slider bullshit and accel fixes go out the window.

This!

I hate engines with no possible raw mouse input at all.

iirc raw ql still honors driver slider (and just is factoring it down to another cpi, purely mathematical speaking)

I confirm it does.

Makes sense. But it still means there's no 6/11 and accel to worry about.

Does it do that with in_mouse 2?

my abyssus has only 125/1000hz hardwareswitch on bottom. How do you change to 500hz ?

Isn't 125hz enough? It doesn't have buffer overflow problem like wmo and 125 hz is your frame rate.

On the other hand it may be that 125hz has 8-16ms delay while 500hz has 8-10ms.

Can someone confirm this? Is it even noticeable in game?

Read my first post...
And mouse polling rate got nothing to do with your frame rate...

Of course it's noticeable, set it to 125, join a game and start looking around, the lag will be obvious.

Ultimate goal is to reduce latency. Latency depends on both - mouse polling rate and fps. My naive understanding of how latency is introduced leads to the conclusion I gave in previous post (second paragraph).

If you can explain it better then pls do it. I'm not looking for an usurper e-authority (125=bad 500=good) but for rational explanation or at least conclusive experiment.

I can't test it now as I'm not accustomed to using mouse atm and I won't feel the lag. I can't switch polling rate on the fly too.

Sure, but you were trying to suggest that 125hz is cool or something since that's your frame rate, but that just doesn't matter.
Lower or higher fps itself isn't latency, you just see less or more, you can have latency on your frames that are being put out though.

1000hz means it's being polled 1000 times a second, 1000ms/1000 = 1 millisecond.
125hz -> polled 125 times a second -> 1000/125 = 8 ms.

I didn't suggest anything. It was a question.
By latency I mean latency between your mouse movement and crosshair movement on the screen. Higher fps means lower latency (at least until you hit your mouse polling rate).
There was this very detailed article on input delay in gaming. I'm going to find it but I'm not sure if it was this detailed.
edit: No it isn't. This is why I wonder if there is perceivable difference between 125hz and 1000hz.

No it isn't what?
And there is, I just told you, now you can stop wondering.

Ok.
Type com_maxfps 20 and tell me if it feels delayed?

edit: Ach - "No it isn't" meant that this article I was talking about isn't this detailed.

Yes, there is a perceivable difference between 125 and 500. Even from 125 to 250. The only unperceivable difference is from 500 to 1000.

125 fps will not sync with 125 hz input rate to provide a raw input info for every frame. The bigger the pool of inputs, the smoother the movement. 125 hz will feel laggy, 250 and above will feel perfectly smooth. Delay-wise there is no big improvement, since the hard cap is your actual fps. But in smoothness it's obvious.

Screen and mouse are not connected to each other.

Your screen might be 120hz, but you can actually react with your mouse before it updates on the screen.

So for example, you spot a guy and you are going to flick rail him. If you do it on 125hz there will be up to 8ms lag to make the shot. On 1000hz there will be 1ms lag.

Since it's a flick rail you do not need to track or follow the screen at all, everything depends on your mouse movement.

The difference is purely reaction speed, actual tracking won't be affected (well maybe the position on the screen will be more accurate)

125hz -> 500hz is quite noticable. The easiest way is to use 500hz for a while and then switch back.

I'm writing about input/output delay not reaction time.
Things like reaction time or actually shooting ppl (keep in mind that hits get registered on server not locally) are far more complicated.

Like any other mouse - hidusbf.zip.

Yes Windows slider affects precision. Only with the default 6/11 (?) can you get 1-1 ratio precision on the mouse. If you lower it windows will throw away information and if you up it it will add as to de-/increase mouse sense.

I use a salmosa sensor with the abyssus top shell part. I know noctis and winz did so too for a while. Anyone else?

Did the same at one point.