Hi Russ,
Yes, I've discovered the same issue using VNC as well. This is apparently a bug in SDL, which is the platform-abstraction library that PixelCNC uses, and it results in the mouse motion messages from the OS being read incorrectly when there is a remote control application sending event messages to PixelCNC, like Virtual Desktop/VNC/etc. If there has been a fix in a newer version of SDL we'll be updating everything to that. Right now we're just working on getting v1.81b out for the moment, which the build for is pretty much locked for any major changes, and we should have it out by the end of the day :]
Thanks!
- Charlie