![]() Anything under 70 ms would be hardly noticeable for me, as the fastest that I can click twice in a row is around 75 ms after some testing. If the issue still occurs, increase the delay time. In addition, adding a 10-20 ms delay after releasing the button can help with issues if a click occurs when the button is released. By adding a 10-20 ms delay after the button is pressed down, the issue is fixed. The issue with fixing it this way is that it reduces the report rate for the mouse (making it less smooth) and this fix is temporary.Ĭreating a macro in GHUB for each mouse button and binding it to the proper button can fix this issue almost entirely, significantly increasing the lifetime of the G502. This meant that the input for the mouse button was not being properly debounced, as most users wouldn't hit a button 1000 times per second (if that's humanly possible). As a temporary fix, I reduced my report rate (in GHUB) from 1000 Hz (1 ms) to 500 Hz (2 ms) to see if this fixed the issue, which it did. So, instead of buying a new mouse, I decided to tackle this issue myself. ![]() I have spent about a week looking for a fix and stumbled across review after review saying that this issue was even more common in new versions of the G502 and other gaming mice across the board (especially the ones using 50 million press switches happening after 3-6 months). My mouse after about 3-4 years developed a double clicking issue on the left mouse button.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |