Snappy inputs slap
Input delay sucks
See for yourself
Delay:
How poor are they that have not patience!
What wound did ever heal but by degrees?
Thou know’st we work by wit and not by witchcraft,
And wit depends on dilatory time.
You can't eyeball latency. Input delay is too easy to get used to it. Your project will get more and more sluggish. Hard to believe? Just look at… most software, really.
Lower latency is an advantage. But how do you know if borderless windowed or fullscreen is faster? How do you squeeze the most from your setup?
Users can tell when your software is snappy. It feels great! But your teams will sacrifice responsiveness if it's not tracked.
Want to integrate latency testing into your release pipeline? Drop a message!
But first, Late Mate will be crowdfunded. Follow on Twitter and smash the button for updates
Late Mate device takes a testing scenario and executes it, pretending to be a keyboard and a mouse. It's polled at 1kHz, the highest polling rate available for USB<3.0 devices.
From USB controller to software to the kernel to the compositor, your computer works hard to change pixels on the screen.
The device looks at a patch of your screen, waiting for a brightness change. It only takes Late Mate 0.5ms to know that the computer started reacting to the input.
Timing is done completely on-device, so the results are precise no matter what your computer's clock does.
Follow on
Twitter
and subscribe
↓ ↓ ↓