are you playing bf4 with the default fov? do you have uniform aiming enabled with the coefficient at 133 %?

 

and what's your fov in overwatch?

Edited May 28, 20169 yr by stereo3D

Hey Stereo,

 

its all posted in the the photo what settings I used. BF4 is 101 FOV, Uniform aiming I have no touched so this setting is at default

 

Overwatch FOV is at default 103, I heard it was best to leave it at that or it gets difficult to do the math on sensitivity changes.

 

Best,

Hector

both bf4 with uniform aiming and csgo scale it like this:

 

fov 103 at 16:9 = fov 86.63 at 4:3

fov 51 at 16:9 = fov 39.37 at 4:3

 

39.37 / 86.63 = 45.45 %

Should I be putting my percent in overwatch at 45% then? Just want to make sure I am understanding this correctly. Currently have it at 50. This for relative aiming for Widow Maker.

Actually, let me moderate my answer a little; 50 is correct for edge-to-edge screen movement, while 37 is correct for moving 1 count.

The more you move with 37, the more it (quickly) deviates from the hipfire distance, and with 50 it's opposite; it gets more correct the more you move.

 

I'll see if I can get a video up showing this

37 or 38 like people say on Reddit?

Edited May 28, 20169 yr by Ankore

I think, DPI wizard says he has an explanation. Really want his input. :-) or anyone's help who can get concrete info!

37-38 scales down the sensitivity too much. just zoom in while moving your mouse horizontally and you will notice the slow down.

 

use one of the following settings:

 

fov 106 with relative aim 48

fov 102 with relative aim 50

fov 100 with relative aim 51

This thread seems interesting, worth checking out.

Edited May 29, 20169 yr by pubba

for csgo use fov 106 with relative aim 44

 

fov 106 at 16:9 = fov 90 at 4:3

fov 51 at 16:9 = fov 39.37 at 4:3

 

39.37 / 90 = 43.74 %

This thread seems interesting, worth checking out.

I just added support for zoom sensitivity for all CSGO scopes

Could you add Widow zoom sensitivity that is equal to zoom_sensitivity_ratio "1" in CS:GO?

THIS, I WANT THIS SO BAD!

THIS, I WANT THIS SO BAD!

I'll start working on a new mode for the calculator now, a ratio conversion. A mode that keeps the "distance" your crosshair moves constant. The crosshair never really moves, but you get the idea 

 

Four years back when I started this, converting 360 degree turn seemed to be the most universal standard for sensitivity conversion. Later the desktop-to-game conversion came, which in a sense keeps the ratio constant. There are however two problems with this conversion:

