MuntyYy

Scopes will be added throughout the day.

No problem.
Same FOV as in Hardline - 74. If you play with the same resolution, that is. 

13 Hardline 74 FOV
0.10/ 0.024752 Fortnite 80 FOV, If possible - change it to 100 

Pretty sure it's the Steam version of the game that has the acceleration and that the Origin version is fine.
 

Did some tests with ironsight, reddot, 2x, 3x and 4x now and they are all the same as before. The only thing the override box does is to unify all scope sensitivity into one slider, setting all scopes to the same value (meaning they are matched 100% monitor distance). Iron-sight sensitivity is both reddot, holo and ironsight.

I was being sarcastic...

^
A scope could say 16x, but the devs could have coded it as FOV/16 (e.g. 90/16 = 5.625 FOV), which will be incorrect and the result would depend on what measurement they use (vertical, horizontal, 4:3, etc). The correct result would be (360 arctan(1/16 tan((π 90)/360)))/π =  7.153. Or the devs could use the correct math, but they calculate it from the default FOV and not the actual FOV set by the user.

Technically yes, but don't put too much into the naming of the scopes. They can vary depending on settings and what the devs do with the scope.
Pay instead attention to the actual FOV's of the scopes in the calculator and compare them to the hipfire FOV.

I've made a quick video demonstrating what Monitor Match 0% does with tracking:
The apparent size of the fast moving targets are the same for all the different aims, and they move the same distance on the screen. Using the same script on all the aims you can see that the tracking is exactly the same.

this is a dumb question lmfao

Sent you a PM

That probably means it uses 0% as a default, but others who know for a fact might chime in. I will analyze it and add it next!

That's why you use 76.19% on that 21:9 panel, and 100% on that 16:9 panel, to maintain the same match lol. Of course the percentages aren't going to line up when the calculator is using a percentage of the horizontal, which is dependent on the aspect ratio. If you think of it as a multiplier of the 1:1 aspect ratio, then both examples in your picture would have the same value and the same match point, which will be independent. In that example, it will be a 16/9 coefficient, 1.778. Any monitor match % results in the 'gear ratio', it just depends on what your measuring. Anything above 0%, it is a simple ratio between the angles, they all follow the 'gear ratio' principle. Compare 90/45 Hdeg 4:3 when matched to 4:3 and you will get 2 * the circumference, same thing when comparing 16:9 values when matched to 16:9, or comparing Hdeg or Vdeg if you are match to 1:1 (depends if landscape or portrait). For 0%, it's not just naiively dividing angles, it's the tan ratio, so compare 90 and whatever fov is exactly half of 90, (it is 53.13) and you will get the gear ratio. All monitor match percentages follow this principle. It just depends on where you measure.

Both are added now.

1 is now exactly 1:1. The slider in-game is a bit inaccurate, so when you set it to 1 you get some decimals in the config file.

Yeah that's right
The other factor is also how far away we each sit from said monitor.

Ok so. for anyone who was struggling or just wandered how to change the ADS sensitivity to 100% mm, instead of 00% in COD 4 and 5 at least, here is how
Given the sensitivity - 1.085515 - FOV 80, scale 1.125 ( 360 movement - 60.9825 cm )
The AR at 50*1.125 FOV would have the following sensitivity:
- 1.356071 ( 360 movement - 91.3275 cm )
SMG's would have, at 55*1.125 FOV:
- 1.316826 ( 360 movement - 83.8711 cm )
Sniper rifles, 15*1.125 FOV:
- 1.540946 ( 360 movement - 289.6056 cm )
Pistols, 60*1.125 FOV:
- 1.275022 ( 360 movement - 77.7017 cm )
 
Now, by having all the desired FOV's you may choose one ( for e.g the smg one ) and just use and add in the cfg file the following lines:
 
bind MOUSE2 "+speed_throw;-sprint;vstr zoom;-speed_throw"
seta zoom "vstr zoom1"
seta zoom1 "sensitivity DESIRED ADS SENSITIVITY / MUTIPLIER;seta zoom vstr zoom2"
seta zoom2 "sensitivity HIPFIRE SENS;seta zoom vstr zoom1"
 
Instead of *DESIRED ADS SENSITIVITY* put yours ( at the given FOV, mine is 1.316826 )
For the *MULTIPLIER* field divide your 360 movement ( mine is  60.9825 cm ) with the 360* movement of the SMG FOV ( 83.8711 ),  and replace the value accordingly
And last, but not least at the *HIPFIRE SENS* put your 360 degrees hipfire sensitivity. ( for instance, mine is 1.085515 ).
 
The lines will look like this:
bind MOUSE2 "+speed_throw;-sprint;vstr zoom;-speed_throw"
seta zoom "vstr zoom1"
seta zoom1 "sensitivity 1.316826 / 0.7270978918840936;seta zoom vstr zoom2"
seta zoom2 "sensitivity 1.085515;seta zoom vstr zoom1"
 
Have a nice day.