Have I been using the tool right?

[kelvinator]

Hey all, recently got a lifetime membership after paying monthly for about a year as I really dig what this site does so thanks to those who keep it going!

That being said I have continually doubted myself in terms of whether or not I am using the site and calculator correctly and finally figured I would make a post as reading posts and watching videos still has me doubting myself.

I started getting more competitive with FPS games in the past several years and Overwatch happened to be one of the games I started on.

Since then I have been determining the sens I should use for all other games by converting distance from OW.  Below are my settings:

Now ever since I started using the site I was just converting to viewspeed V1 and then to viewspeed V2.

Here is an example of me converting my OW cm/360 to BF4:

NOTE: I change my Vdeg FOV in BF games to 74 or 90 Hdeg FOV. I don't necessarily change FOV's in all the FPS games I play though.

Given that I don't mind spending the time converting sensitivities as I really want that ideal conversion. Is the way I am using the tool actually right, sort of right, or is there a better way to get more accurate conversions?

Apologies in advance if this question gets asked too often.

[potato psoas]

I would use 0% to convert between everything. 360 Distance does not account for a change in zoom. Viewspeed and every other monitor match percentage is arbitrary.

[potato psoas]

Please refer to this forum post if you have any questions:

https://www.mouse-sensitivity.com/forum/topic/4704-conversion-method-guide-and-other-faqs/

Edited September 19, 2018 by potato psoas

[kelvinator]

On 9/18/2018 at 10:34 PM, potato psoas said:

I would use 0% to convert between everything. 360 Distance does not account for a change in zoom. Viewspeed and every other monitor match percentage is arbitrary.

Thanks for the response and the links. I read that one you sent and have been reading through some comments on some other threads. To clarify then, which of the below is correct.

This:

or this:

A few other questions:

• Should I have FOV Scaling ADS and Uniform Soldier Aim on when using converting using 0% monitor distance?
• In this link here: https://www.mouse-sensitivity.com/forum/topic/4524-completely-confused/
  • Drimzi said for 0% monitor distance match that it requires a higher sensitivity in general. Is my 30cm/360 fine? I am not sure what the cutoff point is where a sensitivity becomes too low to use this conversion method.
• I notice FOV is mentioned a lot. Should I generally be changing my FOV in games to try and get a fairly consistent horizontal FOV between all my games? I generally just go with the default FOV for games. BF1 and BF4 being the exceptions where I changed the FOV to 74 Vdeg or 90 Horizontal FOV.

Edited September 20, 2018 by kelvinator

[Fluvio]

Just use Viewspeed or Monitor match for every calculation and you should be good to go.

[MuntyYy]

57 minutes ago, kelvinator said:

Drimzi said for 0% monitor distance match that it requires a higher sensitivity in general. Is my 30cm/360 fine? I am not sure what the cutoff point is where a sensitivity becomes too low to use this conversion method.

You should be fine with 0 at any sensitivity. I've played with over 100cm @ 0 for more than a year and i was pretty decent.

[MuntyYy]

1 hour ago, kelvinator said:

I notice FOV is mentioned a lot. Should I generally be changing my FOV in games to try and get a fairly consistent horizontal FOV between all my games? I generally just go with the default FOV for games. BF1 and BF4 being the exceptions where I changed the FOV to 74 Vdeg or 90 Horizontal FOV.

If you use 0% mm to convert your sensitivity, don't worry too much about the FOV. With practice, your brain will develop the necessary muscle memory for you to be good at a wide range of FOVs.

Edited September 20, 2018 by MuntyYy

[kelvinator]

37 minutes ago, MuntyYy said:

If you use 0% mm to convert your sensitivity, don't worry too much about the FOV. With practice, your brain will develop the necessary muscle memory for you to be good at a wide range of FOVs.

Understood thanks. I take it that it is ideal though to have the FOV in all your games closer than farther apart and not to have an FOV that is really high or really low?

39 minutes ago, MuntyYy said:

