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.