>I said lower end is buffer limitation, which does scale with polling rate.
can you explain where that would lie in the sensor -> mcu -> cable chain
because i'm pretty sure that if some "buffer" were capping out, then either 125hz and 500hz would be the same, or 500hz would have more like 4x the malfunction speed, or the true malfunction speed of the mouse would be hit (which it is).
the real reason that it's hitting a cap at 1.5m/s instead of, like, 4m/s, is probably because it uses a binary sensor array instead of an 8-bit one. you say a binary array is why it feels so responsive. I know that's wrong because I understand how signal processing works. Literally all having a binary array does is introduce posterization -- quantization -- which eliminates information that can be useful when other dimensions are scarce (correlation overlap area) in return for possibly
(and I really mean that: the following statement is speculation) being excessively responsive to initial movements.
We already know that the MLT04 has weird correlation properties (i.e. diagonals). There's no reason to believe that some strange buffering bug is the reason that it malfunctions easily. That would not
be surface-dependent. The much easier explanation is that -- and guess what, this is compatible with the information that the malfunction properties depend on the surface -- the binary sensor array becomes harmful at high speeds, which it obviously does if you have any idea how ICS math works. You can even see it cause jitter on soft pads like the QCK and less on glass ones like the G-Pad.
Indeed, look at what the DTP Soft does. Oh my god.Edited by wareya - 9/25/15 at 8:50pm