You should be fine with 0 at any sensitivity. I've played with over 100cm @ 0 for more than a year and i was pretty decent.

Wow 100cm/360!? Were you just playing CSGO? I feel like my shoulder and arm would fatigue so quickly like that.

 

 

I saw Drimzi saying he recommended viewspeed v2 but that was in the spring and now it looks like he is recommending 0% monitor match distance.

I see that micro adjustments are argued for a lot when making the recommendation of using 0% monitor match distance which is interesting. I don't disagree with it but I was always under the impression that for flicks the point is to flick onto your target on the first go. That being said I was watching some of the aim secret videos by iostux an OW coach and he was mentioning he used to be mostly a flick aimer but started converting more to tracking because its more consistent than flicking. So maybe the lack of consistency when it comes to flicking does indeed cause micro adjustments to happen just due to over or under shooting the target.

When I first got more into this mouse sensitivity stuff I started lowering my sensitivity to be more competitive and have worked to mostly switch to arm aiming versus wrist aiming to save my wrist and not develop carpel tunnel. It sounds like with 0% monitor match distance I will need to be using a combination of my wrist and arm. Which honestly may already be true since I am using 30cm/360 which may not be a low enough sens to strictly use arm aiming. I did notice @Drimzi saying that with 0% you will have to master all the aim styles ( such as micro, finger, wrist, and arm (from elbow and shoulder) movement). I am wondering if this is going to be tough given that I am not a fingertip grip user but am more of a palm grip/relaxed claw grip user which makes it difficult to adjust with the fingers.

Edited September 20, 2018 by kelvinator

[potato psoas]

It's probably better to match your hipfire FOV or try to make most of them similar. Have your "90 FOV" CS:GO games, your "130 FOV" Quake games, etc. all the same... But the problem is when you have to ADS. You are going to have to adjust to a lot of different zoom types unless all you ever play are hipfire-only games. e.g. ADS could be 55 FOV for SMGs, 50 FOV for Assault Rifles, 45 FOV for LMGs, 15 for snipers... Games like Battlefield have even more variety. You are never going to be able to use the same FOV for everything so will inevitably have to learn to adjust. But it's best to make sure your common hipfires use the same or similar FOV to develop that flick muscle memory. But in the end, I wouldn't worry too much.

 

[potato psoas]

5 hours ago, kelvinator said:

which of the below is correct.

This:

or this:

Since you are changing your FOV you must convert your 360 distance, so best to use 0% or whatever.

5 hours ago, kelvinator said:

Should I have FOV Scaling ADS and Uniform Soldier Aim on when converting with 0% monitor distance?

FOV Scaling does not affect your conversions, it just changes the amount of zoom relative to your hipfire FOV in Battlefield. I usually turn it on because I like a fast ADS speed. However, I may turn it off in Battle Royale games like Blackout because the zoom levels are designed in such a way to suit different engagements and you don't want your hipfire FOV to mess with them.

I would turn Uniform Soldier Aim on because then you don't have to convert every single Aim type. Just set all mouse settings to one and let the game do the sensitivity scaling, according to your chosen coefficient - which should be 0% if you are using 0%.

5 hours ago, kelvinator said:

In this link here: https://www.mouse-sensitivity.com/forum/topic/4524-completely-confused/

Drimzi said for 0% monitor distance match that it requires a higher sensitivity in general. Is my 30cm/360 fine? I am not sure what the cutoff point is where a sensitivity becomes too low to use this conversion method.

Yeah I wouldn't worry about that, 30cm/360 is fine. The thing was that when using 0%, the ADS speed feels slower relative to your hipfire. But 0% is actually the fastest method if you convert from the desktop. The cm/360 approaches 0 as you also approach 180 FOV. But I'd completely ignore all of that. Just pick the conversion method you think gives you the most advantage and disregard what sensitivity suits such and such method, as all this does is cause confusion.

5 hours ago, kelvinator said:

