Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/18/2018 in all areas

  1. 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.
    3 points
  2. ^ 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.
    1 point
  3. 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.
    1 point
×
×
  • Create New...