How precise does the calculator work?

[uncle.dolan]

Hello everyone!

I recently discovered this awesome little tool here.

I am a huge fan of Rainbow Six Siege and play ranked with my friends a lot. Sadly, the game lacks some sort of training maps like they are available in Counter Strike.

So I thought, why not use Counter Strike to train aim?

The only thing is, it is quite difficult to measure your exact mouse distance on the mouse pad. I calculated the 360 distance for CS:GO with my mouse settings from R6 Siege. Mouse acceleration in Windows off and Windows mouse speed at 6. I even use the MarkC Mouse fix, because some older games (Half Life 1 etc.) still want to use this stupid acceleration.

My R6 Siege settings are: V 10, H 10, 83 ADS (doesn't matter in this case), FOV 90, 24 inch monitor. Standard aim multiplier (0.02).

I converted this to the 360 distance for CS:GO and have in both games a 360 distance of 15.708 inches. My problem is, I cant stop feeling like the the viewspeed in CS is slightly off. Could this be because of the field of view, which seems to be different in these two games?

Its very possible that there is no problem at all, and it all exists just in my head :D

Thank you for helping me out!

[DPI Wizard]

For most games the calculation is 100% accurate. Some games do have issues with packet loss or acceleration so the measurement will not always line up with the calculation.

Siege and CSGO don't have any issues with this though. The issues here is the FOV as you assume. The best practice is to always use the same FOV, this is however not possible in all games.

[uncle.dolan]

I am not sure if there is any issue at all. I had half an hour of spare time and tried to measure it physically with markers on my desk and a long ruler.

Seems to be pretty accurate. I was a few degrees off every time (measured both games twice), but I think that could be due to the measuring method, which is pretty inaccurate itself.

Anyway, thanks for your quick reply and sorry for creating a useless thread!

[Nereithr]

FOV 90 in R6Siege isn't the same as CSGO's 90 FoV. CSGO's FoV is roughly quivalent to 74 in R6Siege.

If you want more accurate viewspeed you need to do monitor distance match or viewspeed, not 360 distance.

Edited June 15, 2018 by Freeway
Wording

[uncle.dolan]

Wait, I don't understand

I have a 360 distance of 15.708 inches in both games. Even if the fov is different, the 360 distance should be the same? Means, that I need to move my mouse ~ 1mm to turn for 1degree in the game?

[Drimzi]

Since both games have different fovs, they will look like different speeds when moving the camera.

Matching the 360 distance is not the solution for this problem, so don't fret about whether or not the measurements are correct. You can put your ruler away.

The fix for this issue is viewspeed V2, but really this issue isn't something you should worry about anyway.

Distances and speed should scale proportionately with the fov, and matching them is just going to be detrimental to your aim in the long run.

Convert using 0% monitor match instead of 360 distance or viewspeed. What this does is scale sensitivity with the focal length of the camera. 0% is not a distance, but rather the velocity will be constant. This is most likely how your brain will expect the sensitivity to behave without predisposed muscle memory and bias.

The issues...Lower fovs will result in larger screen distances between targets, and thus require larger physical movement, and the opposite is true for higher fovs, so distances will not be constant and different fovs will require different muscle groups (finger, wrist, arm), and the difference in fov and distortion will cause a perceived speed difference, but in the end the distances are what is expected and speed is just something you perceive (and should ignore) in the middle of performing a movement. 360, viewspeed, and monitor distance match methods (with higher percentages) all combat different issues, but these issues are things you should just accept. The only solution is to match the fov.

[uncle.dolan]

So if I want to keep the mouse settings, I should adapt my FOV in R6 to CS? Means, that the FOV in R6 should be at 74 to match the FOV from CS, which I can't change?

[MuntyYy]

Just use viewspeed 2, or a type of monitor match

[uncle.dolan]

So I calculated with a monitor match of 0%. 360 Distance of R6 is still at 15.708 inches, but the distance for CS is at 20.9439 inches.  I still don't understand how this works, but I tried it in CS and it felt good immediately. But I still don't really get why.

I am thinking about keeping the old value for the sensitivity at CS and switching the FOV in R6 to 74. This should be the easiest solution, because the 360 distance would be same for both games and the FOV should also be the same.

Edited June 17, 2018 by uncle.dolan

[MuntyYy]

If you can change the FOV in R6 then that's the better thing to do

[uncle.dolan]

Yes, that is possible.

Only thing I am not sure about now is that R6 uses the value of the vertical FOV, whereas CS uses the value for the horizontal FOV. But 74 vertical should be fine I think.

[MuntyYy]

Different games, different engines, try to set the FOV in R6 to 73.74 and you're ready to go

[Drimzi]

It's just different measurements for the same thing. As long as the Actual vfov  value is identical, you will avoid any illusive issues. Don't forget you can change csgos fov with server cheats enabled if you are playing csgo for training purposes.

[uncle.dolan]

Good point, I didn't think about this. I mostly play CS for training, but on rare occasions I play ranked there too. So changing the FOV in R6 was the best solution, I wanted to reduce this there anyway for different reasons.

Thank you for your help, everything seems to be fine now. Only thing is, I cant change FOV in R6 to decimal values, but I think 74 is fine. I updated my CSgo sensitivity with the monitor calculation, which is slightly lower now.