add mode to further improve input latency while maintaining accuracy #8

Merged
Naxdy merged 7 commits from refs/pull/8/head into main 2024-04-08 20:53:24 +00:00
Naxdy commented 2024-04-04 16:54:19 +00:00 (Migrated from git.naxdy.org)

This feels even hackier than consistency mode... we hold off on writing USB reports until the button state actually changes. Passes the input integrity benchmark with ~99.6%, but that doesn't mean much since the challenge is preserving input integrity for inputs less than 8.33ms apart.

Current rate limiter looks good from initial measurements, so will probably merge this at some point and leave it up to users to try the mode out or not. For now, I'd still recommend regular consistency mode, it's still hacky, but way less than this.

Also, not breaking because the new enum for input consistency mode is backward compatible with the bool.

This feels even hackier than consistency mode... we hold off on writing USB reports until the button state actually changes. Passes the input integrity benchmark with ~99.6%, but that doesn't mean much since the challenge is preserving input integrity for inputs less than 8.33ms apart. Current rate limiter looks good from initial measurements, so will probably merge this at some point and leave it up to users to try the mode out or not. For now, I'd still recommend regular consistency mode, it's still hacky, but way less than this. Also, not breaking because the new enum for input consistency mode is backward compatible with the bool.
Sign in to join this conversation.