Jump to content

Atlas

Added!
Read more...

Just Cause 4

Just added!
Read more...

Supraland

Acceleration is fixed and sensitivity numbers are added, so this game is in!
Read more...

Hitman 2

Pretty much the same as the previous Hitman, but here it is!
Read more...

Spellbreak

In-game and config file sensitivity added!
Read more...
DPI Wizard

Overwatch

Recommended Posts

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 by Dookie

Share this post


Link to post
Share on other sites

@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.

 

Share this post


Link to post
Share on other sites
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

New Bitmap Image.png

Share this post


Link to post
Share on other sites

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.

Screen Shot 2018-11-13 at 2.28.41 PM.png

Edited by nielsenrc

Share this post


Link to post
Share on other sites
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 :)

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
Posted (edited)

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 by Mohbaw

Share this post


Link to post
Share on other sites
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).

Share this post


Link to post
Share on other sites
Posted (edited)
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 by Mohbaw

Share this post


Link to post
Share on other sites

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

BF1 Hipfire to OW Ashe ADS: 51.49

qvoVF1l.png

OW Hipfire to OW Ashe ADS: 51.47

V5D694f.png

 

BF1 Hipfire to OW Ana/Widowmaker Scope: 37.91

3KhAwo1.png

OW Hipfire to OW Ana/Widowmaker Scope: 37.89

RUFYNXj.png

 

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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×