I notice FOV is mentioned a lot. Should I generally be changing my FOV in games to try and get a fairly consistent horizontal FOV between all my games? I generally just go with the default FOV for games. BF1 and BF4 being the exceptions where I changed the FOV to 74 Vdeg or 90 Horizontal FOV.

Sure, but don't worry about it too much. You will have to adjust, as I mentioned in my previous post.

[kelvinator]

5 minutes ago, potato psoas said:

It's probably better to match your hipfire FOV or try to make most of them similar. Have your "90 FOV" CS:GO games, your "130 FOV" Quake games, etc. all the same... But the problem is when you have to ADS. You are going to have to adjust to a lot of different zoom types unless all you ever play are hipfire-only games. e.g. ADS could be 55 FOV for SMGs, 50 FOV for Assault Rifles, 45 FOV for LMGs, 15 for snipers... Games like Battlefield have even more variety. You are never going to be able to use the same FOV for everything so will inevitably have to learn to adjust. But it's best to make sure your common hipfires use the same or similar FOV to develop that flick muscle memory. But in the end, I wouldn't worry too much.

 

Okay that makes sense. Since I am converting everything from OW I will probably try to get my FOV for other games close to that. I already had my BF4 and BF1 FOV similar.

I guess for more competitive games I should go for a similar FOV but with a game like Destiny 2 it may not matter as much. In your opinion, is there any downside to changing the FOV's of some of these games. I see no real downside by having the BF games at about 103HFOV and that is the default for OW. But games like Destiny 2 and PUBG have a much lower default FOV. Destiny 2 having an HFOV of 81.6 and PUBG having an HFOV of 80. Obviously the higher the FOV you go the lower the FPS you will get. But are the games like designed to be played at the FOV that is set by the company or is 103 FOV in OW the same as 103 in BF games or Destiny or PUBG? OR is it really dependent on the particular game and whether or not the targets themselves are big enough or you have enough awareness?

Also thanks again for the replies! I spent most of my day at work reading through a bunch of forum posts so I definitely feel I have a much better understanding of things in general now.

[kelvinator]

11 minutes ago, potato psoas said:

Since you are changing your FOV you must convert your 360 distance, so best to use 0% or whatever.

• So then picture 1 is the correct way?

FOV Scaling does not affect your conversions, it just changes the amount of zoom relative to your hipfire FOV in Battlefield. I usually turn it on because I like a fast ADS speed. However, I may turn it off in Battle Royale games like Blackout because the zoom levels are designed in such a way to suit different engagements and you don't want your hipfire FOV to mess with them.

I would turn Uniform Soldier Aim on because then you don't have to convert every single Aim type. Just set all mouse settings to one and let the game do the sensitivity scaling, according to your chosen coefficient - which should be 0% if you are using 0%.

• Oh interesting! So then if I have it on then I only need to change the GetInput.MouseSensitivity Setting for both BF games and not all the multiplier 2 ones listed below?
• 
• If I have the ADS scaling on and I do change each of the multiplier 2 inputs is that bad?

Yeah I wouldn't worry about that, 30cm/360 is fine. The thing was that when using 0%, the ADS speed feels slower relative to your hipfire. But 0% is actually the fastest method if you convert from the desktop. The cm/360 approaches 0 as you also approach 180 FOV. But I'd completely ignore all of that. Just pick the conversion method you think gives you the most advantage and disregard what sensitivity suits such and such method, as all this does is cause confusion.

• I don't convert from the desktop. Is that something I should do?

See comments inline^

[potato psoas]

5 minutes ago, kelvinator said:

Okay that makes sense. Since I am converting everything from OW I will probably try to get my FOV for other games close to that. I already had my BF4 and BF1 FOV similar.

