
thanks a lot sir! <3
CASE CLOSED!
Mon | Tue | Wed | Thu | Fri | Sat | Sun |
1 | 2 | |||||
3 | 4 | 5 | 6 | 7 | 8 | 9 |
10 | 11 | 12 | 13 | 14 | 15 | 16 |
17 | 18 | 19 | 20 | 21 | 22 | 23 |
24 | 25 | 26 | 27 | 28 | 29 | 30 |
31 |
Edited by drejjk at 06:22 CST, 26 January 2017 - 31907 Hits
Mon | Tue | Wed | Thu | Fri | Sat | Sun |
1 | 2 | |||||
3 | 4 | 5 | 6 | 7 | 8 | 9 |
10 | 11 | 12 | 13 | 14 | 15 | 16 |
17 | 18 | 19 | 20 | 21 | 22 | 23 |
24 | 25 | 26 | 27 | 28 | 29 | 30 |
31 |
wmo is "stable" up tp 8000HzWell putting the word stable into quotation marks already shows that you must have a pretty weird definition for stability. The WMOs I had ran stable up to 500Hz, when I set 1000Hz the rate heavily fluctuated inbetween 500...1000Hz while other mice performed well on the same system, forcing 1000Hz made the rate instable and also didn't raise the maximum speed above 1.5m/s, that is why most users set 500Hz.
mouserate checker shows close to 1000hz at fast movementsComing close to 1000Hz is quite cute but not stable 1000Hz and 1.5m/s ain't a fast movement.
imo the term "stable" should be used when actual use experience shows unstable (I assume you meant "You couldn't be more wrong, personal feeling = voodoo << ... << reproducible measurement, all day every day; trust me, I am an engineer.unstable") behavior, not when some generic measurement setup shows it
the one flaw of wmo, low negative accel threshold could be compensated by accelNo, the WMO will start malfunctioning at movements of 1.5m/s (horizontal axis) while sending wrong reports to the system/game (vertical axis), no matter what ingame acceleration you apply, see IME3.0 that has the same sensor: