Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Sluggish mouse


Recommended Posts

Hi

I switched to the v2 beta4 with my master running Ubuntu 16.04 64 and my slave Windows 10 64. I'm connected to my Symless account and I am getting access to both machines, but the mouse on the slave machine is very sluggish.

Anything can be done to get a smooth mouse? This was not an issue with v1.8

Thanks!

Link to post
Share on other sites

Any idea on troubleshooting this problem? The service is not really usable with a mouse that keeps jumping around every time I am on my secondary monitor.

Link to post
Share on other sites

What's also weird is the mouse dies when using the keyboard on the client computer. I have to go back to the other computer and press F12?

Unless that's by design and it assumes I only use one set of a keyboard+mouse. I am using 2 laptops, one mouse. I want the mouse to remain seemless (works great otherwise).

So far the copy paste files and drag-n-drop between computers isn't working? Is that on the way? Or should I just stick with Version 1?

Edited by joedf
Link to post
Share on other sites
Brian Davis

Sounds like something is broken. It shouldn't disconnect when using the other keyboard. I'm not sure drag n drop files is working yet in the beta, but I know copying to the clipboard between both machines does work pretty reliably from what I've seen (I'm using Windows + Mac.)

Link to post
Share on other sites

The text copy-works great. The file copy-past is a no-go. Sometimes I can use both keyboards and the mouse will still work. Looking at the logs, it seems that the services are occasionally de-synchronized. I have to repeatedly return to the other computer and do F12 to force an update which sometimes lags also. Right now it works just fine as i'm writing this post, except the mouse is slightly sluggish at a few rare times.

Edited by joedf
Link to post
Share on other sites
GranPaSmurf

When I was using beta 3 & 4, I didn't notice any lag. In the past, I have noticed it in version 1 and noticed that also there was an auto-scan running of a virus scan. In other words, on that particular older machine, it seemed to be an issue of resource/memory utilization. The lag went away when the scan finished. Nick is aware of this lag on some setups and said that beta 5 would bypass whatever was causing it. We're hoping for beta 5 in the next couple of weeks.

  • Like 1
Link to post
Share on other sites

Switched back to v1.8.8 which is perfectly smooth. The beta 4 feels like it's trying to stop or slow down at every horizontal line on the monitor or something like that. It's not usable to work with.

Waiting for beta 5 now...

  • Like 1
Link to post
Share on other sites
2 hours ago, Herve said:

Switched back to v1.8.8 which is perfectly smooth. The beta 4 feels like it's trying to stop or slow down at every horizontal line on the monitor or something like that. It's not usable to work with.

Waiting for beta 5 now...

+1

Link to post
Share on other sites
  • 3 weeks later...
  • Synergy Team
Nick Bolton
3 minutes ago, joedf said:

Great! I will try it out soon and report back on this :D

Looking forward to hearing about it!

Link to post
Share on other sites

It's a lot better, much smoother transition. The only downside is when I use my keyboard on the 2nd computer, I lose the sync for a few seconds until I activate/click the Synergy window on the main computer. :)

Link to post
Share on other sites

Running beta 5 and noticing a slight 'lag' when transitioning from Server to client.  Sometimes I have to 'ram' the mouse to the side before the client acknowledges the mouse has transitioned.

I would say roughly a half second lag.  Sometimes more when a game is going like World of Warcraft.

This is on Windows 10x64.

Link to post
Share on other sites
  • Synergy Team
Nick Bolton
8 hours ago, Keiichi25 said:

Sometimes I have to 'ram' the mouse

Do you see a "bogus delta motion" log line? 

Link to post
Share on other sites
Robert Sillett

I too am experiencing a significant (i.e. sadly, unusable) lag with the mouse on the client PC.  My setup is very simple.  I have a desktop Windows PC that is the master and a Microsoft Surface Pro 4 as a client.  I'm afraid that I need to revert to Synergy v1 as v2 is just not working right.  The mouse transfers from the master to the client only rarely.  And when the mouse does transition over, it's very slow on the client.

