Local-remote pointer synchronization

Forums / General Discussions / Local-remote pointer synchronization

This topic contains 1 reply, has 2 voices, and was last updated by Avatar fra81 3 months, 4 weeks ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #22098
    Avatar
    darkoverlordofdata
    Participant

    I just started using NoMachine, so I am on the latest free version – my client is 6.6.8.1 from the repository on Manjaro Linux 18.04 using Deepin desktop 15.10. My server is version 6.6.8 running on Windows 10.0.17763

    I’m not having any technical issues – this product works well. I’m using it to connect from Linux to Windows – basically as a thin client because my windows ZenBook has a small screen and keyboard, while my linux box has a 15″ screen and a 101 key keyboard but a slow i3 (old inspiron). So I’m trying Linux as my thin-client.

    The issue I have is that using it for any amount of time causes headache and nausea. I googled, and there is a syndrome ‘cyber sickness’ that is akin to ‘motion sickness’. The cause is a mismatch between visual and physical mouse motion. And sure enough, I am ok while I am browsing the web or typing. But when I start to use the mouse much, nausea and headaches start.

    Does anyone else experience this or is there a way to better synchronize the mouse in NoMachine?

     

     

    #22112
    Avatar
    fra81
    Moderator

    Hi,

    thanks for letting us know that the product is working well.

    About the noticed “motion sickness”, let me point out that, from a technical standpoint,  any “lack of synchronization” is unlikely due to the way NoMachine handles the mouse movements. Mouse movements, in fact, are handled locally and displayed immediately, as they happen, on the client side. In other words, what you see moving on screen, is the local cursor and not the remote one. On the other hand, it’s true, that to see the response of the graphical environment (for example an icon becoming highlighted after a mouse click) the mouse event must reach the remote server, the graphical output encoded, sent and displayed by the client, so that the response can be actually “delayed”, depending on the network latency or the speed of the involved machines. Unfortunately there is very little we can do to avoid this. To better check the latency that exists between the mouse movement and the speed of the server to reflect the change, you can enable showing the remote cursor as it is processed by the server. You can find this option in the Input preferences panel. Such option is turned off in the default settings.

Viewing 2 posts - 1 through 2 (of 2 total)

This topic was marked as solved, you can't post.