![how to match sensitivity getting over it game how to match sensitivity getting over it game](https://ds055uzetaobb.cloudfront.net/brioche/uploads/ilCFQwThsn-group1.png)
- #How to match sensitivity getting over it game how to
- #How to match sensitivity getting over it game windows
360° distance is same (red line) but real sensitivity (green line) differs a lot.
![how to match sensitivity getting over it game how to match sensitivity getting over it game](https://i.ytimg.com/vi/cCL6tWv_7FM/maxresdefault.jpg)
#How to match sensitivity getting over it game windows
It's means if we move the mouse on the mousepad by 1 inch, the cursor/croshair on the screen will move about this physical distance in Windows or Game.
#How to match sensitivity getting over it game how to
The quickest way how to understand my utility, is to understand the "real sensitivity". Try it hard to explain I think very complicated. If you do the opposite and set windows to game 0%, then your manoeuvrability increases, your tracking stays the same as the windows cursor, but the sens is higher overall across the screen compared to the 100% mdh windows to game conversion. There isn't a healthy human alive who is not more precise on lower sensitivity than higher once they get used to the feel, because human motor skills, muscles / nerves / brains all fundamentally process the same type of signals in the same way. It's not magic from the formula, it's just increased accuracy from a lower sensitivity. The reason it feels so accurate at 100% mdh, is just because your tracking at the screen centre is actually now much slower than what the cursor speed is in windows per pixel - you are used to pointing at icons on your desktop, and then go in a game and get an increased accuracy bonus from the slower cross hair sensitivity per pixel. If you use fast in windows slow in game (e.g windows to game 100% mdh, so basically "zero" FOV to high FOV) then your sens overall is lower in the game so you will feel more accurate at the expense of manoeuvrability (Remember 0% feels slower and slower the more you zoom in with scopes, so when you do the opposite and convert from windows zero FOV to a high hipfire FOV in game, it also does the opposite and feels faster and faster the higher you set the hipfire FOV. All that's happening here is you are changing the reference point of your "fast to slow".