When I turn off secondary computer I can't use the primary.

Hello,

- I use seemless mode
- My two computers physically share one of the monitors (One with VGA and the other with HDMI, switching between them by changing inputs using the menu buttons on the monitor.)
- I don't want the mouse to move between the two computers except when I'm ready to switch.
- So I use the hotkeys and I've also tried the prevent it from switching unless shift is held and I've tried the scroll lock method to prevent accidental switching.
- When I shut down my secondary PC, the process requires the use of the mouse and keyboard on the secondary pc... but once the computer is off... the mouse and keyboard don't automatically revert back to the primary PC... so it's stuck in limbo with no way to control it... and no way to change the Multiplicity settings... I have no input methods (mouse and keyboard) to input commands to the Multiplicity software to move the control back to the computer they are plugged into.

- This isn't an oversite is it? Surely if Multiplicity loses connection to the secondary PC, it's supposed to revert the control back to the primary by design and I'm doing something wrong... right?

Help me out... thanks!

Eric

5,027 views 5 replies
Reply #1 Top

Hello,
I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 Top

Hello,

Sorry to hear you are having trouble.

Try installing the beta on each box:
https://forums.stardock.com/500675/page/1/#3782926

Sean Drohan
Stardock Support Manager

Reply #3 Top

You are correct that in the event of loss of connection control is returned to the primary.  This is automatic after 6 seconds.

Reply #4 Top

I'm having the same issue. Control doesn't revert to the primary when the secondary computer is turned off in seamless mode. I need to CTRL-ALT-DEL the primary and reboot to get control back. Windows 10 19042 build 630, it also has happened on prior builds. If I manually pull the mouse back to the primary as the secondary statrs to shutdown I can sometimes get it to work.

 

Help is appreciated.