Ghost mouse cursor on secondary

from Stardock Forums

I did not notice this issue until upgrading to Pro build 00090 from the evaluation version, but it may have been there.

When using a secondary KVM machine when it is NOT under the control of another machine, a second mouse cursor is present under the local mouse cursor.  When moving the mouse cursor, the ghost cursor follows it, but with a time-lag of about one second.  This is extremely distracting. expecially when trying to move the mouse cursor accurately over small distances, when two cursors are visible most of the time.

To avoid this, I either have to go and turn on a primary machine and connect to the secondary from it, or stop the Multiplicity service (and disable its auto-restart) on the secondary machine.  Either action defeats the entire purpose of using Multiplicity.

Please suggest a better workaround, or fix this!  I remember seeing a setting relating to 'virtual mouse cursor' in the evaluation version (and it is in the on-line documentation) but it can no longer find it in the Pro version.

Both machines are using Windows 10 x64 1909.

multiplicity
4,791 views 3 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your questions/problems to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate you feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

It sounds like you have indeed turned on the emulated cursor which is used when your computer does not have a physically attached mouse as some versions of Windows will not show a cursor in such situations.

The setting is on the main page of Multiplicity on the secondary computer.  There should be three checkboxes.  The bottom one is "Enable fake pointer support if there is no mouse attached on Windows 8/10"  Untick this.

ObjectDock - Access shortcuts and frequently used applications from an animated dock.
Reply #3 from Stardock Forums Top

Thanks, that was it.  I believe I may have set this at the start of my eval period when looking for a way to revive monitors which had gone dark because of a timeout in power settings.  Unlike moving or clicking the local mouse, similar actions on the Primary do not make the screen contents appear.