Hey Synd1cate,
Good catch — you were right. We looked into it and confirmed that we accidentally posted the 1000Hz results in last week’s retest. I’ve just swapped them out for the correct 8000Hz data and graphs. Sorry for the confusion, and thanks for flagging it to us.
since i noticed a mistake, could you please fulfill my request and test wireless, 2000hz with motion sync, 800dpi, 2mm lod and wired in high speed mode, without motion sync, 800dpi, 2mm lod
I think they suspects the test was conducted at 1000hz because the curve graph appears jagged rather than smooth, unlike the 8k ones.
Edit: I think it also could be firmware issue making 8000hz performs like 1000hz?
no, I tested the pooling rate using mousetester, 8khz is good and stable, it’s their mistake, I don’t want to tie in conspiracy theories, but maybe it’s beneficial for someone to understate the results
so fun guys, if you look at the graph, it’s 1000Hz, and I understand the data was made at 1000Hz without high speed mode, did someone pay you or something?
Which Synapse version are you using? Do you feel like it has accel?
I’m using the latest version. this feels like acceleration because the mouse in fact always works at 8000Hz, which is why at low dpi you get a negative srav. well, to implement 8000Hz you need at least 3200 dpi, but I tested all values starting from 3200 and they all seem bad to me
At what lod did you do the srav test, low mid or high? and could you do similar tests with different lod options, I don’t know why, but the mouse behaves differently with different lod settings at different dpi
Hello again,
We haven’t explored the impact of higher Lift-Off Distance (LOD) settings on sensor latency yet. Our testing primarily focuses on the mouse’s lowest LOD, which we assume most users will utilize, being the default setting in most cases. Consequently, we don’t have data on sensor latency performance at higher LOD settings. During sensor latency testing, the mouse remains on the mousepad’s surface throughout, securely fixed in a rig that moves along a track. This renders the LOD setting irrelevant to sensor latency in our testing setup.
Additionally, the DeathAdder V3 already boasts exceptional sensor latency, scoring a 9.3 in our testing. Any further improvement would likely be minimal and nearly imperceptible, even during the most intense gaming sessions.
Hello Synd1cate,
I appreciate your suggestion to adjust the LOD (Lift Off Distance) settings to high in order to potentially improve sensor latency performance. However, it’s important to note that sensor latency is not typically affected by the LOD settings.
The Lift Off Distance primarily determines how high you need to lift the mouse off the surface before it stops tracking. This setting mainly impacts tracking accuracy and behavior when repositioning the mouse during gaming or other activities. On the other hand, sensor latency refers to the delay between physical movement of the mouse and the corresponding movement on the screen. This delay is influenced by various factors such as the sensor’s technology, firmware, and the processing speed of your computer.
In fact, the mouse remains on the surface throughout the entire testing process of the sensor latency test, the Lift Off Distance setting becomes irrelevant since the mouse is constantly in contact with the surface. Therefore, any potential improvements in sensor latency performance wouldn’t be attributable to changes in the LOD setting.
In theory, as you said, it should work exactly like this, but tests and such experiments are created in order to support these theories, do you have proof in the graphs of exactly what you said?
Can you change the LOD in the settings to high, and check the results again, judging by my feelings, I think the results will change for the better.I’m talking about sensor lantency
I have a question. Sensor latency transition graph looks the same at 400 or 1600 dpi at 1000hz or differently? could you send me a link to a graph of 400 or 1600 dpi? Or if u have 400 or 1600 dpi graph another mouse
I think you need to use a more precise cpi step, because as I know cpi is the resolution of the sensor and if it says that cpi = 400, then this means that we have a resolution of 20x20 counts. I don’t know how mouse manufacturers implement 800 cpi, but I would recommend measuring at 6400, 12800 and 25600 cpi, respectively, and if I’m right then at 4 kHz, or on a wired this mouse should produce the same results at these high cpi as gprox on 400,800,1600
I’m talking about sensor latency video, ur tested this in cs2, and result can be different with 2 sens 400 dpi or 1 sens 800 dpi, or 3.62 400dpi and 3.62 800 dpi?
You mean next friday?
since i noticed a mistake, could you please fulfill my request and test wireless, 2000hz with motion sync, 800dpi, 2mm lod and wired in high speed mode, without motion sync, 800dpi, 2mm lod
no, I tested the pooling rate using mousetester, 8khz is good and stable, it’s their mistake, I don’t want to tie in conspiracy theories, but maybe it’s beneficial for someone to understate the results
so fun guys, if you look at the graph, it’s 1000Hz, and I understand the data was made at 1000Hz without high speed mode, did someone pay you or something?
I’m using the latest version. this feels like acceleration because the mouse in fact always works at 8000Hz, which is why at low dpi you get a negative srav. well, to implement 8000Hz you need at least 3200 dpi, but I tested all values starting from 3200 and they all seem bad to me
At what lod did you do the srav test, low mid or high? and could you do similar tests with different lod options, I don’t know why, but the mouse behaves differently with different lod settings at different dpi
Can u test 3200 dpi srav 8khz and 1khz?
Do you have data on mouse latency at 1000Hz?
Do you have data on mouse latency at 1000Hz?
In theory, as you said, it should work exactly like this, but tests and such experiments are created in order to support these theories, do you have proof in the graphs of exactly what you said?
Can you change the LOD in the settings to high, and check the results again, judging by my feelings, I think the results will change for the better.I’m talking about sensor lantency
I have a question. Sensor latency transition graph looks the same at 400 or 1600 dpi at 1000hz or differently? could you send me a link to a graph of 400 or 1600 dpi? Or if u have 400 or 1600 dpi graph another mouse
I think you need to use a more precise cpi step, because as I know cpi is the resolution of the sensor and if it says that cpi = 400, then this means that we have a resolution of 20x20 counts. I don’t know how mouse manufacturers implement 800 cpi, but I would recommend measuring at 6400, 12800 and 25600 cpi, respectively, and if I’m right then at 4 kHz, or on a wired this mouse should produce the same results at these high cpi as gprox on 400,800,1600
Thanks for your work!
I’m talking about sensor latency video, ur tested this in cs2, and result can be different with 2 sens 400 dpi or 1 sens 800 dpi, or 3.62 400dpi and 3.62 800 dpi?
Can u test with 4khz because motion sync auto turned on at 4khz
Ure tested sensor latency with one sensitivity?
Can u test sensor latency wired?