My old ugly Logitech mouse since 10 years died. For long I have been thinking about replacing it not really knowing what to get instead.
I have a “das keyboard” and I want a mouse with the same build quality and feel, but without a million configurable buttons. I also have a KVM switch (using two computers with the same display, keyboard and mouse) from Aten.
I bought a Corsair Katar mouse.
Findings:
- When KVM-switching it takes a few seconds for the mouse to start working.
- The mouse is very fast at first. In Windows it slows down after a few seconds (I guess when drivers and mouse profile kick in).
- The mouse works just fine in Ubuntu, but it is too fast for my taste (even with basic mouse configuration options set at slowest).
Perhaps I would have been better off with a sub-$10-noname-mouse.
Update 2016-10-16
I found a way to slow down my mouse! This support post was useful, although my solution was slightly different.
First run:
$ xinput list ? Virtual core pointer id=2 [master pointer (3)] ? ? Virtual core XTEST pointer id=4 [slave pointer (2)] ? ? Corsair Corsair Gaming KATAR Mouse id=11 [slave pointer (2)] ? ? Corsair Corsair Gaming KATAR Mouse id=12 [slave pointer (2)] ? Virtual core keyboard id=3 [master keyboard (2)] ? Virtual core XTEST keyboard id=5 [slave keyboard (3)] ? Power Button id=6 [slave keyboard (3)] ? Video Bus id=7 [slave keyboard (3)] ? Power Button id=8 [slave keyboard (3)] ? Metadot - Das Keyboard Das Keyboard Model S id=9 [slave keyboard (3)] ? Metadot - Das Keyboard Das Keyboard Model S id=10 [slave keyboard (3)]
I found out that fixing device 11 was useless, but device 12 was helpful.
My mouse parameters are obtained:
$ xinput list-props 12 Device 'Corsair Corsair Gaming KATAR Mouse': Device Enabled (142): 1 Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 3.000000 Device Accel Profile (269): 0 Device Accel Constant Deceleration (270): 1.000000 Device Accel Adaptive Deceleration (271): 1.000000 Device Accel Velocity Scaling (272): 10.000000 Device Product ID (262): 6940, 6946 Device Node (263): "/dev/input/event6" Evdev Axis Inversion (273): 0, 0 Evdev Axes Swap (275): 0 Axis Labels (276): "Rel X" (152), "Rel Y" (153), "Rel Vert Wheel" (268) Button Labels (277): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151), "Button Side" (266), "Button Extra" (267), "Button Forward" (291), "Button Back" (292), "Button Task" (293), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265) Evdev Scrolling Distance (278): 1, 1, 1 Evdev Middle Button Emulation (279): 0 Evdev Middle Button Timeout (280): 50 Evdev Third Button Emulation (281): 0 Evdev Third Button Emulation Timeout (282): 1000 Evdev Third Button Emulation Button (283): 3 Evdev Third Button Emulation Threshold (284): 20 Evdev Wheel Emulation (285): 0 Evdev Wheel Emulation Axes (286): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (287): 10 Evdev Wheel Emulation Timeout (288): 200 Evdev Wheel Emulation Button (289): 4 Evdev Drag Lock Buttons (290): 0
Here, the “Coordinate Transformation Matrix” is the key to speeding the mouse down. The last parameter was 1.0, it is now 3.0, this seems to mean my mouse is just a third as fast as it used to be. To set it:
xinput --set-prop 12 "Coordinate Transformation Matrix" 1.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 3.0
I suppose your mouse can go quite crazy if you change all those 0.0 to something else. Good luck!