360* Distance seems off for me

[KaJ]

Long time lurker, first time subscriber.  I've read through the instructions but maybe I am messing something up here.  The conversion from PUBG to COD Warzone seems perfectly fine but I've noticed the 360* Distance to be off based off my own measurements.  Basically my mouse pad is >19 in wide and doing a full swipe edge to edge still doesn't quite make it to 360* in either game.  However, the calculator shows ~14.0776 in based off my settings.  Am I filling out this calculator wrong somehow?  I double checked my DPI and it is 800.

 

[DPI Wizard]

22 hours ago, KaJ said:

I double checked my DPI and it is 800.

Have you checked with the DPI Analyzer or just in the drivers? 

[KaJ]

1 hour ago, DPI Wizard said:

Have you checked with the DPI Analyzer or just in the drivers? 

I just checked via your analyzer and it showed ~750 after a few runs.  For that calculation are you supposed to keep the cursor in that ruler graphic the whole time or just move it point A to B on your pad?  Either way it was always a little less than 800.  However, even typing that into the calc shows a 360* of 15" though not 18+. 

Edit: I actually just re-tested with a shorter distance and it shows right around 800 now.  I think I was just hitting the edge of my screen with the larger distance.

Edited March 17, 2020 by KaJ

[DPI Wizard]

1 minute ago, KaJ said:

I just checked via your analyzer and it showed ~750 after a few runs.  For that calculation are you supposed to keep the cursor in that ruler graphic the whole time or just move it point A to B on your pad?  Either way it was always a little less than 800.  However, even typing that into the calc shows a 360* of 15" though not 18+. 

Try to keep the cursor on the rules so you move it as straight as possible. But about 750 sounds reasonable, sensors are usually off by a few %.

This wouldn't explain your 360 discrepancy though. I know that the calculations for these games are 100% correct, so there's something else going on. When you're in the PUBG menus, how far do you have to move your mouse to cursor all the way from left to right?

[KaJ]

41 minutes ago, DPI Wizard said:

Try to keep the cursor on the rules so you move it as straight as possible. But about 750 sounds reasonable, sensors are usually off by a few %.

This wouldn't explain your 360 discrepancy though. I know that the calculations for these games are 100% correct, so there's something else going on. When you're in the PUBG menus, how far do you have to move your mouse to cursor all the way from left to right?

A little under 4".. maybe around 3.75".  What should it be?

[DPI Wizard]

25 minutes ago, KaJ said:

A little under 4".. maybe around 3.75".  What should it be?

800 should be 3.2", but you're not that far off. Are you testing the 360 distance in first person or third person?

[KaJ]

9 minutes ago, DPI Wizard said:

800 should be 3.2", but you're not that far off. Are you testing the 360 distance in first person or third person?

May have gone a little past the edge of my screen for that edge to edge measurement. I only play first person. 

[KaJ]

One thing I noticed is that FOV changes the calculated movement needed for 360* but I changed it from 60 to 120 in COD:MW and I always end up in the same spot doing a 360 edge to edge on my mouse pad. The FOV is definitely changing cause I can see it narrow or widen in real time.  The 360* travel distance on my mouse pad never changes though.

[DPI Wizard]

11 hours ago, KaJ said:

One thing I noticed is that FOV changes the calculated movement needed for 360* but I changed it from 60 to 120 in COD:MW and I always end up in the same spot doing a 360 edge to edge on my mouse pad. The FOV is definitely changing cause I can see it narrow or widen in real time.  The 360* travel distance on my mouse pad never changes though.

360 distance for hipfire in MW is not affected by FOV changes. If the calculated sensitivity changes for hipfire when changing FOV it's because you haven't selected 360 distance as the matching method.

[KaJ]

1 minute ago, DPI Wizard said:

360 distance for hipfire in MW is not affected by FOV changes. If the calculated sensitivity changes for hipfire when changing FOV it's because you haven't selected 360 distance as the matching method.

Yeah I just realized that.  PUBG is impacted by FOV but not COD:MW. 

 Still trying to figure out why in it's so far off in both games still.  I am a good  ~4" more distance required when I match my settings.

[DPI Wizard]

Just now, KaJ said:

Yeah I just realized that.  PUBG is impacted by FOV but not COD:MW. 

 Still trying to figure out why in it's so far off in both games still.  I am a good  ~4" more distance required when I match my settings.

That's very strange indeed. Have your tried verifying the 360 distance with script or a sensitivity matcher like this?

[KaJ]

51 minutes ago, DPI Wizard said:

That's very strange indeed. Have your tried verifying the 360 distance with script or a sensitivity matcher like this?

Not until now.  Interesting that it does match your calculator in PUBG.  It says ~14" for a 360. But my pad is definitely 19.2" edge to edge. Is there a reason the actual distance traveled on the pad isn't matching any of these things?

Edited March 18, 2020 by KaJ

[DPI Wizard]

17 minutes ago, KaJ said:

Not until now.  Interesting that it does match your calculator in PUBG.  It says ~14" for a 360. But my pad is definitely 19.2" edge to edge. Is there a reason the actual distance traveled on the pad isn't matching any of these things?

Are you keeping the mouse inside the boundaries of the mouse pad and not centering it on the edge of the pad on both sides? If so you have to subtract the width of the mouse if you haven't already. That in addition to the sensor being lower DPI than configured might explain it. If we assume the 3.75"  you moved from side to side in PUBG is correct and subtract about 3" for the width of the mouse the distance lines up.

The main reason for distance calculated not matching reality is that the true DPI is different. Also some drivers sneakily changes the DPI when launching games.