Mouse cursor size bug

Every time I use Multiplicity to switch PC, my cursor on the master PC become big and low res. With time, it seem to become lower and lower util i can see individual pixel.

The slave have 2 4k screen and the master have one 2560 x 1800 and one 4k.

The cursor only change on the 2560 x 1800. 

All 4k monitor are set to zoom 150%.

If I go in the setting and i change the cursor size, it fix the problem util I use Multiplicity to switch PC again.

I really like the software as its more responsive than others that i used in the past but this bug is very annoying.

I understand that i have a non conventional setup but i hope we can fix this :).

45,921 views 35 replies
Reply #1 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 your feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #2 Top

All 4k monitor are set to zoom 150%.
End of quote

Zoom? Do you mean DPI or..?

Are you using any mouse / cursor software (Logitech would be one example).

Sean Drohan
Stardock Support Manager

Reply #3 Top

Yes I mean the scale and layout option int the display setting of windows.

Yes i have the Logitech Option software installed but I deactivated the Flow option.

I just tried to stop every Logitech process and it is still happening.

Reply #4 Top

I have the issue, too.  One monitor is 1080 and the other is 1440.  Both have scaling at 100% and mouse pointer size 3 and yellow.  The primary window's mouse pointer goes back to being tiny until I hover over something and it turns into the alternate cursors as the intended big size.

Reply #5 Top

Quoting allensantos, reply 4

I have the issue, too.  One monitor is 1080 and the other is 1440.  Both have scaling at 100% and mouse pointer size 3 and yellow.  The primary window's mouse pointer goes back to being tiny until I hover over something and it turns into the alternate cursors as the intended big size.
End of allensantos's quote

Hello,
Sorry to hear you are having issues. Need to know few items.

1) Windows version. Please use Winver.exe for full Windows version numbers.

2) CursorFX version.

Thanks

Basj,
Stardock Community Assistant.

Reply #6 Top

I Have a similar mouse pointer bug. I have a PC with 2 4k screens as Multiplicity master and a laptop with an external screen (4K) and it's internal screen (1K) as slave. The mouse pointer size is set to 2 on both systems, but as soon as I move the mouse to the laptop, the mouse size on the primary reduces to 1. When I check the pointer size settings it looks to be 2, but I have to change it to another size before it increases it's size again.

I must say, I have the 3 4K screens since 2 weeks. Before that I had 3 screens (1920x1200) but didn't use increased ponter size, so I don't know if this feature allready excisted!

Both systems run Win10 version 1909, build 18363.778

Mouse and keyboard are wired (USB), thus the original Windows software drivers 10.0.18362

I can reset the primary PC, and pointer size comes enlarged back on again. But as soon as I move the pointer to the laptop, the pointer size falls back to size 1. Strange enough, the size of the text editing pointer on this webpage remains enlarged, but the size of the arrow (the moving pointer) is reduced to size 1. Apparently there is a difference in pointer size between the arrow and the text editing (capital I in Book Antiqua font)) pointer function?

Reply #7 Top

Hello Adrian2,

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 your feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #8 Top

Quoting basj, reply 5

1) Windows version. Please use Winver.exe for full Windows version numbers.

2) CursorFX version.
End of basj's quote


Hi Basj,

Primary:      1080 / Win 10 18363.815 /  2-computer version 3.44 Build 00090 
Secondary: 1440 / Win 10 18363.778 / 
2-computer version 3.44 Build 00090 

Reply #9 Top

Quoting allensantos, reply 8

Hi Basj,

Primary: 1080 / Win 10 18363.815 / 2-computer version 3.44 Build 00090
Secondary: 1440 / Win 10 18363.778 / 2-computer version 3.44 Build 00090

End of allensantos's quote

CursorFX version?

Thank you,

Basj
Stardock Community Assistant.

Reply #10 Top

Quoting basj, reply 9

CursorFX version?


End of basj's quote


None... just using windows built in stuff.  Today the secondary monitor is the one w/ a tiny white pointer.

Reply #11 Top

Hello,

Sorry to hear you are having trouble.

This seems to be something that was introduced with the Windows 10 May 2019 update that no one had seen \ reported yet.

Well, I am seeing it on the Primary with these steps to repro:

  • Ease of access - Cursor & Pointer
  • Change pointer size
  • Transition to MP Secondary, back to Primary
  • The cursor will be small but other cursor states - resize for example - will show the changed size

Thanks for the report - I bugged it internally.

Internal ref: ODNT-566

Sean Drohan
Stardock Support Manager

