Leaderboard

What is sensitivity? A common misunderstanding is that mouse sensitivity adjusts the speed of the input from the mouse, or the speed of your crosshair/character movement. While increased or decreased movement speed is the primarily perceived effect, what it really does is modifying how far each count from the mouse moves your crosshair. When you are adjusting the sensitivity, you are actually defining a grid to which your movement snaps. The lower the sensitivity, the finer the grid. This is sensitivity The animations on the left show the actual in-game movement for a 1 degree turn in Battlefield 3 with a resolution of 1920x1080 and a FOV of 90. 1 degree with these settings equals 12 pixels. The image on the right display the actual pixels and crosshair movement from the animation, and the black dots represent the grid as defined by the sensitivity. As you can clearly see, lower sensitivity gives you a finer grid, which again gives you more accurate aim and smoother movement. Even at a 1:1 ratio between the grid and pixels, the movement is quite choppy. Sensitivity: 0.627370 | Counts/degree: 3 | Pixels/count: 4 Sensitivity: 0.311185 | Counts/degree: 6 | Pixels/count: 2 Sensitivity: 0.153093 | Counts/degree: 12 | Pixels/count : 1 Sensitivity: 0.074046 | Counts/degree: 24 | Pixels/count: 0.5 Sensitivity: 0.034523 | Counts/degree: 48 | Pixels/count: 0.25

Might I just add that that bug has been around for a while. I have experienced it occasionally when using the old viewspeed for the past 2 months or so. Maybe only 5-6 times, but I KNOW when my chord length is almost 2 inches off when I've been doing calculations for a few hours. Same bug occurs with the current viewspeed, even after you took the new version off of the live calculator. I've had it happen ~2 times in the past few days. If it is useful information, I have only noticed it happening when I use windows snap assist to put my calculator on the left side of my monitor while I edit the config file on the right side of my monitor. I've never seen it happen while chrome is maximized. I've found that refreshing or just opening a new tab with mouse-sensitivity.com fixes it though. Regardless of any bugs however, I LOVE the new viewspeed, and I have been using it for every game now. I have always felt that my snaps from game to game have not been quite 100% since I started using viewspeed, but I was fine with it because I would otherwise only be able to seriously play one game at a time, and viewspeed made it so that it would feel very close, albeit not perfect, to a match. With the new viewspeed, however, all of my games feel identical, all of my snaps from target to target, regardless of game, feel identical. It is truly amazing. I was fine with compromising accuracy a bit before so that I could play more games than whatever title I was most invested in at the time, but now I can play my most competitive title (overwatch), and still be able to play whatever game a friend asks me to join him/her in without hurting my muscle memory whatsoever. This new version works perfectly (aside from the fov glitch which is easy to catch) for Overwatch at 70.53 fov converting to aimhero at 70fov and battlefield 4 at 90fov. They all feel identicle, and it is truly the most amazing change I have ever seen on this website. Thank you three (and anyone else involved) for all the hard work you've put into this!