Overclock.net › Forums › Components › Mice › Firmware Added Button Delay Testing Attempts(Tapping mouse buttons lightly)
New Posts  All Forums:Forum Nav:

Firmware Added Button Delay Testing Attempts(Tapping mouse buttons lightly) - Page 33

post #321 of 387
Thread Starter 
Last time I wired up and tested the FK1('fixed" revision) it was 10ms. I'd check again, but I would have to buy it again(no ty).
post #322 of 387
Quote:
Originally Posted by Mediumost View Post

Thanks for the answers guys!

If I sand the buttons down, will the FK1 have button delat that could be compared with the delay of a good mouse or will it still be kind of bad? Will replacing the switches help some, like if I put some d2f-01f switches in it?

How would a "fixed" FK1 perform button delay wise if you compare it to for example G400?

I actually don't advise sanding. If done wrong it can make things even worse. I mentioned it just because it's the only thing that can be done (maybe you can get a LITTLE softer clicks if you replace switches with something from omron, but people reported that the difference is miniscule).

Button delay is not affected by shell, afaik. It's routine that runs on mouse's electronics. It can "feel" better if the clicks are lighter though.
post #323 of 387
Quote:
Originally Posted by uaokkkkkkkk View Post

Last time I wired up and tested the FK1('fixed" revision) it was 10ms. I'd check again, but I would have to buy it again(no ty).

How much ms has the Logitech G400 and SteelSeries Rival 300 and Rival 100?

And how would i know if i have a FK1 fixed revision?

Which switches are the most easy to click ones on the market? d2f-01f?
post #324 of 387
Thread Starter 
Any zowie mouse manufactured from like Jan 2015 to today is the latest revision. So basically anything purchased through eg webshops and in store as of 2015.

For G400 1ms. For Rival 300 7ms.

D2f-01f's are well regraded in that category, so yes.
post #325 of 387
Quote:
Originally Posted by Mediumost View Post

Thanks for the answers guys!

If I sand the buttons down, will the FK1 have button delat that could be compared with the delay of a good mouse or will it still be kind of bad? Will replacing the switches help some, like if I put some d2f-01f switches in it?

How would a "fixed" FK1 perform button delay wise if you compare it to for example G400?

post #326 of 387
Is there anyone who tested the button delay on DM1 Pro S? It looks nice and from what i can Read the DM2 Confy got really good button delay while DM1 Pro got worse delay, is that correct?
post #327 of 387
From http://www.overclock.net/t/1607990/click-latencies-compiled the original pro is 1.3ms and the new pro s is 6.2ms. 6.2ms is still better than most though.
post #328 of 387
Quote:
Originally Posted by chr1spe View Post

From http://www.overclock.net/t/1607990/click-latencies-compiled the original pro is 1.3ms and the new pro s is 6.2ms. 6.2ms is still better than most though.

Oh, thanks man!

Do you guys have any info about the buttons on DM1 Pro, if they are stiff or soft? Anyone who have been able to compare them to Zowie FK or ZA buttons?

I will order either the DM1 or the DM2 but the DM1 will be totally out of the picture if the buttons are stiff like on FK or ZA. I know how the buttons on the DM2 is since DM2 is same as Mionix Naos 7000 which i own one.
post #329 of 387
I've made some tests.
RX-250 - 16.05 ms
ZM-M600R - 2.90 ms
G502 - 2.78 ms
G403 - 2.72 ms

Above are median values with g100s as baseline. Median values are used since I got big range (max - min values).
May be it caused by using g100s as baseline (not Ikari like uaokkkkkkkk did). No soldering used (dunno it matters or not). One wire, pressed g100s micro switch.
I don't like these big ranges (max - min values). By looking at source code of software I see QueryPerformanceCounter used.
If I understand correctly TSC or HPET can be used to time/register clicks. Tried both almost no difference (less 1 ms).
I tried changing USB port, using front USB, disabling 1000Hz rate keyboard (Logitech G910), even plug mouse in USB 3.0. This makes almost no difference (less 1 ms).
Any suggestion how to improve results? May be linux with new software and new setup will help smile.gif
More info about tests with setup
raw data of tests

Logitech RX-250 - 125hz. Some default office mouse with build-in harware mouse accel. Just for testing.
Zalman ZM-M600R - 1000hz fw 2.26. It's a export version of Skydigital NMouse 4K.
Logitech G502 - 1000hz fw 88.2.16. Model proteus core.
Logitech G403 - 1000hz fw 108.1.12 (release). Wired model.
Logitech G100s as baseline - 500hz. Blue colored model. Does black model differ?
post #330 of 387
Thread Starter 
By the way what does the setup look like? One wire wrapped up around the switch contacts or something?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mice
Overclock.net › Forums › Components › Mice › Firmware Added Button Delay Testing Attempts(Tapping mouse buttons lightly)