It would be great if you would add back the manual configuration options that you have in Synergy v1.  Think about making it an option.  You can configure in cloud mode or legacy mode.  

Link to post
Share on other sites
  • Synergy Team
Nick Bolton
4 minutes ago, Robert Sillett said:

It would be great if you would add back the manual configuration options that you have in Synergy v1.  Think about making it an option.  You can configure in cloud mode or legacy mode.  

We'll be adding a manual config mode in 2.1.

Link to post
Share on other sites
5 hours ago, Nick Bolton said:

Do you see a "bogus delta motion" log line? 

Nope.  I see the following:

Quote

[ Core ] [2017-11-03T08:04:54] INFO: switch from "Keiichi" to "SKasai-Yoga900" at 3199,1799

[ Core ] [2017-11-03T08:04:54] INFO: leaving screen

[ Core ] [2017-11-03T08:04:54] DEBUG: open clipboard

[ Core ] [2017-11-03T08:04:54] DEBUG: close clipboard

[ Core ] [2017-11-03T08:04:54] DEBUG: ignored screen "Keiichi" update of clipboard 0 (unchanged)

[ Core ] [2017-11-03T08:04:54] DEBUG: open clipboard

[ Core ] [2017-11-03T08:04:54] DEBUG: close clipboard

[ Core ] [2017-11-03T08:04:54] DEBUG: ignored screen "Keiichi" update of clipboard 1 (unchanged)

[ Core ] [2017-11-03T08:04:54] INFO: switch from "SKasai-Yoga900" to "Keiichi" at 1,1070

[ Core ] [2017-11-03T08:04:54] INFO: entering screen

[ Core ] [2017-11-03T08:04:54] INFO: switch from "Keiichi" to "SKasai-Yoga900" at 3199,1799

[ Core ] [2017-11-03T08:04:54] INFO: leaving screen

[ Core ] [2017-11-03T08:04:54] DEBUG: open clipboard

[ Core ] [2017-11-03T08:04:55] DEBUG: close clipboard

[ Core ] [2017-11-03T08:04:55] DEBUG: ignored screen "Keiichi" update of clipboard 0 (unchanged)

[ Core ] [2017-11-03T08:04:55] DEBUG: open clipboard

[ Core ] [2017-11-03T08:04:55] DEBUG: close clipboard

[ Core ] [2017-11-03T08:04:55] DEBUG: ignored screen "Keiichi" update of clipboard 1 (unchanged)

[ Core ] [2017-11-03T08:04:55] INFO: switch from "SKasai-Yoga900" to "Keiichi" at 1,1062

[ Core ] [2017-11-03T08:04:55] INFO: entering screen

[ Core ] [2017-11-03T08:07:40] INFO: switch from "Keiichi" to "SKasai-Yoga900" at 3199,1025

[ Core ] [2017-11-03T08:07:40] INFO: leaving screen

[ Core ] [2017-11-03T08:07:40] DEBUG: open clipboard

[ Core ] [2017-11-03T08:07:40] DEBUG: close clipboard

[ Core ] [2017-11-03T08:07:41] DEBUG: ignored screen "Keiichi" update of clipboard 0 (unchanged)

[ Core ] [2017-11-03T08:07:41] DEBUG: open clipboard

[ Core ] [2017-11-03T08:07:41] DEBUG: close clipboard

[ Core ] [2017-11-03T08:07:41] DEBUG: ignored screen "Keiichi" update of clipboard 1 (unchanged)

[ Core ] [2017-11-03T08:07:43] INFO: switch from "SKasai-Yoga900" to "Keiichi" at 2,618

[ Core ] [2017-11-03T08:07:43] INFO: entering screen

[ Core ] [2017-11-03T08:09:43] INFO: switch from "Keiichi" to "SKasai-Yoga900" at 3199,857

[ Core ] [2017-11-03T08:09:43] INFO: leaving screen

[ Core ] [2017-11-03T08:09:43] DEBUG: open clipboard

[ Core ] [2017-11-03T08:09:43] DEBUG: close clipboard

[ Core ] [2017-11-03T08:09:43] DEBUG: ignored screen "Keiichi" update of clipboard 0 (unchanged)

