|
|
|
|
|
by ascom
2243 days ago
|
|
FPS games typically use raw input, which bypasses any acceleration settings in the OS. This works on both Windows and macOS, assuming the game is properly written. This is why I insist on keeping mouse acceleration enabled since it helps with everyday computing tasks and has no effect on at least the games I normally play. Regarding the comment above, it is definitely possible there are subtle configuration differences that cause the described behavior (different acceleration curves, polling rate/DPI settings, display refresh rates, etc). FWIW, my “gaming” mouse works fine with my MBP, but it takes a moment to readjust to the different sensitivity and acceleration behavior. |
|
Even if you use the command line to actually disable it for some reason the mouse still feels off.
If you google, for example "counterstrike mac os raw input" or something similar, you'll see lots of posts about people having the same issue. The raw input setting doesn't work properly. Granted the posts are from a couple years ago. The last time I tried to play a game on a Mac was probably around 2018. I tried every workaround I could find on the internet and it was still terrible.
What I described has nothing to do with a difference of sensitivity or polling rate/dpi. Although if a person is unfamiliar with those things they could have an issue with them.