I've been playing sc2 for about 3 months now. I used to play quake and only quake, and I played it a lot. In quake, finding the right mouse sensitivity is crucial. Oddly, among the very best players there were some who were very particular about their mouse and it's configuration, but some of the greatest didn't care about that stuff at all. I think that while there is a lot that can be done to tweak and personalize the way a mouse responds, it's more important to use what feels good to you.

Generally the idea was to make everything consistant. That's why most players would disable all mouse acceleration in and out of game, so the pointer speed is constant. I would also do something I don't think got mentioned by the OP. The USB polling rate can be changed from default (125hz) to 250, 500, or 1000, with a bit of tweaking. Many players (and some mice manufacturers eventually as well) wanted 1000hz. I'm not sure why honestly. Maybe they just felt faster was always better, but again, it's about consistancy. The USB rate does not stay at 1000hz, it is just capped there. The rate will fluctuate up and down with respect to USB device usage. So, I would set mine to 250hz. There are utilities to monitor the USB hz rate, and with one it is clearly seen that 250hz stays steady and constant, while the higher values would fluctuate. I felt that the difference between the two was very noticeable.

There was more stuff too but I can't recall right now..

Deleted User 135096

3624 Posts

May 23 2012 23:57 GMT

#23

On May 24 2012 07:57 elenkus wrote:+ Show Spoiler +

I've been playing sc2 for about 3 months now. I used to play quake and only quake, and I played it a lot. In quake, finding the right mouse sensitivity is crucial. Oddly, among the very best players there were some who were very particular about their mouse and it's configuration, but some of the greatest didn't care about that stuff at all. I think that while there is a lot that can be done to tweak and personalize the way a mouse responds, it's more important to use what feels good to you.

Generally the idea was to make everything consistent. That's why most players would disable all mouse acceleration in and out of game, so the pointer speed is constant. I would also do something I don't think got mentioned by the OP. The USB polling rate can be changed from default (125hz) to 250, 500, or 1000, with a bit of tweaking. Many players (and some mice manufacturers eventually as well) wanted 1000hz. I'm not sure why honestly. Maybe they just felt faster was always better, but again, it's about consistancy. The USB rate does not stay at 1000hz, it is just capped there. The rate will fluctuate up and down with respect to USB device usage. So, I would set mine to 250hz. There are utilities to monitor the USB hz rate, and with one it is clearly seen that 250hz stays steady and constant, while the higher values would fluctuate. I felt that the difference between the two was very noticeable.

There was more stuff too but I can't recall right now..

Those resources are definitely there, I just didn't go into too much detail about them as there are other external sources (which are linked) that are dedicated to properly changing your polling rate or the like. This is meant more as a primer of sorts to your overall understanding, but it does mean that you (you as in the general populous) should be reading up on every linked thread or resource to get a more comprehensive understanding of these topics. For instance I don't really get too much into how you can change the inflection points of the windows acceleration curve because hoppan already has an excellent write-up on the matter.

lollyz

218 Posts

June 19 2012 20:44 GMT

#24

Artisan mousepad #1

chongu

Malaysia2593 Posts

June 20 2012 14:37 GMT

#25

<3 Now I know so much more about mice than I ever did. Professional and concise. Good work OP!

Care to share what mouse you perdsonally own/love?

Deleted User 135096

3624 Posts

June 21 2012 19:20 GMT

#26

I currently own a Roccat Pyra, Logitech Performance MX, Tt eSports Azurues mini, and KTEC 9500+. I am currently using the 9500+ because the shape and size is the most comfortable out of all of them for me, though its low MR makes it impossible for me to use in FPS games. Tracking isn't perfect either, but I'm mostly stalling right now until I can get a better mouse (limited funds). On that, I will almost %100 get bst's mouse when it is released (baring any major issues) as it has pretty much everything I need in a mouse.

ACrow

Germany6583 Posts

June 21 2012 19:55 GMT

#27

Holy shit, that's a nice article, very good work!

TwilightRain

Germany351 Posts

July 09 2012 17:02 GMT

#28

one additional question: Does interpolated dpi mean that this resolution setting is not native and is achieved by pixel skipping/ignoring?

P.S. any insider knowledge on when bst's mouse is gonna come out?

Deleted User 135096

3624 Posts

July 09 2012 18:45 GMT

#29

On July 10 2012 02:02 TwilightRain wrote:
one additional question: Does interpolated dpi mean that this resolution setting is not native and is achieved by pixel skipping/ignoring?

P.S. any insider knowledge on when bst's mouse is gonna come out?

Pixel skipping is a different thing entirely. Interpolated steps are just CPI steps that aren't natively programmed into the registry of the SROM. This either means that there is some additional calculation going on to achieve these settings, or some kind of halving or discarding of data to achieve them (depends on the manufacturer).

For example, without touching the SROM for a stock A3090 you could achieve a 450 and 900 CPI steps by either quartering or halving the 1800 CPI step through various calculations (could be MCU level, could be driver). You could also program a 600 or 1000 CPI step as well, but in these cases those resolutions would not be native to the sensor (stock native is 1800 and 3500 only). Of course the manufacturer could also build a custom SROM for the 3090 that included these steps natively, but that requires slightly more work on their part (and is more expensive).

It is also important to know that sensors can have more than on SROM. The A9500 afaik has at least a few firmware versions on the market that I know of, so they all have slightly different registries.

Deleted User 135096

3624 Posts

July 26 2012 12:26 GMT

#30

I finally decided what to do with that reserved section. As new items pop up I will be adding them to the addendum that is now part of that section. As an example Glymbol over on OCN just sleuthed out that Windows has many more sensitivity settings that just 11 (20 in total) and that we can access them from a python script that he wrote. See the Addendum for more information.

TwilightRain

Germany351 Posts

August 06 2012 07:36 GMT

#31

Is there such a thing as native dpi for laser sensors or do they track equally good or bad regardless of which dpi setting you select manually?

Deleted User 135096

3624 Posts

August 06 2012 13:29 GMT

#32

On August 06 2012 16:36 TwilightRain wrote:
Is there such a thing as native dpi for laser sensors or do they track equally good or bad regardless of which dpi setting you select manually?

Yes, but there is a caveat. In CMOS laser sensors such as the A9500 by Avago, the native steps are in increments of 90, so 90, 180, 270, etc... are all native settings. This means that 496 CPI if achievable in the driver, is not native and some additional calculation is occurring to get that resolution (possibly calculated from nearest native step above, but idk). All of this is highly dependent on the firmware though.

Example, the new Taipan uses the S9818 (modified A9800) where the native steps are in increments of 100. The original specs from the datasheet indicate the native steps being in ~200, but Razer has enough pull from what I understand to have been able to get a custom sensor package (also optical S3668, and S3888). Also, PTE sensors if I'm reading this correctly function very similarly to the way native steps in Avago sensors work, though what the increments are, and what the CPI resolutions available are are highly manufacturer, mouse, or firmware specific (see the mouse sensor technology guide on ocn).