Possible fix for Parallels mouse sensitivity issues
After wrestling with Parallels mouse sensitivity issues for years, I think I've finally figured out what the main problem is.
When it comes to games and other applications that are affected by changes in mouse sensitivity,
Parallels seems to assume that nobody ever adjusts the tracking speed of their mouse under OS X. In other words, these types of applications only run properly in Parallels when the Mac OS X factory default values for mouse tracking speed are applied. Apple doesn't provide a "Reset to defaults" button in System preferences (nor should they need to), so anyone who's ever adjusted the mouse tracking speed on their Mac will have this issue.
Here's how I finally solved my mouse issues under Parallels 8 on Mac OS X 10.9.2 (Mavericks), running a Windows XP VM.
I have no idea if this will work the same way in Windows 7 or 8, but it does in XP:
1.
Restore Mac OS X tracking/sensitivity settings to factory default value(s). I found a great free preference pane to manage this called
CursorSense, which has an actual "Restore System Defaults" button. While it's unfortunate that Parallels isn't smart enough to make all this unnecessary, it's relatively easy to restore your previous preference values after you're done using it.
2. In Parallels Desktop, turn
SmartMouse off. The option to
Optimize modifier keys for games should be
checked (on).
3. In Windows XP, set mouse sensitivity one click above slowest setting. Be sure
Enhance pointer precision is turned
on.
These exact settings, while a bit annoying, work great for me and I can now play games that were previously unusable after the update mentioned above. I can't say for sure that it will, but I hope this information helps you resolve your own mouse issues if you're having them.
I decided to figure this out after getting fed up with Parallels bombarding me with ads to upgrade to the latest version. Their update broke a feature that worked properly before, and I seriously doubt that Parallels Desktop 9 has fixed the problem. I had steam coming out of my ears over this for several months, and am pretty glad to have figured out a solution.
To the Parallels team: seriously, how hard would it be to resolve this once and for all? This has been an ongoing issue with Parallels Desktop for
years, and it affects a significant portion of your customer base. Your inaction on this makes hundreds of Windows applications unusable with your product, yet you don't seem to care enough to do anything about it. It shouldn't be impossibly difficult to compensate for or ignore custom Mac OS X mouse acceleration values, if that's all there is to it. I certainly won't be upgrading to a new version of Parallels before I'm 100% certain you've fixed this.