Stupid question, but the calculator is only showing the option of either sensitivity or distance for me. How do I use the viewspeed method? 

I'm an idiot, I figured it out. 

Edited October 18, 20178 yr by Cole
...

It's an option for the game you are converting to, in the heading that looks like this: 

19 minutes ago, DPI Wizard said:

It's an option for the game you are converting to, in the heading that looks like this: 

Thanks for the quick response.  So when I'm inputting values to the convert to section (the viewspeed), the monitor distance keeps on getting locked out.  How do I change that? Or is it completely irrelevant? I'm trying to convert my overwatch sensitivity on a 24.5 inch monitor 103 fov to a 15 inch windows desktop and also to a 24 inch overwatch profile with 90 fov (i use mouse and keyboard on xbox and xbox uses 90 fov for overwatch).  Like I said, I can't change the monitor size in the convert to section. 

Just now, Cole said:

Thanks for the quick response.  So when I'm inputting values to the convert to section (the viewspeed), the monitor distance keeps on getting locked out.  How do I change that? Or is it completely irrelevant? I'm trying to convert my overwatch sensitivity on a 24.5 inch monitor 103 fov to a 15 inch windows desktop and also to a 24 inch overwatch profile with 90 fov (i use mouse and keyboard on xbox and xbox uses 90 fov for overwatch).  Like I said, I can't change the monitor size in the convert to section. 

The Monitor Distance percentage selection is only available when you have Monitor Distance selected. It's irrelevant for Viewspeed and 360 Distance. Viewspeed uses a somewhat dynamic formula so the result will be close to Monitor Distance 70%.

1 minute ago, DPI Wizard said:

The Monitor Distance percentage selection is only available when you have Monitor Distance selected. It's irrelevant for Viewspeed and 360 Distance. Viewspeed uses a somewhat dynamic formula so the result will be close to Monitor Distance 70%.

I was specifically referring to "Monitor Size", sorry about that. 

Just now, Cole said:

I was specifically referring to "Monitor Size", sorry about that. 

Aha, the Monitor Size for the game you are converting to is actually not in use, the input size will be used for the calculations. Note that the monitor size is not used in any sensitivity calculation, it's just used to give you ratio output like for instance: 

Ratio: 1 inch mouse movement = 2.7452 inches crosshair movement

2 minutes ago, DPI Wizard said:

Aha, the Monitor Size for the game you are converting to is actually not in use, the input size will be used for the calculations. Note that the monitor size is not used in any sensitivity calculation, it's just used to give you ratio output like for instance: 

Ratio: 1 inch mouse movement = 2.7452 inches crosshair movement

Oh okay. So, just to confirm, the monitor size in the convert to does not matter? You could be converting it to a 100 inch or 10 inch monitor and it would output the same values? 

Yes, you would just get a wrong ratio in the output, but the sensitivity calculations will be correct.

1 minute ago, DPI Wizard said:

Yes, you would just get a wrong ratio in the output, but the sensitivity calculations will be correct.

Is 360 degrees output a ratio? Because I will be using that value for the xbox conversion, since overwatch pc sensitivities are not used in xbox. 

Just now, Cole said:

Is 360 degrees output a ratio? Because I will be using that value for the xbox conversion, since overwatch pc sensitivities are not used in xbox. 

No, just the line in the output that actually says "Ratio:" (Only visible when selecting Monitor Distance).

When using viewspeed, I am trying to convert my overwatch sensitivity to a windows / desktop speed (first pic).  How do I know when I get a quality match?  Am I trying to get the lowest discrepancy valve underneath base length as possible? 

When trying to get the lowest discrepancy value possible, I noticed that changing the windows value to 4 gave me the lowest discrepancy value of -31%, which didn't seem to be that great. Out of curiosity, I ran the test backwards with putting in the windows values that I got from the first test  (550 dpi, 4 windows) to get an overwatch sensitivity (second pic). I was expecting close to the same overwatch sensitivity values that i started with (400 dpi 8.5 sens), but they are not even close, as you can see.  

I am obviously doing something wrong. Can someone help me get my overwatch sensitivity of 400 dpi, 8.5 sens, 6 windows, 24.5 inch monitor, 1920 x 1080 resolution to properly match a desktop / windows sensitivity? 

Edited October 20, 20178 yr by Cole

The Viewspeed calculation in the alpha calculator has some issues (which is why it's still a test), specifically with different resolutions. So I would say those calculations are wrong.

Use the one on the main calculator instead, and you will get a consistent result when converting back and forth. Do not pay attention to the discrepancy when converting TO Windows though, as it has a bug with Viewspeed (this has no effect on the calculation itself).

Regarding discrepancy in general, you should not have to adjust anything to get it closer to 0%, unless it is off by a lot (several percent). It's just an effect of the games lack of fine-adjustment.

I'm still having some issues, even when using the main calculator.   I could not get a close match with my overwatch sensitivity to windows. The windows sensitivity roughly equaled to a 34 cm/360 in overwatch when back calculated while the original overwatch sensitivity was 40.75 cm/360.  

I had an idea to try to first start with the windows sensitivity and just keep changing the WPS and dpi values until i got a close base length to my known overwatch base length of 13.39 cm.  I got very close to that base length, as you can see in the first picture.  When I reversed the calculation, the base length came out to 17 cm, not the original 13, causing the discrepancy to be very large, which you can see in the second picture. 

Does this matter? 

What is base length, anyways? 

If you use Monitor Distance 70% instead of Viewspeed, the discrepancy calculations will be correct as well. Viewspeed will be fixed in a future release. 

I just measured the cm my mouse had to move to get across the windows monitor when set at 350 dpi 5 WPS and its wayyy less than the outputted value of 13.2 in the viewspeed? 

This can mean your mouse DPI is inaccurate, test it here. The math for this is quite simple:

Horizontal Res / WPS / DPI * 2.54 to get cm:

1366/0.75/350*2.54 = 13.2177 cm.

cool, thanks for the help. couple more questions.

What is base length? Also, is viewspeed just a glorified calculator for matching a certain percentage of monitor distance? Because i thought that it was impossible to match sensitivities across different fov's, so what is viewspeed really calculating / accomplishing?  

On 10/27/2017 at 5:18 AM, Cole said:

What is base length?

This is an old thread, but I also have the same question while using Viewspeed. What is base length? Why does it appear so much lower/faster than the actual cm/360°? Is it showing how many centimeters the FOV is comprised of relative to your sensitivity?

2 hours ago, hi23468 said:

This is an old thread, but I also have the same question while using Viewspeed. What is base length? Why does it appear so much lower/faster than the actual cm/360°? Is it showing how many centimeters the FOV is comprised of relative to your sensitivity?

Base length is the arc of the FOV, like L in this picture:

So the goal is to keep the mouse movement to rotate L the same between FOVs.

So the base length indicates how far you have to move your mouse to cover this distance.