I guess for more competitive games I should go for a similar FOV but with a game like Destiny 2 it may not matter as much. In your opinion, is there any downside to changing the FOV's of some of these games. I see no real downside by having the BF games at about 103HFOV and that is the default for OW. But games like Destiny 2 and PUBG have a much lower default FOV. Destiny 2 having an HFOV of 81.6 and PUBG having an HFOV of 80. Obviously the higher the FOV you go the lower the FPS you will get. But are the games like designed to be played at the FOV that is set by the company or is 103 FOV in OW the same as 103 in BF games or Destiny or PUBG? OR is it really dependent on the particular game and whether or not the targets themselves are big enough or you have enough awareness?

Also thanks again for the replies! I spent most of my day at work reading through a bunch of forum posts so I definitely feel I have a much better understanding of things in general now.

See it's better to have similar FOV but if the game needs a different FOV then change it. Open World games where you have to be aware of enemies in the distance will require lower FOV (like Rust, Planetside 2, etc) but Close Quarters games like Call of Duty and Rainbow Six Siege can have as high a FOV as you want.

"Obviously the higher the FOV you go the lower the FPS you will get."

This is a misconception. FOV doesn't really affect FPS. Since the amount of pixels on your screen doesn't change, you are not increasing or decreasing the amount you have to render. The FPS will be exactly the same or similar, depending on how the game references objects in the game world.

"is 103 FOV in OW the same as 103 in BF games or Destiny or PUBG"

It depends on the FOV type the game uses. The calculator will tell you the Actual Horizontal FOV the game is using. And if you are unsure what FOV type a game uses, it is usually the default when you select a game in the calculator.

[potato psoas]

So then picture 1 is the correct way?

Yes, since it is showing that you are converting using 0% monitor match.

Oh interesting! So then if I have it on then I only need to change the GstInput.MouseSensitivity Setting for both BF games and not all the multiplier 2 ones listed below?

Correct. If you set the coefficient 0 in the calculator it will show you that all the ZoomSens multipliers are 1.0 (or close to 1.0, since there is some error going on) and will give you all the settings you need to change the hipfire and vehicles.

If I have the ADS scaling on and I do change each of the multiplier 2 inputs is that bad?

Well it would be a headache but the calculator will adjust for ADS scaling.

I don't convert from the desktop. Is that something I should do?

