sensitivity after the convention not accurate to the centimeter ( i am German and my English is bad sry for taht )

[Pullpo]

the mouse is a Logitech G502 Ligtspeed with a DPI of 1600.
(win11 mouse pointer acceleration is off) Aim Lab I use 40 centimeters and convert it to battlefield 2042,
then I measure with a ruler and it's not exactly 40 centimeters.
with my logitech i have to go up to 41 centimeters for a 360.
and with my Razer Viper Ultimate. 38 centimeters for a 360 why is that?


Before that I had the G902 and with it everything was always on point in every game,
always 35 centimetres.
I also wonder if something is wrong in win11 or if both mice are broken,
so technically the DPI is simply not exactly 1600 in terms of software

Edited January 26, 2023 by Pullpo

[DPI Wizard]

The sensors in the different mice are not the same, and rarely are they actually the DPI they say they are. You can test the true DPI in the DPI Analyzer.

It's not uncommon for the sensors to be off by 2-3%, some are even up to 10% off.

[Pullpo]

Thank you for your prompt reply. I analyzed the DPI and it came out at 1433 dpi but I couldn't believe it. 
too bad....
so you should basically always use the DPI analyzer to have it right.

 

 

I have one more question, do I then have to enter 1433 in the control settings for Aim Lab in the DPI to get the exact value?

[DPI Wizard]

Just now, Pullpo said:

I have one more question, do I then have to enter 1433 in the control settings for Aim Lab in the DPI to get the exact value?

Correct, this will make sure the actual physical 360 distance is correct.

1433 sounds very low for 1600 though, are you sure you measured correctly and moved the mouse in a straight line? It's not unheard of though, some sensors are off by very much. But Logitech usually have pretty accurate sensors.

[Pullpo]

vor 12 Minuten schrieb DPI Wizard:

Correct, this will make sure the actual physical 360 distance is correct.

1433 sounds very low for 1600 though, are you sure you measured correctly and moved the mouse in a straight line? It's not unheard of though, some sensors are off by very much. But Logitech usually have pretty accurate sensors.

I have now measured 10 times, this number always comes out 4 centimeters from the left side to the right.

[Pullpo]

 

Now I have Aimlab DPI 1434 35 centimeters for a 360 the sens comes out as a value of 0.36438 everything entered in Mouse Sensitivity Battlefield 2042 resolution 2560x1440p 27 inches 1434 DPI FOV 85 it gives me this value 0.00294953841052. I enter the values in the config, start the game and measure it, I get 31 centimeters out now when I do a 360...... WTF is going on here? do you have an idea

 

 

 

something is not right here it can't be that I get wrong values again even though I know the exact dpi now or do I have to enter 1434 dpi for aim lab and 1600 for mouse sensitivity? is that the mistake?

[DPI Wizard]

2 minutes ago, Pullpo said:

this value 0.00294953841052. I enter the values in the config, start the game and measure it, I get 31 centimeters out now when I do a 360

In that case it sounds like you mouse is indeed very close to 1600. Measuring over just 4 cm using the DPI analyzer is very hard, with such a short distance the error can be quite high.

Measuring over a long distance like at least 25-30 cm is recommended. To do this you have to adjust the WPS in Windows and set the same WPS in the analyzer to get it in range.

[Pullpo]

vor 33 Minuten schrieb DPI Wizard:

In that case it sounds like you mouse is indeed very close to 1600. Measuring over just 4 cm using the DPI analyzer is very hard, with such a short distance the error can be quite high.

Measuring over a long distance like at least 25-30 cm is recommended. To do this you have to adjust the WPS in Windows and set the same WPS in the analyzer to get it in range.

 

what is WPS?

ok i find it out yea its the same on (6 from 11)

Edited January 26, 2023 by Pullpo

[Pullpo]

I test with DPI Analysator 400 DPI, that is 16.5 centimeters and a DPI of 347.74,
 everything is entered and tested, the same problem comes out 31 cm with 400 dpi. My next step mybe reinstall win11 ? i really dont understand the problem 

[Dissorda]

I was also very surprised when I noticed how off my Razer DA2 is. I set 1450 DPI in the software and get about 1615 real DPI. But with these settings now fit my 360° in games.

[Pullpo]

hello me again I still get wrong values. maybe one of you has an idea here, 
you would be grateful if someone reports again and can help me

Edited February 4, 2023 by Pullpo

[d3fct]

I think something is amiss with the measurements.

I have my mouse set to 1600 dpi and if I do the test it says I'm at 900 something (done it 3-5 times and all in the same range).

I just went and did the windows paint trick (use the pencil tool and draw your 1 inch line starting all the way to the left edge and just measure the pixels at the end of your 1 inch line), and I'm a lil over 1500 which seems reasonable when measured by hand.

 

[DPI Wizard]

5 minutes ago, d3fct said:

I think something is amiss with the measurements.

I have my mouse set to 1600 dpi and if I do the test it says I'm at 900 something (done it 3-5 times and all in the same range).

I just went and did the windows paint trick (use the pencil tool and draw your 1 inch line starting all the way to the left edge and just measure the pixels at the end of your 1 inch line), and I'm a lil over 1500 which seems reasonable when measured by hand.

That's basically what the DPI analyzer does. Do you have windows at 100% scale an no zoom in your browser? 

[d3fct]

I do, I just tried with the window maximized and I got a much closer number (almost 1500).

So maybe chrome is scaling it oddly if not fully maximized, idk?

Edited February 5, 2023 by d3fct

[philheath]

might need to get a gpro wireless, all the tests i have seen, its one of the few legit actual dpi mice

Edited February 5, 2023 by philheath

[Pullpo]

thank you for your reply and suggestions.
 I tried it again with rust g502 800 DPI 360 35 CM.
 I measure in rust and get 36.5 CM out..
 is there a program similar to aimlab. where I can also set 35 CM for a 360 
and the program then gives me the sens that I have to enter to get exactly 35 CM for a 360.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

My idea would now be to enter 33.5 CM for aim lab, then I should come up with 35 CM.

 

 so now I've tested and get hold on to 30.5 CM for a 360.
 I've measured it 10 times XD what's going on here. it should be compensated now or am I wrong.

 if one of you felt like it and had the time, 
 he could test whether he got the same result.. if not then I would just reinstall windows.thx for your time guys

Edited February 7, 2023 by Pullpo

[d3fct]

I could be wrong here, but it looks like you are using 2 diff fov's and trying to get them to convert to the same 360 distance.

Again, I could be wrong but I don't think 2 diff fov's will equal the same 360 distance.

[Pullpo]

vor 23 Minuten schrieb d3fct:

I could be wrong here, but it looks like you are using 2 diff fov's and trying to get them to convert to the same 360 distance.

Again, I could be wrong but I don't think 2 diff fov's will equal the same 360 distance.

yes you're right I'll give it a try but I mean I've taken that into account and still get different values in game

[Pullpo]

I have now taken it into account and still have the same problem 
the value has improved by 0.5 CM but I still need 36 CM for a 360

Edited February 6, 2023 by Pullpo