If the desired pan rate is 600px/s and you have a 100hz mouse (6px per Hz) and the monitor is 60Hz (10px/frame if smooth):
- Monitor image published (from start) | target viewpoint from start of pan | mouse position as of last update
1/60(0.0166s) | 10px | 6px (update back at 1/100 or 0.0100s)
2/60(0.0333s) | 20px | 18px (from 3/100 or 0.0300s)
3/60(0.0500s) | 30px | 30px (0.0500s, same)
8000Hz mouse? 144Hz monitor? While that would potentially increase the zeroes in the fractions, the better recommendation is to choose a mouse (or configure if possible) that is any multiple of the monitor refresh rate (including 1×). If you have a cheap 100Hz mouse then it is fine paired with a monitor set at 100Hz, and this presumes the video card can keep up with the f/s (it may take an intermediate reading of your super-fast mouse for the next frame), so bottom line (potentially), it’s best to set the mouse/monitor to the same (or multiple of the) update rate, and not retire that sub-100Hz gaming mouse (they seem to exist - I’ve got a logitech, seems to be 60 - I will admit that is slow with today's monitors but you see their intent. Slow mice could be the cause of the stutter that G-SYNC was intended to stop). This writeup is to cover accelerometers too.
C.