Yeah definitely. It helps a lot. As long as I'm converting everything with 0% monitor match, I don't even need to change in-game settings. I can just change my DPI if I want to experiment with my sensitivity. Only reason to change your in-game sensitivity is if you change the FOV or Windows Pointer Speed (and that's if the game is even affected by them).

[kelvinator]

42 minutes ago, potato psoas said:

See it's better to have similar FOV but if the game needs a different FOV then change it. Open World games where you have to be aware of enemies in the distance will require lower FOV (like Rust, Planetside 2, etc) but Close Quarters games like Call of Duty and Rainbow Six Siege can have as high a FOV as you want.

"Obviously the higher the FOV you go the lower the FPS you will get."

This is a misconception. FOV doesn't really affect FPS. Since the amount of pixels on your screen doesn't change, you are not increasing or decreasing the amount you have to render. The FPS will be exactly the same or similar, depending on how the game references objects in the game world.

"is 103 FOV in OW the same as 103 in BF games or Destiny or PUBG"

It depends on the FOV type the game uses. The calculator will tell you the Actual Horizontal FOV the game is using. And if you are unsure what FOV type a game uses, it is usually the default when you select a game in the calculator.

That makes sense! I guess what I meant by "is 103 FOV in OW the same as 103 in BF games or Destiny or PUBG" is if I match the actual HFOV of two different games will it be the same or does it depend on the way the game is created? It sounds like the answer is yes they are the same.

[kelvinator]

26 minutes ago, potato psoas said:

So then picture 1 is the correct way?

Yes, since it is showing that you are converting using 0% monitor match.

Oh interesting! So then if I have it on then I only need to change the GstInput.MouseSensitivity Setting for both BF games and not all the multiplier 2 ones listed below?

Correct. If you set the coefficient 0 in the calculator it will show you that all the ZoomSens multipliers are 1.0 (or close to 1.0, since there is some error going on) and will give you all the settings you need to change the hipfire and vehicles.

If I have the ADS scaling on and I do change each of the multiplier 2 inputs is that bad?

Well it would be a headache but the calculator will adjust for ADS scaling.

I don't convert from the desktop. Is that something I should do?

Yeah definitely. It helps a lot. As long as I'm converting everything with 0% monitor match, I don't even need to change in-game settings. I can just change my DPI if I want to experiment with my sensitivity. Only reason to change your in-game sensitivity is if you change the FOV or Windows Pointer Speed (and that's if the game is even affected by them).

Cool. I am going to give 0% monitor match a shot!

Haha I guess it is a headache to enter each multiplier. I don't mind though. copy and paste is pretty quick...maybe I just have too  much time haha

Do you have a post you can point me to that explains how to convert from the desktop?

[potato psoas]

2 minutes ago, kelvinator said:

Do you have a post you can point me to that explains how to convert from the desktop?

Not sure if there is a post, but I'll say it here.

Firstly, you should set your Windows Pointer Speed to something like 3/11 so you can get more precise increments. i.e. 1600 DPI @ 3/11 = 400 DPI @ 6/11 but 1500 DPI @ 3/11 = 375 DPI, which is a DPI setting that doesn't exist on most mice.

Then what you do is convert your best game/settings to Windows/Desktop, like so:

Make sure to convert using 0%, make sure all the variables are correct, etc.

It will give you the DPI you should use instead. In this case, it is 1110 DPI @ 3/11 WPS. Keep in mind, since you will never be able to perfectly convert your DPI, you will have to round it up or down to your mouse's closest increment. And so your old game will have a slightly different sensitivity. But that is okay, it won't feel very different at all. Then you'll have to reconvert your new DPI to everything, even your chosen game, like so:

Since my mouse uses increments of 100 DPI I had to round down to 1100DPI.

Then you can just save this as a profile and do the same for every other game you play:

[potato psoas]

25 minutes ago, kelvinator said:

That makes sense! I guess what I meant by "is 103 FOV in OW the same as 103 in BF games or Destiny or PUBG" is if I match the actual HFOV of two different games will it be the same or does it depend on the way the game is created? It sounds like the answer is yes they are the same.

If the Actual HFOV is the same then you can convert with 360 Distance, but there really is no point since every other conversion method will give the same result. All methods use similar mathematics to reach their conclusions - they all follow the gear ratio principle.

[MuntyYy]

8 hours ago, kelvinator said:

Wow 100cm/360!? Were you just playing CSGO?

COD promod, mainly with the scope. 

3 hours ago, potato psoas said:

As long as I'm converting everything with 0% monitor match, I don't even need to change in-game settings.

How can you use 275 dpi in 2d ? What if your sensitivity is around 70 cm/ 360... 170 dpi is nuts. Am I missing something ?

[potato psoas]

14 minutes ago, MuntyYy said:

COD promod, mainly with the scope. 

How can you use 275 dpi in 2d ? What if your sensitivity is around 70 cm/ 360... 170 dpi is nuts. Am I missing something ?

Wait 275 @ 6/11 or 275 @ 3/11?

[MuntyYy]

275 @6, 1100 @ 3                                             

[potato psoas]

11 minutes ago, MuntyYy said:

275 @6, 1100 @ 3                                             

Yeah that's why you gotta use 3/11. 1100 @ 3/11 is useable. I actually used to use 1100 for a long while.

[MuntyYy]

Wow... and I'm here complaining about 400dpi @ 6.. 

[kelvinator]

I am curious after all this discussion and reading I did yesterday. Does anyone who was using viewspeed v1 or v2 or horizontal monitor match at 75% or 56.25% that switched to 0% notice an improvement in their performance and aim or is it something that people readjust to over time and over time their aim gets better?

[MuntyYy]

I've switched back from 100% mm to 0, feels like home. Drimzi switched as well, from viewspeed to 0.