Leaderboard

Viewspeed v2 DNAMTE has come up with another solution for converting sensitivity to different field of views. This time it is independent of the aspect ratio, which is a flaw with viewspeed v1. The aim of this solution is to make the different field of views behave the same visually when moving the mouse, solving any perceptual issues such as feeling like it is slowing down or speeding up. This makes this method especially useful for zoom/ads sensitivities. The sensitivity scaling is done using two ratios, the circle ratio and the chord ratio. DNAMTE is unsure on how to do the math for it, so I will do it. In the picture above, he did 90 degrees and 45 degrees for the angle of view, and found a chord ratio of 2.41 and a circle ratio of 1.3. circle ratio / chord ratio The chord ratio can be found using: tan(y * pi/360) / tan(x * pi/360) Where the variables are the degrees. If we substitute x for 45, and y for 90, we end up with a ratio of 2.41 as shown in the image above. Scaling the sensitivity by the chord ratio alone would be equal to scaling the sensitivity by the zoom amount. The circle ratio can be found using: cos(x * pi/360) / cos(y * pi/360) If we substitute x for 45, and y for 90, we end up with a ratio of 1.3 as shown in the image above. Put these two together, and you simply get the sin ratio. (cos(x * pi/360) / cos(y * pi/360)) / (tan(y * pi/360) / tan(x * pi/360)) = sin(x * pi/360) / sin(y * pi/360) When substituting the variables with the angles, you want to use the vertical / horizontal angle for the 1:1 aspect ratio. With this additional option of converting sensitivities, you end up with the options of converting using the tan ratio (mm 0%), sin ratio (viewspeed v2), or matching a screen-space distance using monitor distance match. Recommendations: Use tan ratio (0%) or 360 distance match for converting hipfire. Use tan ratio (0%) or sin ratio (viewspeed) for converting zoom/ads.

I used my strategy in the previous post and was able to snag an 8x scope to take some screenshots and mouse data. I derped a little bit and did it versus third person instead of first person, but I suppose it's still fine. Here are the images for comparison if anyone wants to do any calculations with them. I tried but got too confused by the trigonometry to get much out of them. Third person 8x scoped in 8x scoped in overlayed on third person I also took MouseTester data to get the total x-counts in a 360° rotation. Here are the images of the points I used to start/stop on while collecting MouseTester data: third person, 8x scoped in. For third person, it was a total of 16362 x-counts, which converts to 46.177cm per 360° with my 900DPI. This is very close to the 46.1818cm per 360° from the calculator for my 0.009900 hipfire sensitivity. For 8x scoped in, it was a total of 173621 x-counts, which converts to 489.997cm per 360° with my 900DPI. This is not close to the 540.6461cm per 360° from the calculator for my 0.007732 Scope 8X sensitivity. However, if the calculator treated the Scope 8X sensitivity as having 7.25x magnification, then the calculator would give 489.9608cm per 360°, which is very close to my measured 489.997cm per 360°. So I think we can conclusively state that the 8x scope is indeed 7.25x magnification as reported on PUBG.ME, and we can furthermore anticipate that the 15x scope will be 12x magnification. To demonstrate the difference this makes, the 0.007732 sensitivity I was using for Scope 8x sensitivity should actually be 0.008532 (= 0.007732 * 8 / 7.25) to take the 7.25x magnification into consideration. I was also using 0.007732 for Scope 15X sensitivity, which should actually be 0.009665 (= 0.007732 * 15 / 12) to take the 12x magnification into consideration. The various sensitivities I used for PUBG come from my own method, which I will make a post for soon, but the bottom line is that this effects everyone who used the calculator for deriving Scope 8X and Scope 15X sensitivities. Oh, and somehow I managed to win that game after I collected these screenshots and mouse data even though I was just trying to find an 8x or 15x scope for this test. Just goes to show, man's best laid plans in PUBG

I will re-test everything when the monthly patch is released with an FOV slider next week, some values might have changes since I did the calculations. Also, if anyone have access to a custom server that I can use, it would be extremely helpful. I'll apply as soon as they are open for applications, but who knows if I'll get one. Getting my hands on a 15x scope and having time to analyze accurately it in a real game is not very easy!

This feels much better than any iteration of viewspeed we've had so far.