This thread is a bit old, but I will add my 2 cents. The problem has to do with the way in which the remote desktop is executed and how data is sent to the PC. VNC Viewer uses the graphics of the RPi and sends screen images to the PC. This can cause data bottlenecks at the preferred screen resolution of KStars, 1920x1080. Products like TightVNC create a replica of the RPi desktop on the PC. The result of this different encoding of the screen data means that TightVNC (and probably others) gives a snappier response and fewer, if any, dropouts compared with VNC Viewer. VNC Viewer is really intended for remote tech support whereas TightVNC is intended for headless remote operation.

Read More...