Leaderboard

The Optimum Tech video on DPI latency / input lag used a flawed methodology to test movement latency as there was no normalised output distance for each tested input distance (DPI’s). He measured movement resolution, NOT latency. There is no input lag or latency effect at all for different DPI values. Imagine Usain Bolt was sprinting against a 5 year old and they both set off at exactly the same time. If we apply the same testing philosophy that we see in that video, we would only measure the time until the first foot landed on the ground, and because of their tiny little legs and narrow stride pattern, we would therefore conclude the 5 year old was the faster runner. Suffice to say, it’s not the time until first point of data, but the time to a significant target location to define “input latency” i.e input to “something”. Of course, a higher DPI would make “some first movement” faster than a low DPI at the same hand speed, as that is the definition of DPI, but presuming you have the same effective sensitivity in a game between DPI settings (i.e the same 360 distance) then the distance turned in-game is smaller for that first movement, so additional inputs (which take additional time!) would be required to turn the same distance as only one input would do from the lower DPI mouse. Once the minuscule amount of time has passed for the lower DPI mouse to send data, it updates to exactly the same position as the higher DPI mouse at exactly the same time. Saying there is a different “sensor lag” or "latency" for the natural effect of DPI is misleading - the path the data takes to your pc is exactly the same. In other words, there is no difference in input lag for different DPI values. What was tested is easily calculable with simple math and isn't required to test in this manner. If you could set the DPI to "1", and moved your hand at 1 inch per second, you would see 1000ms pass before the count was sent and their measuring devices registered some movement. This does not mean there is 1 second latency in the mouse input.

No, in the calculations output. The conversion is using monitor distance, which requires premium subscription. It should say so in a red text.

The calculator is calculating the DPI for you, it's in the output.

0.7 ms less latency makes absolutely no difference.

Try this: https://www.mouse-sensitivity.com/?share=b56d104cf211854c1a1db2ade714c96b

3200 dpi is not “less laggy” than 1600 in any case. In fact in cheaper sensors / firmwares, going above 1600 DPI often incurs smoothing (which create motion delay, albeit very slight). if you want the speed of 1600 dpi on your desktop, just use 1600 dpi

You can do like this, and just adjust the WPS until the calculated DPI is 3200: https://www.mouse-sensitivity.com/?share=c04fc1a15389c33438169a9328a69ad8

Oh what a mess this was, I've gone through an analyzed every single scope now and added them. Also added the 8x scopes which can be configured in the config file only