What was your acceleration setting in SmoothMouse? If it was “off”, just draw a straight line. ControllerMate is unique-there are no comparable applications in neither macOS or Windows worlds. While it may seem a little harder to use, the extra effort is well worth it, because it allows you to actually draw the acceleration curve and program mouse buttons however you want using visual programming (i.e. It’s a wonderful piece of software by very talented programmer Ken Heglund. It’s been around for over a decade and I think its very underrated.
If you’re looking for something to replace SmoothMouse I can highly recommend ControllerMate. Mouse acceleration in macOS sucks and it’s not only a matter of taste (maybe I’ll write another post on this). That said, if you’re a C++ programmer who worked with the inners of macOS (kernel) and have a desire to experiment, please click here. Quite possibly it will never happen because Apple nowadays is too busy with other things. SmoothMouse won’t support Sierra. We will unfreeze the project if we find a better API to move the mouse pointer. I’m sorry, but we’re putting the project on pause. be more like other mouse drivers). We won’t do the former and we don’t really see the point in the latter, so… It boils down to two options: “bite the bullet” (use Apple’s buggy API and hope for the best) - or - reengineer SmoothMouse from the ground up (i.e. And for this very reason SteerMouse still works in Sierra and SmoothMouse doesn’t. When I emailed SteerMouse developers back in 2010 (before SM began) about the pointer lag, they were like “what are you talking about? We’re not doing this!” Of course, they could not do what I wanted. SmoothMouse didn’t tweak the default driver of macOS like SteerMouse or USB Overdrive, it took its place instead. Under the hood, SmoothMouse is very different to all other 3rd party mouse drivers, because it was designed for a different purpose. Apple has fixed the 16ms lag in El Capitan (and Sierra). You don’t need SmoothMouse anymore if you use SmoothMouse only to fix the lag. It’s simply difficult to learn something when the outcome of your actions is delayed. On a slightly unrelated note, I strongly believe that many people didn’t realize the reason for their discomfort from using a mouse with macOS wasn’t the quirky acceleration algorithm per se, but the input lag which made the algorithm a lot harder to get used to. For many years it had been lagging for 16 milliseconds compared to Windows, and SmoothMouse was the only solution to this problem. Yes, the lag of 16ms may be noticeable by the human eye when combined with the display lag. The top priority was to improve the response time of the mouse pointer in macOS. SmoothMouse wasn’t created only to “fix acceleration”. It wasn’t our top priority back in the day. We filed a bug report in 2014 (#21909158), emailed various Apple employees including Craig Federighi, without any results. Of course, we knew about those problems, but we couldn’t fix them, because they were all caused by a serious bug within IOHID. “IOHID” (deprecated in Sierra) had a lot of problems too, but performance was not one of them. Quite possible you’ve seen SmoothMouse causing crazy things to happen in Steam games or while in Screen Zoom mode-when you pressed a mouse button. To our surprise, those weren’t only games, but also a plethora of professional applications like Ableton, Traktor, Cinema4D etc. The second worst problem was that it didn’t work well with the applications that needed to take control of the mouse pointer. CGEventPost would make SmoothMouse skip movements when your computer was doing graphically intensive calculations. The recommended API called “CGEventPost” (a part of Quartz) is full of problems. We know this from our experience, because we used CGEventPost in SmoothMouse in 2012–2013 before switching to IOHID. The worst problem was performance. In Sierra, Apple has deprecated “IOHID”, the API SmoothMouse uses to move the mouse pointer.
0 kommentar(er)
