Standard debouncing (delay) is usually somewhere between 10-20 ms for a button, and does not occur until AFTER the button has been pressed. I tested this by altering the report rate in G HUB for 1000 Hz (a 1ms delay) to 500 Hz (a 2ms delay) and saw that this fixed my issue. Doesn't a software fix affect the response times? Technically yes, but realistically no. It uses non-blocking code for events (meaning that inputs from other mouse buttons should not be blocked during the delay)īut.Delays under 50 ms should be almost un-noticeable.If the issue still occurs or starts occuring again due to age, the delay length can be increased to compensate.It requires opening the mouse and soldering (something that most people aren't comfortable with on such a high-priced device).Most people that I've seen opt for a hardware fix, but replacing the switches has a few issues: A delay under 50ms is recommended for this program. Note: Setting the delay too high can cause missed mouse inputs. Programming is my passion (if you can't already tell by the fact that I'm doing this).
I also thought it would be good to learn a new language (lua) and solve this issue to the best that my ability and free time allows. I had some free time, so I thought I'd solve it. This is a repo created to help fix an issue prevalent in Logitech Gaming Mice.
0 kommentar(er)
