For a about a month I have been tweaking Input Director in a standard Master (Desktop) with two Slaves (laptops on either side) setup. Everything was working perfectly with the exception of only a single issue. Every so often, mostly during gaming, one of the laptops would unexpectedly grab the cursor.
Originally I associated this with some sort of process on the laptop "grabbing focus". This ended up not being the case after all sorts of process monitoring and system analysis. It wasn't until recently that I realized to properly associate the issue with screen transitions because when the mouse would unexpectedly jump to the slave, it was always on the "transition point" or very edge of the screen. This was the case during many tests where the cursor was being visibly tested very carefully in the center of the master's screen.
Recently I upgraded to the latest version of Input Director and unfortunately there was no improvement. Played around with just about every single setting without any success until I started to alter "Transition at screen-edge" in Master Preferences. For some unknown reason, when this is set to "Immediately" I would experience the unexpected cursor-to-slave transition with a high degree of frequency, approximately once every 1 to 2 minutes. As of this evening I have been running with it configured to "On cursor lingering for 300 milliseconds" and have had zero cases of unexpected master-to-slave transitions. The only undesirable behavior left in the entire deal is the very rare occurrence where the cursor drifts from it's original location following a moment of very active input - but at least it is not transitioning now which is a big win.
Just to summarize, Input Director has worked flawlessly for me with the exception of this one issue. Now it is finally stable to the point I can confidently say the transition issue is resolved and the 300 ms delay is an acceptable workaround I can live with. The primary trigger to reproduce the issue was semi-rapid mouse movement with left or right mouse button held down while pressing other keys (typical gaming behavior). I realize not everyone may have this same use-case, but if you do and have been struggling against the very frustrating issue of slaves grabbing your cursor away from the master, try this change.
Notes:
- Master and slaves all running the latest version of Windows 10
- Input Director v1.4.1
- No mouse attached to either laptop, trackpad is also locked / disabled
- Master is a beefy desktop with 32 inch 4K monitor
- Slaves are both 17" gaming laptops, both running 1920 x 1080 resolutions
- Peripherals on master are all Logitech, tested both with and without the gaming software enabled.
Thanks,
~ G