[ Core ] [2017-11-03T08:09:43] DEBUG: open clipboard

[ Core ] [2017-11-03T08:09:43] DEBUG: close clipboard

[ Core ] [2017-11-03T08:09:43] DEBUG: ignored screen "Keiichi" update of clipboard 1 (unchanged)

[ Core ] [2017-11-03T08:09:43] INFO: switch from "SKasai-Yoga900" to "Keiichi" at 1,515

[ Core ] [2017-11-03T08:09:43] INFO: entering screen

In this instance, I get the occasional delay.  Looking further back, I don't see any "bogus delta delay" messages.

Link to post
Share on other sites

Here is another log:

Quote

[ Core ] [2017-11-03T13:38:39] NOTE: Cursor is locked to screen, check Scroll Lock key

[ Core ] [2017-11-03T13:38:39] NOTE: Cursor is locked to screen, check Scroll Lock key

[ Core ] [2017-11-03T13:38:39] NOTE: Cursor is locked to screen, check Scroll Lock key

[ Core ] [2017-11-03T13:38:39] NOTE: Cursor is locked to screen, check Scroll Lock key

[ Core ] [2017-11-03T13:38:39] NOTE: cursor unlocked from current screen

[ Core ] [2017-11-03T13:38:39] DEBUG: active sides: 2

[ Core ] [2017-11-03T13:38:39] INFO: switch from "Keiichi" to "SKasai-Yoga900" at 3199,612

[ Core ] [2017-11-03T13:38:39] INFO: leaving screen

[ Core ] [2017-11-03T13:38:39] DEBUG: open clipboard

[ Core ] [2017-11-03T13:38:39] DEBUG: close clipboard

[ Core ] [2017-11-03T13:38:39] DEBUG: ignored screen "Keiichi" update of clipboard 0 (unchanged)

[ Core ] [2017-11-03T13:38:39] DEBUG: open clipboard

[ Core ] [2017-11-03T13:38:39] DEBUG: close clipboard

[ Core ] [2017-11-03T13:38:39] DEBUG: ignored screen "Keiichi" update of clipboard 1 (unchanged)

[ Core ] [2017-11-03T13:38:39] INFO: switch from "SKasai-Yoga900" to "Keiichi" at 1,366

[ Core ] [2017-11-03T13:38:39] INFO: entering screen

[ Core ] [2017-11-03T13:38:39] INFO: switch from "Keiichi" to "SKasai-Yoga900" at 3199,565

[ Core ] [2017-11-03T13:38:39] INFO: leaving screen

[ Core ] [2017-11-03T13:38:39] DEBUG: open clipboard

[ Core ] [2017-11-03T13:38:39] DEBUG: close clipboard

[ Core ] [2017-11-03T13:38:39] DEBUG: ignored screen "Keiichi" update of clipboard 0 (unchanged)

[ Core ] [2017-11-03T13:38:39] DEBUG: open clipboard

[ Core ] [2017-11-03T13:38:39] DEBUG: close clipboard

[ Core ] [2017-11-03T13:38:40] DEBUG: ignored screen "Keiichi" update of clipboard 1 (unchanged)

[ Core ] [2017-11-03T13:38:42] INFO: switch from "SKasai-Yoga900" to "Keiichi" at 43,777

[ Core ] [2017-11-03T13:38:42] INFO: entering screen

This was right after noticing the scroll lock was enabled, noticing about a half second to second lag.  Sort of feel like I had to 'ram' the mouse to get it to go over to the client side.

I should redefine what I mean by lag, by a 'pause' between hitting edge of screen on server, seems to sit there and then shows it going over to client screen.  But from client to server, no noticeable pause.

Also - Suggestion - Don't re-center the mouse pointer.  It can cause some confusion as to where the mouse is on the 'non-active' screen.

Link to post
Share on other sites
  • Synergy Team
Nick Bolton
18 hours ago, Keiichi25 said:

Don't re-center the mouse pointer

This is a bug, it'll be fixed soon.

  • Like 1
Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...