1. The distance covered by the mouse pointer in Windows (let's call it X) can never be perfectly matched to moving the crosshair to an object X pixels away all over the screen. This is because the view in an FPS or 3rd person game is spherical, while the view in Windows is obviously two dimensional. The best you can do is match it for one fixed parameter, and I chose moving the cursor from the center of the screen to the edge to match turning to an object at the edge of the screen in-game. This makes short crosshair movement around the center a little bit off, while larger movements towards the edge of the screen match good.
2. The second problem is that you can't convert from one game to another with this mode, you need to base them all off of the Windows / Desktop input.

Now with a ratio conversion (ratio being the correlation between how far you physically have to move the mouse to aim at an object in-game, regardless of FOV), the second problem will be solved. But the first problem is still there to a certain degree, as you have to match the ratio at a fixed point. And I plan to add this as an option if possible, so you choose where you want the ratio to match. For instance a percentage between the crosshair and the edge of the screen.

 

No promises of what will come yet as I haven't started coding, but something like this is the plan.

I'll start working on a new mode for the calculator now, a ratio conversion. A mode that keeps the "distance" your crosshair moves constant. The crosshair never really moves, but you get the idea 

 

Four years back when I started this, converting 360 degree turn seemed to be the most universal standard for sensitivity conversion. Later the desktop-to-game conversion came, which in a sense keeps the ratio constant. There are however two problems with this conversion:

1. The distance covered by the mouse pointer in Windows (let's call it X) can never be perfectly matched to moving the crosshair to an object X pixels away all over the screen. This is because the view in an FPS or 3rd person game is spherical, while the view in Windows is obviously two dimensional. The best you can do is match it for one fixed parameter, and I chose moving the cursor from the center of the screen to the edge to match turning to an object at the edge of the screen in-game. This makes short crosshair movement around the center a little bit off, while larger movements towards the edge of the screen match good.
2. The second problem is that you can't convert from one game to another with this mode, you need to base them all off of the Windows / Desktop input.

Now with a ratio conversion (ratio being the correlation between how far you physically have to move the mouse to aim at an object in-game, regardless of FOV), the second problem will be solved. But the first problem is still there to a certain degree, as you have to match the ratio at a fixed point. And I plan to add this as an option if possible, so you choose where you want the ratio to match. For instance a percentage between the crosshair and the edge of the screen.

 

No promises of what will come yet as I haven't started coding, but something like this is the plan.

 

Excuse me how do i find the calculator and use it? I can't seem to find it in the webpage at all

Excuse me how do i find the calculator and use it? I can't seem to find it in the webpage at all

The calculator is located on the front page (http://www.mouse-sensitivity.com/), but if you mean the ratio one it is not done yet.

The calculator is located on the front page (http://www.mouse-sensitivity.com/), but if you mean the ratio one it is not done yet.

Thanks ! Btw I've spent awhile fiddling with the calculator but I seem to not do it accurately. If my ingame normal sens is 11 what should my relative zoomed in sens be for widowmaker at 103 fov? I'm using a 4000 dpi mouse razer lachesis. Window's dpi is 96x96 , 19.1 inch monitor at  1600x900 resolution. I cant seem to find a way to input accordingly. Please enlighten me on what my zoomed in sens should be if my normal sens is 11?

Edited May 31, 20169 yr by sinfulken

Thanks ! Btw I've spent awhile fiddling with the calculator but I seem to not do it accurately. If my ingame normal sens is 11 what should my relative zoomed in sens be for widowmaker at 103 fov? I'm using a 4000 dpi mouse razer lachesis. Window's dpi is 96x96 , 19.1 inch monitor at  1600x900 resolution. I cant seem to find a way to input accordingly. Please enlighten me on what my zoomed in sens should be if my normal sens is 11?

It should be 50 when your FOV is 103.

It should be 50 when your FOV is 103.

Sorry if I am asking you to repeat but if my normal sens is 11 my zoomed in should be at 50 or is it 50%? 1 question , will this improve aims overall?

 

I really appreciate your calculator and explaination but I am kinda dense regarding dpi sensitivity and stuff.  I am sorry if this sound like a total newb but the value itself to put inside the zoomed sensitivty should be 50 if my normal sens is 11 is that correct? I tried it out and it seems very slippery and fast.

Edited May 31, 20169 yr by sinfulken

Sorry if I am asking you to repeat but if my normal sens is 11 my zoomed in should be at 50 or is it 50%? 1 question , will this improve aims overall?

 

I really appreciate your calculator and explaination but I am kinda dense regarding dpi sensitivity and stuff.  I am sorry if this sound like a total newb but the value itself to put inside the zoomed sensitivty should be 50 if my normal sens is 11 is that correct? I tried it out and it seems very slippery and fast.

Your zoomed sens does not depend of your normal sensitivity. 50 zoom sensitivity means you will have 1:1 (as FoV is 50% reduced on 103) when you are stationary, if you move then the value is closer to 38. I don't know why, but it is.

Edited May 31, 20169 yr by Ankore

Your zoomed sens does not depend of your normal sensitivity. 50 zoom sensitivity means you will have 1:1 (as FoV is 50% reduced on 103) when you are stationary, if you move then the value is closer to 38. I don't know why, but it is.

Not exactly, 50 zoom sensitivity matches moving the mouse to the object at the edge of the screen perfectly, while 37 matches moving only an inch or so on the monitor.

Not exactly, 50 zoom sensitivity matches moving the mouse to the object at the edge of the screen perfectly, while 37 matches moving only an inch or so on the monitor.

Uhm, but why? btw an I wrong and it is 37 instead of 38? 

It's 37.something if I recall correctly. The reason is that with different FOVs it's impossible to match the exact movement in terms of "2d distance" (that is moving the crosshair to an object on the monitor) over the entire monitor. You have to match it to a fixed point, and before or beyond this point it will not match. I'll try to explain this better in a video at a later point

It's 37.something if I recall correctly. The reason is that with different FOVs it's impossible to match the exact movement in terms of "2d distance" (that is moving the crosshair to an object on the monitor) over the entire monitor. You have to match it to a fixed point, and before or beyond this point it will not match. I'll try to explain this better in a video at a later point

So what you're saying is that micro-adjustments of the crosshair will be accurate with ~37 Widow zoom sens, while large adjustments are accurate with 50? I find myself rarely adjusting my crosshair large distances, so would it be better for me if I use 37 than 50?

So what you're saying is that micro-adjustments of the crosshair will be accurate with ~37 Widow zoom sens, while large adjustments are accurate with 50? I find myself rarely adjusting my crosshair large distances, so would it be better for me if I use 37 than 50?

Basically yes, but I have to analyze this further to see how quickly ~37 gives you a disadvantage over 50.

Basically yes, but I have to analyze this further to see how quickly ~37 gives you a disadvantage over 50.

Any update on this? Not to rush you or anything just genuinely curious.

Your zoomed sens does not depend of your normal sensitivity. 50 zoom sensitivity means you will have 1:1 (as FoV is 50% reduced on 103) when you are stationary, if you move then the value is closer to 38. I don't know why, but it is.

I don't understand, in the calculator it's telling me for example 10 sensitivity at 800 dpi is 17.3cm/360 and with widowmaker ADS at 50 with also 10 sensitivity and 800dpi it says it's 34.6cm/360 and in order to get 17.3cm/360 you'd need 100 widowmaker ADS, FOV doesn't have an impact on it.

 

This is all very confusing. Even after reading through every page it's just weird, but I'm going to try going with the 56 that the osu! conversion gave me based on my resolutions, screen size, and fov. But making sense of this is complicated as hell.

Edited June 12, 20169 yr by Keldrath