[quote who="Mikaller" reply="8" id="3784142"] I have this same exact issue, did you ever find a resolution? [/quote] My solution was reformatting the host and the problem client. I spent hours trying things and no luck. Good luck sir!
Alignment Switching on small monitor gaps didn't work. Such a strange issue. For science I loaded up a vastly inferior similar application and I get the same behavior. So it is not Multiplicity issue it in OS configuration. I started experimenting with refresh rate on the monitor. 2k 144Hz rigs and the troubled machine GPU just can only 100Hz but that also didn't work. Time to brain storm on what else could be causing this.. or maybe just a reformat in
It does transition eventually but it is not a seamless smooth transfer like normal. I have to pick up the mouse multiple times and keep dragging that direction before the cursor starts to move on the troubled machine. Its the same behavior moving back to the main rig from the trouble machine as well. both monitors are 2k but ill dabble with alignment.
Hello thank you for the quick reply. I had already went through the FAQ searching for a resolution to my issue. No luck. Hopefully I did a good job explain the behavior I am observing with my Multiplicity. It is just one of the computers in my 6 computer setup that is misbehaving. I recently did reformat the machine and installed a fresh Win10. And it was working for the last month as intended, the other day I noticed the delay before the mouse actually
I have 6 computer in my setup that I use Multiplicity to control with single keyboard and mouse. The other day for reasons unknown 1 of 6 computers has this 'dead space' or 'buffer' in between the two monitors when I move the mouse from host computer to the client. All of my 5 other computer transfer the mouse seamlessly as it has for years. I have to pick up the mouse to move the mouse all the way to the troubled computer. I have looked through host and client setti
Stardock Forums