Yes. Those options have absolutely no effect on mouse wheel movement. Optimizing for Gaming causes the mouse cursor to become stuck in the VM guest window.
No matter what it takes 8 "clicks" of the mouse wheel to produce 1 "click" worth of scrolling. This was not the case in the past. It began with VMware Fusion 11.
Does anyone know what to do about this? Scrolling in any VM guest is painfully slow and jerky. It used to work. Now with VMware Fusion 11 it is broken.
So? No answer on this?
Has anyone else experienced the issue that mouse wheel scrolling SUCKS in guest VMs? It takes 8 "steps" of the scroll wheel to make 1 "step" worth of scrolling; 7 "steps" are totally ignored by the guest and only every 8th step counts.
This is affecting ALL my virtual machine guests regardless of their operating system. That means it is NOT a configuration issue of a guest OS.
Mouse wheel scrolling works as expected in the Mac host (every "step" of the scroll wheel results in scrolling; no steps are ignored), so this is NOT an issue with my Mac or my mouse.
The only thing remaining is VMware, where mouse wheel scrolling used to work perfectly and started acting this way ever since an update in the not-too-distant past.
Does VMware care? I haven't seen any substantive reply to this thread.
I have the same issue. Very slow scrolling. 8 or so clicks on the mouse wheel equals 1 scroll movement on the screen.
Mac host version: 10.15.2
VMware Fusion version: 11.5.1
Mouse: Logitech MX Anywhere 2S connected via Bluetooth to Mac.
Guest VM: Ubuntu 19.10
I really hope this can get resolved soon. It is really frustrating to scroll.
I have the same issue. Windows 10 host, Ubuntu 19.10 gust. VMWare Workstation 15.5. It's gotten to where I will use the scroll bar instead whenever I'm browsing in the guest.
This problem exists so long, as I remember, some mouse drivers react better, but in general mouse wheel is buggy and skips or didn't catch all events ( of course vmware tools installed everytime ).
I have the same problem with workstation pro 15 on a centos 8 host inside of my Ubuntu 18 guest. It is incredibly annoying, but I’m willing to tolerate it for now because workstation pro is the only solution that I found with 3D hardware acceleration (but only after I spent hours figuring out that a secret “allow blacklisted driver” flag was required for my graphics card).
The only other thing that drives me nuts is that I can’t figure out how to make the guest fully capture the windows key (always goes to the host even in full guest input containment mode - forgot the name for this).
All mouse related usability quirks I noticed went away as soon as I changed the mouse settings to "always" use "game mode". The mouse pointer became as sensitive as on the host and scrolling in the guest works perfectly. I am on workstation pro 15 centos 8 host with ubuntu 18 guest.
My other problem - exclusive mode doesn't capture some keys - also seems to be related to centos 8 using wayland by default. Logging in using xorg instead fixed that problem.
Now vmware workstation pro 15 works perfectly for me and is way better in every respect I can think of (guest performance, virtualization usability) than KVM or virtualbox.
These issues all sound like problems with what's called "Smooth Scrolling" or "Pixel Scrolling" (depending on your OS), where the host's mouse sends very fine-grained scroll events, and either the host isn't sending this consistently, or something is going wrong in the conversion so that the guest isn't getting the same level of sensitivity applied.
You can probably work-around this by adjusting the following config options:
MacOS Hosts: mks.mouse.pixelScrollSensitivity (default value 8)
It sounds like most of the MacOS users here with issues should set:
(Although you can to adjust to different values as needed.)
Higher values mean that it requires more host scrolls to produce a single guest-scroll.
Depending on the precise problem, some combination of these options should help:
Adjust the mks.win32.scrollScaleFactor as needed to increase/decrease the scaling. Higher values means that a single host-scroll will turn into more guest-scrolls.
I'd probably start with just the mks.win32.scalePartialScroll=TRUE option, and if that doesn't work, also add the mks.win32.scaleScroll=TRUE option, and then adjust the mks.win32.scrollScaleFactor from there if it seems to help, but only partially.
I haven't seen any reports of this on Linux before, and I'm not aware of a config option that can help. To be honest, the Linux reports here sound more like mouse-movement problems rather than scroll-wheel problems, and might be due to Wayland/X11 interactions. (The fact that it went away with the "Gaming Mouse" setting ,and works in X11 mode also confirms that.) We'd have to investigate and get back to you, possibly with an option in a future version of Workstation.