Blur Busters Forums

Polling variance between the two devices stays within 1ms at 1kHz, so it should not be that much of a concern, although I understand your general skepsis regarding Windows' input handling of two polled devices. And like I said, I agree that using testing equipement you have full control over and get...

Well, you obviously adjust your test setup so the devices are set to the same polling rate and preferably don't share controllers. The program accounting for physical traits of switch actuation isn't necessarily bad as that is a real latency factor in use as well. But you can use a common switch on ...

How is it a terrible way to measure click latency? It's actually rather precise and consistent, more so than I could achieve with my camera.

You could just use the "bloody" mouse latency software and modify your keyboard and arduino to send M1/M2 commands and actuate them simultaneously. In Windows you can treat the keyboard as a mouse. I think it wouldn't be too complicated to write a program that registers and timestamps keyboard event...

I liked that reply. Will keep an eye on your tests. Anyway, multithreaded rendering must cause frametime variance in order to overcome inherent latency ("This is because multithreaded rendering has to synchronize with the GPU and render thread to avoid latency that can happen when the GPU or driver ...

Taking a look at this article http://www.ganssle.com/debouncing.htm made me wonder just what type of debounce mice use and why. Because click latency commonly is changed with firmware flashing, chances are most use software-based rather than hardware-based debounce techniques. And because click late...

I see. But yes, what you are describing is exactly what I meant. Registering the initial state change and disregading any further changes (or simply not reporting a key/button event for those) for Xms after that. From the button latency in mice we know that they don't use this debounce type. One pos...

I didn't imply otherwise - I actually mentioned just that. There is the possibility of debouncing only after the initial actuation. Entirely possible that Chief actually meant this type of debounce with "after button release" now that I think about it. But again, my guess why it isn't deployed in an...

For debounce to do what it is intended to do it cannot be applied after button release. There is the possibility of debouncing only after the initial actuation, but that is not worthwhile in mice as quick double-clicking wouldn't be possible. In mice, debounce has to be of the "call state stable aft...

How do you get results as low if your monitor's refresh interval of 85Hz dictates on average at least ~12ms delay? You could naturally be looking for changes at the bottom of the screen, but I imagine it takes countless takes to get the impact timing right if you do that. when vsync is off, and fps...