Windows Desktop

[ChrisMemes]

Hey whats up guys, just wondering if I'm stupid or something but what I'm trying to do is make it so my overwatch sens is the same as my windows desktop,(ie 1 full 360 in overwatch should be my cursor from 1 monitor edge to another) the calculator keeps telling me to increase my dpi, as my overwatch settings as follow.

 

OVERWATCH

DPI:800

INGAME-SENS:11.35

RES:1920x1080

FOV:103

 

maybe if one of you geniuses can enter it for me and find it out It would be great, thanks so much.

 

ps if you need screenshots or something feel free to ask.

 

 

[DPI Wizard]

The way the desktop conversion works now is a little different than that.

 

What it does is matching the movement from the middle of the monitor on your desktop to the percentage you choose in the "match at" box (0% being exactly under the cursor, 100% being the edge of the monitor), to the same movement as moving the crosshair to this position in a game (where 100% is moving to what you see on the edge of your monitor), or vice-versa. In other words the same distance on your monitor.

 

Matching a full 360 to edge-to-edge movement would probably not feel right.

 

So when you convert from Overwatch to Desktop (which I assume it is you're doing), it's telling you what to set the DPI to in Windows to best match this movement.

[ChrisMemes]

Thanks made it clear as day for me now! Appreciate it!

 

The way the desktop conversion works now is a little different than that.

 

What it does is matching the movement from the middle of the monitor on your desktop to the percentage you choose in the "match at" box (0% being exactly under the cursor, 100% being the edge of the monitor), to the same movement as moving the crosshair to this position in a game (where 100% is moving to what you see on the edge of your monitor), or vice-versa. In other words the same distance on your monitor.

 

Matching a full 360 to edge-to-edge movement would probably not feel right.

 

So when you convert from Overwatch to Desktop (which I assume it is you're doing), it's telling you what to set the DPI to in Windows to best match this movement.

[DNAMTE]

I have been Recently thinking similar. I'v been using 0% matching from 2D - 3D which im thinking of changing.

 

In my opinion setting your cm 360 in ratio with Pi (3.142) isnt such a bad idea.. That is the maximum distance your cursor can travel across your monitor equals one full 360 ingame. Your dealing with the two extremes in terms of relative mouse movement.

 

cm 360 / Pi

 

In my situation using a 4:3 FOV of 90 (106 16:9) yields very close results to the 100% monitor matching option.

 

40cm 360 / Pi = 12.73 (100% monitor match is 11.82cm)

 

Food for thought

Edited January 7, 2017 by DNAMTE

[Skwuruhl]

I have been Recently thinking similar. I'v been using 0% matching from 2D - 3D which im thinking of changing.

 

In my opinion setting your cm 360 in ratio with Pi (3.142) isnt such a bad idea.. That is the maximum distance your cursor can travel across your monitor equals one full 360 ingame. Your dealing with the two extremes in terms of relative mouse movement.

 

cm 360 / Pi

 

In my situation using a 4:3 FOV of 90 (106 16:9) yields very close results to the 100% monitor matching option.

 

40cm 360 / Pi = 12.73 (100% monitor match is 11.82cm)

 

Food for thought

So basically because of :math: this is only true because what you're basically doing is finding the 100% match distance for an fov of 114.59. Which is relatively close to 106.26 so by extent the 100% match distances will be similar. In other words dividing it by pi is completely arbitrary.

 

Math follows:

 

100% match distance for monitors can be calculated by:

fov/360 * (cm per 360) = match distance

for example 106.26 would be

106.26/360 * 40 = 11.81

When dividing 40 by pi to get your match distance you're multiplying 40 by a fov/360 such that fov/360 is equal to 1/pi. So you solve the equation:

fov/360 = 1/pi

and find that fov = 360/pi = 114.59

 

In fact since this is all linear you can just find that 12.73/11.81 = 1.078

 

and then 1.078*106.26 = 114.54 which is only off due to my rounding to two decimals.

 

Also want to point out that that fov of 114.59 is also completely arbitrary because when dealing with degrees pi has no significant meaning. Pi is only significant to measuring angles when using radians.

[DNAMTE]

No equations necissary it was a simple post with little meaning.

 

Besides unless your going to use FOV 180' then there's little point in trying to calculate it with Pi.

I was simply pointing out two maximums, that is 360 distance and monitor distance isn't a bad way to pair 2d - 3d. I personally use 0%.

 

My opinion is pointer acceleration rather than distance is how your brain locks it's targets.