Overwatch 2

[Dookie]

True, the default value in BF1 is much lower than in OW.

You should be able to match the FOV in both games. (70.53 vFOV in BF1 for 103 hFOV in Overwatch => https://www.mouse-sensitivity.com/forum/topic/2762-fov/)

Additionally the mouse sensitivity is not affected by FOV in both games, like the converter's game infos say. The mouse distance on your mouse pad is the same and not dependent on the FOV. Same for BFV i guess.

Edited November 13, 2018 by Dookie

[nielsenrc]

@Dookie

The limitation of 360 distance calculations is actually when you have very different FOVs. 360 distance works OK when you have games that have relatively similar FOVs (like CSGO and OW) but falls apart when they are radically different (Quake Champions vs CSGO). You'll want to use Monitor Distance or Viewspeed conversions to compensate for large differences in FOV, or else adjust the FOV when possible to be the same between both games. 

I adjusted the Quake Champs FOV down to 103 to match OW and it feels much more consistent (and, according to DPI Wizard, your targets get bigger and easier to hit as you scale down FOV). 

TLDR: If the games have similar FOV, you can get away with 360 distance calculations. If they have very different FOVs, and you can't adjust them to be the same, you need to rely on a different conversion method like monitor distance.

 

[Dawndrake]

Is this right? Do I have to change anything in the conversion setup?

 

Edited November 13, 2018 by Dawndrake

[nielsenrc]

@Dawndrake

If you're just looking for the relative sens for Ashe, I think all you'd need to do is input your sens and DPI and it will give you your relative sens for Widow, Ana, an Ashe. No need to convert it.

[Dawndrake]

1 minute ago, nielsenrc said:

@Dawndrake

If you're just looking for the relative sens for Ashe, I think all you'd need to do is input your sens and DPI and it will give you your relative sens for Widow, Ana, an Ashe. No need to convert it.

It doesn't

[nielsenrc]

Do this (ignore the Black Ops stuff you only need to fill out the first game):

 

[DPI Wizard]

1 minute ago, Dawndrake said:

It doesn't

49 for Widowmaker is close to 100% MDH, so it's best to do it this way (all in one conversion):

[nielsenrc]

Plug in your own settings though of course. Use the Aim "All"

[nielsenrc]

@DPI Wizard Is there a compelling reason not to default to 0% MDH here?

[DPI Wizard]

Just now, nielsenrc said:

@DPI Wizard Is there a compelling reason not to default to 0% MDH here?

No, just saw it was used 49 for Widow, so 100% MDH is close to that. I would prefer 0% indeed!

[Dawndrake]

Thanks for the replies. This better? I wanted to try and be exact.

Edited November 13, 2018 by Dawndrake

[nielsenrc]

I'd do this personally:

I know this is not what you asked, but this is an EXTREMELY high sensitivity. I think you'd benefit a great deal from slowing your mouse down about 25% of what it is. Not kidding at all. It'll be a revelation to you.

Edited November 13, 2018 by nielsenrc

[Dawndrake]

I have a small mouse pad. But I will try and see. Thanks.

[nielsenrc]

If you've got the real estate on your desk and $14, this will be a game changer for you: https://www.amazon.com/SteelSeries-QcK-Cloth-Gaming-Mouse/dp/B000UVRU6G/ref=sr_1_2?ie=UTF8&qid=1542142128&sr=8-2&keywords=qck%2B

[DPI Wizard]

36 minutes ago, Dawndrake said:

Thanks for the replies. This better? I wanted to try and be exact.

Yes, if you like 49 for Widowmaker this is perfect!

[yarr]

On 11/6/2018 at 4:36 PM, Skwuruhl said:

Ashe FOV isn't 66, (for horizontal it's more closely 65.8 but it's not exactly that either)

In fact Widowmaker/Ana FOV aren't 51.

It's actually 40° vertical and 30° vertical respectively.

See: 

https://www.reddit.com/r/Competitiveoverwatch/comments/9ui5hv/ashe_fov_is_66_and_11_relative_sens_is_about_515/e95c2kj/?context=3

and

https://www.reddit.com/r/Competitiveoverwatch/comments/9ujb0i/widowmakers_and_anas_fov_has_changed/

 

hey! you're the guy from reddit that helped me out last year! Cool to see you here too

[Mohbaw]

Do I need to change my relative zoom sensitivity if I changed my FOV?

was on fov 103 , zoom sens = 37,87 switched to fov 90

[DPI Wizard]

2 minutes ago, Mohbaw said:

Do I need to change my relative zoom sensitivity if I changed my FOV?

was on fov 103 , zoom sens = 37,87 switched to fov 90

If you want to keep the same tracking speed yes (i.e. MDH 0%), then it should be 47.64.

Everything will feel faster with 90 fov and this zoom sens though.

[Mohbaw]

thank you.

[Mohbaw]

I have another question 

If I was on 7 sens and 103 FOV and switched to FOV 90 with 5.57 sens will the pixel measurement be the same? 

for muscle memory it was exact the same but wondering about the pixel step

Edited January 7, 2019 by Mohbaw

[DPI Wizard]

3 minutes ago, Mohbaw said:

If I was on 7 sens and 103 FOV and switched to FOV 90 with 5.57 sens will the pixel measurement the same? 

Correct. And if you change to 5.57 you should leave your zoom sens the same as it was since it is based on this value, 47.64 is only if you keep the same sensitivity (and hence the same hipfire 360 distance).

[Mohbaw]

5 minutes ago, DPI Wizard said:

Correct. And if you change to 5.57 you should leave your zoom sens the same as it was since it is based on this value, 47.64 is only if you keep the same sensitivity (and hence the same hipfire 360 distance).

thanks man 

now I understand why I didn't feel aright when I changed the zoom sens so I switch it back to 37,87
that was helpful thank you again

Edited January 7, 2019 by Mohbaw

[octiceps]

Just curious, what causes this slight discrepancy? Is it due to rounding errors during calculation?

BF1 Hipfire to OW Ashe ADS: 51.49

OW Hipfire to OW Ashe ADS: 51.47

 

BF1 Hipfire to OW Ana/Widowmaker Scope: 37.91

OW Hipfire to OW Ana/Widowmaker Scope: 37.89

 

I'm assuming the OW Hipfire to OW ADS/scope conversions are more correct.

[Alcatraz]

Am 8.11.2014 um 22:42 schrieb DPI Wizard:

 

 Overwatch - Hipfire

Location:

In-game

 

Options -> Controls -> Mouse

Sensitivity 1

Minimum:

Sensitivity 1

Default:

Sensitivity 15

Maximum:

Sensitivity 100

Notes:

None

Default FOV:

Field of View 103 | Horizontal Degrees (Resolution Base)

FOV Notes:

Can be adjusted in-game under Options -> Video

Affected by:

FOV: No | WPS: No

Engine:

Overwatch

Added:

2016-05-03

Updated:

2016-07-14

 

 Overwatch - Widowmaker/Ana Scope

Location:

In-game

 

Options -> Controls -> Mouse

Sensitivity 1

Minimum:

Sensitivity 1

Default:

Sensitivity 15

Maximum:

Sensitivity 100

Multiplier 1

Minimum:

Widowmaker/Ana - Relative Aim Sensitivity While Zoomed 0.01

Default:

Widowmaker/Ana - Relative Aim Sensitivity While Zoomed 30

Maximum:

Widowmaker/Ana - Relative Aim Sensitivity While Zoomed 100

Notes:

Setting the Relative Aim to 0 is possible, but result in the same sensitivity as the default 30.
You need to select Widowmaker/Ana as the hero when you are changing the controls to access the Relative Aim Sensitivity setting.

Default FOV:

Field of View 103 | Horizontal Degrees (Resolution Base)

FOV Notes:

The zoomed FOV can not be changed.

Affected by:

FOV: No | WPS: No

Engine:

Overwatch

Added:

2016-05-05

Updated:

2018-11-06

Possible bug?

When converting from Windows to OW, Ana sens results in 37.92 and Ashe sens results in 51.51.

When converting from OW hipfire to OW ADS, Ana sens results in 37.89 and Ashe sens results in 51.47. (Those are the results that seem to be correct.)

Both times 0%MM was used.

 

EDIT: Previous poster seems to be describing a similar phenomenon.

Edited February 20, 2019 by Alcatraz

[Drimzi]

It's not a bug. One result is relative to OW hipfire, and one is relative to Windows.

If your OW had more precision to better match Windows, then you would get 37.89 and 51.47.