Disappearing Mouse Cursor

DUPLICATE FROM THE GENERAL SECTION.   Apologies for the dup, should have been here.

I've started having issues with the mouse cursor disappearing again.  When I hit "Control" key the circle indicator shows up on the primary computer, but no cursor.  I have to restart the computer.  Using version 3.44 Pro build 00090 on 4 computers - all running windows 10 version 1909 build ending in 959.  I've set all mouse settings the same on each computer.  Trails feature is turned off.  It started before the update to windows 1900 build 959, so it's not the most recent update.  Any chance it's related to the 1909 build itself?  I'm losing a couple of hours a day restarting and recovering lost work.  Need a fix please.  T I A, Cliff

4,867 views 9 replies
Reply #1 Top

Hello,

I'll delete the other post .

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

 

AzDude
Stardock Community Assistant

Reply #2 Top

Hello,

Sorry to hear you are having trouble.

Please see
https://forums.stardock.com/500675/page/1/#3782926

Install on all MP PCs and let us know if you still see the issue.

Sean Drohan
Stardock Support Manager

Reply #3 Top

Greetings.
I still, have the issue with the beta linked above. 

Current issues I'm having are 
Cannot force PC to sleep without losing cursor.
Cannot keep PC sleeping.
Cannot WoL as long as Virtual Box is installed

Reply #4 Top

Quoting nubbyninja, reply 3

Greetings.
I still, have the issue with the beta linked above. 

Current issues I'm having are 
Cannot force PC to sleep without losing cursor.
Cannot keep PC sleeping.
Cannot WoL as long as Virtual Box is installed
End of nubbyninja's quote

The loss of cursor would be a huge surprise as how it handles cursors changed.

Did you uninstall and then reboot and then install the new build?

With regards to WakeOnLan,  unfortunately the Virtual Box network adapter has incorrectly set itself to top priority which is preventing the WakeOnLan packet going to the machine you wish it to.  The only way to work around it from an application point of view is to send the packet manually to every single network interface and this isn't something Multiplicity is currently designed to do.

Should a computer you are using (Secondary) go to sleep, control would be returned no more than 6 seconds later to the primary.  This is automatic as the machine thats sleeping will no longer respond to network messages used to check the other end is live.

Also I assume you are not using anything like CursorFX?

Reply #5 Top

I am using CursorFX on the secondary.

Reply #6 Top

It's odd that I'm having so many issues currently. I'm getting odd input delay on the secondary now... 
For a while I was using my primary as a workstation and secondary as a gaming PC and had virtually no lag on the secondary. 

Then as soon as I go through the trouble of configuring everything so I can use WoL (which is still bugged) now I'm getting sluggish input delay issues, cursor lockout issues when forcing the secondary to sleep, etc. It's becoming more and more apparent that I'm going to have to find another solution. I've already lost 2 days of work trying to get this configuration working.

Reply #7 Top

Quoting nubbyninja, reply 6

It's odd that I'm having so many issues currently. I'm getting odd input delay on the secondary now... 
For a while I was using my primary as a workstation and secondary as a gaming PC and had virtually no lag on the secondary. 

Then as soon as I go through the trouble of configuring everything so I can use WoL (which is still bugged) now I'm getting sluggish input delay issues, cursor lockout issues when forcing the secondary to sleep, etc. It's becoming more and more apparent that I'm going to have to find another solution. I've already lost 2 days of work trying to get this configuration working.
End of nubbyninja's quote

Are you using wired or wireless?

And do you have a third party firewall?

There should be no input lag that could be noticeable with a wired connection.  Wireless ones are obviously subject to interference so packet loss on those could be an issue.

Some firewalls or apps which claim to improve LAN throughput could upset things however as they cause packets to be combined for maximum efficiency which means delaying things.  They should not be used.

Reply #8 Top

No third party firewall. 
Hard wired.

I turned off the virtual pointer feature and it's better, but not great. 

Reply #9 Top

I'm pleased to report most of my issues are resolved AFAIK as of right now. @cwarr I can tell you right now, the cursor bug is seemingly impossible to solve, and the best possible solution I've found is to put the reset script found on this thread (thanks sdRohan) in an easy to access place. Typically my keyboard is still accessible, so I recommend using a hotkey tool of some kind to launch the script when the cursor gets stuck.

This seems to be the only thing that gets me unstuck at the moment, other than straight up rebooting, logging out of Windows and back in, or being able to manually restart the service on the Primary. SOMETIMES the secondary bugs out and I have to restart the service there, but more often than not the primary machine gets reset and problems go away, at least for a while.

Thanks again for the help gang. Best of luck.