Key sticking issue until I upload firmware

[joefiorini]

I'm on the latest master firmware (commit fd05771) on my Diverge II. I've noticed that any time I reboot my computer or unplug/plug in the keyboard's USB, the master side starts sticking. By that I mean I have to hit every key four or five times before it actually registers. I can work around the issue by uploading the latest firmware again. I actually started noticing this issue when I updated to the commit that contained the debouncing code. Any thoughts on what might be happening here? Any other detail I can provide?

[blahlicus]

Hmm, that's weird, the debounce would hang and cause a "stick" like situation if the slave side is not communicating properly, have you updated the firmware on both the slave and the master?

I can't replicate this with #fd05771 on both master and slave of a D3 on Win10 USB 2.0 and 3.0 with refresh delay set at 1, I also can't replicate this with #fd05771 master + 2.3.1 slave. My D2 is currently on loan to a friend, but I'll also test it out once I get it back.

Also what is your refresh delay setting? Does pressing and holding a key for a while completely eliminate the skipped key? (perhaps the key was not held down long enough for the debounce prevention to wear off?)

The current apparent suspects for me would be either a communication issue in between the sides or over-zealous debounce prevention due to high refresh delay value. Regardless, I'll do a rework on the debounce prevention, currently, it works by requiring a key to be held down for x milliseconds before triggering a keydown event, perhaps I'll experiment on a cooldown based debounce prevention algorithm instead.