Mouse input slow/lag on slaves?

[Bryan]

Okay, so I have input director installed on two laptops to test the mouse latencies.

I have my Gaming Desktop, 2015 Macbook pro, and a Lenovo t420.

Both of the laptops, and my desktop they are all running Windows 10. The Macbook is boot camping Windows.

For both of the laptops, I suffer extreme mouse lag and delays for both of them.

I don't have the computers connected to an ethernet cable because both the router and modem are in the bedroom.

With the Lenovo t420, I thought it would be a hardware issue and it just can't handle a lot of things but it's even laggy/slow with nothing running in the background.

After that, I tested it with my MacBook and it's doing the same thing- with nothing running in the background.

The mouse would kind of pause, stop moving, or even freeze so that on the master it would tell me that the slave's mouse has stopped responding.

Setting the priority to realtime for Input Director has done nothing also.

Would maybe the delays be caused by my wireless wifi connection?

I read problems where there would be people were having problems with wireless connections and the mouse input lag, but that was maybe a couple years back. I haven't found an update or a fix yet.

Do I just need a faster internet speed to handle the mouse switches between computers?

My connection speed is about 100mbps down (While running Input Director on all three computers.)

http://prntscr.com/evvcxq

Maybe it's a different configuration or installation that I need to do? 

I'm not sure, but I appreciate any help that I can get! :) 

Global Preferences:

http://prntscr.com/evv8bp

Master Preferences:

http://prntscr.com/evv50o

I posted my preferences, which are mostly set to the default options.

Thanks,

Bryan

[Derek E]

Since the machines are all local, you internet connection speed should not matter, but the WiFi latency may matter (aka the amount of time it takes for a packet to get from one computer to another over wifi).

I suggest doing a long ping test from the master to the slave to see how long it takes to get packets there and back over wifi.

Here is an example command to use at command line:

'ping -n 100 10.1.1.115'

While the ping is running, reproduce the lag issue by moving the mouse around on the slave using the master.

At the end of the 200 pings, you will see a summary of the averages and totals. Feel free to share it for my thoughts. In a local network your ping time should be pretty low (under 100ms for sure, hopefully under 20ms)