> This is one of the reasons I ended up using Linux
This is one of the reasons I ended up ditching Linux for Windows+WSL.
Disabling mouse cursor acceleration under X11, for example, depends on which of at least three different X.org mouse drivers you are using (really old, evdev, or libinput). And web searches often turn up an unreliable or incorrect method. (Search this article's comments for "xinput" to find more info I just typed up for another reply.)
And if you use a Logitech unifying receiver you need to research that the program you need is 'solaar' to pair/unpair your mouse under Linux.
And if your bluetooth mouse or keyboard goes to sleep too fast under Linux (5 seconds in my case) you might need to add this to your grub boot params (worked for me):
$ sudo vi /etc/default/grub
# Add btusb.enable_autosuspend=n to GRUB_CMDLINE_LINUX_DEFAULT
The point is, researching all this hardware config stuff is time I could have been using to research more interesting computer science problems. I sure can get my printer working much faster under Windows than Linux....
+1, I've also been using the paid Mac app Smooze (smooze.co) to get smooth mousewheel scrolling animation like I get on Linux and Windows out-of-the-box when web browsing and so forth because I haven't found a free app that can do this.
And while we're talking about the effort needed to get sane mouse behavior for serious CAD/3D editing/art/gaming, it is way too hard to reliably disable cursor acceleration on Linux. There are at least three different X11 mouse drivers on Ubuntu: the really old one, the evdev one, and the newest libinput one. (I don't even know what you have to do for Wayland... never got there....) So if you web search "disable mouse accel linux" you likely get the wrong directions (at least I did) because you might be using the libinput driver and the instructions you found are for evdev. One unreliable method I tried involves setting a matrix. This at first works and then you eventually discover some apps like Blender develop cursor jump bugs....
So the reliable method is....
If using libinput mouse driver you do something like this:
To figure out your mouse name string like the MM710 example I used above you do this:
$ xinput --list
The number of tweaks I've needed to research and implement for both Mac and Linux are one reason I'm now currently using Windows + WSL for getting stuff done. I want to solve computer science problems more interesting than configuring my mouse and my window manager vsync tearing / compositor issues....
This is one of the reasons I ended up ditching Linux for Windows+WSL.
Disabling mouse cursor acceleration under X11, for example, depends on which of at least three different X.org mouse drivers you are using (really old, evdev, or libinput). And web searches often turn up an unreliable or incorrect method. (Search this article's comments for "xinput" to find more info I just typed up for another reply.)
And if you use a Logitech unifying receiver you need to research that the program you need is 'solaar' to pair/unpair your mouse under Linux.
And if your bluetooth mouse or keyboard goes to sleep too fast under Linux (5 seconds in my case) you might need to add this to your grub boot params (worked for me):
$ sudo vi /etc/default/grub
# Add btusb.enable_autosuspend=n to GRUB_CMDLINE_LINUX_DEFAULT
GRUB_CMDLINE_LINUX_DEFAULT="btusb.enable_autosuspend=n"
Then:
$ sudo update-grub
The point is, researching all this hardware config stuff is time I could have been using to research more interesting computer science problems. I sure can get my printer working much faster under Windows than Linux....