+1 Loading…
Reply #12 Top

Dear Sean,

 

I don't know if this is related to above anomoly, but today I experienced another strange feature.

Even while typing this reply on the Multiplicity Master PC, my mouse pointer on the salve PC is reacting. 

When I hit the delete key te take away a few letters, it results in deleting email messages in outlook, because apparently my mouse was there prior to moving back to the master PC.

This anomoly is must serious because it effects my work!

This didn't happen just once, but several times since a few days.

 

Reply #13 Top

Quoting adrian2, reply 12

When I hit the delete key te take away a few letters, it results in deleting email messages in outlook,
End of adrian2's quote

Disable this please:

Sean Drohan
Stardock Support Manager

Reply #14 Top

I'm having the same issue with my mouse cursor.  My main screen is 4k so on that computer I have the cursor set to 3 pts.  When I go to the secondary computer and back again, the pointer reverts back to the default size.  The text cursor remains the correctly set size.

 

I'm doing the same as post 11 and having this issue.

Reply #15 Top

I have this issue as well, and it seems it has started within the last 2-03 weeks and may be associated with one W10 update. 

Reply #16 Top

Windows version 2004, OS build 19041.264 on the primary

Windows version 1909, build 18363.836 on the secondary

Multiplicity 3.44 KVM Build 00090

Reply #17 Top

Additional info on this...

I decided to re-install windows (I was on 2004 May 2020) thinking that with re-installing from the cloud, my PC would revert to 1909, the same as the secondary PC.  BUT, no it did not, Windows 2004 was re-installed, and after getting Multiplicity reinstalled, the cursor size on the Primary would be changed when the cursor moved from the secondary to the primary.

So, now I am in the process of forcing the 2004 May update on the secondary PC.  I hope this may solve the Multiplicity issue! 

Reply #18 Top

With the secondary PC now updated to 2004 May update, same winver as the primary PC, the cursor issue is continuing.  Hence this leads me to believe that Multiplicity version 3.44 can't tolerate 2024.  It would be nice to hear from Support

Reply #19 Top

Quoting billmcl, reply 18

With the secondary PC now updated to 2004 May update, same winver as the primary PC, the cursor issue is continuing.  Hence this leads me to believe that Multiplicity version 3.44 can't tolerate 2024.  It would be nice to hear from Support
End of billmcl's quote

Is your primary computer a multi monitor setup and if so are the two monitors set to the same scaling factor?

Also are you using the OS feature to increase the size of your mouse cursor?

Reply #20 Top

Is your primary computer a multi monitor setup and if so are the two monitors set to the same scaling factor? Yes, the 2nd monitor is extended.  Same scaling on both monitors. This cursor issue never happened before I made the mistake to enter into the pre-release slow ring on the primary.

Also are you using the OS feature to increase the size of your mouse cursor? Yes, but I did before the 2004 release slow ring and never had this issue.  I have been using Multiplicity for years with no problems.

The cursor does not exhibit this issue of moving within the 2 monitors of the primary.  It starts immediately when it cursor moves to one of the secondary computers

Reply #21 Top

Also are you using the OS feature to increase the size of your mouse cursor? I just changed the cursor on both the primary and the secondary to 1 point, no color. NOW, there is no cursor size change when the it moves from one PC to the other.  This really confuses me, but for now, it appears this issue is solved.  Thanks for all of the suggestions.

Reply #22 Top

Since both the primary and secondary are using the default normal cursor, everything is finally working fine. However, I would be interested in why it is not possible in using the OS feature to increase the size the cursor when using multiplicity, especially when using the same configuration on both the primary and secondary?  I don't recall this being a problem prior to  the  Windows 10, version 2004 --  unless I am mistaken about this.

Reply #23 Top

I'd still like a resolution.  I'd rather see big and colored cursors.  The color usually helps me determine if I'm remoted into a work computer.  The size for usability and ease of finding it.

Reply #24 Top

Quoting allensantos, reply 23

I'd still like a resolution.  I'd rather see big and colored cursors.  The color usually helps me determine if I'm remoted into a work computer.  The size for usability and ease of finding it.
End of allensantos's quote

As indicated prior, it is being looked at.

Thank you.

Sean Drohan
Stardock Support Manager

Reply #25 Top

Just chiming in with a 'me too'.  I have 2 PCs, a main and a secondary. The secondary got updated to 2004 first, and for a week there was no issue. It was after my main PC updated 2004 that the issue started.  The pointer size was set to 3 on both PCs, but I've since set it back to 1 which resolves the issue for the time being.