Leaderboard

Alright, thanks! I believe I understand it now. One more thing I thought I should mention, though this is a bit unrelated. I just subscribed to Premium and I noticed something that might explain why I might have been confused about Sensitivity Matching about a year ago when I asked a question on this forum about the topic: When you set the Conversion Method to 360 Distance, and you select All under the Aim dropdown, what the calculator does is that it attempts to match all scopes and fixed-FOV aiming methods in the game to the same cm/360 distance. I would personally never use 360 Distance-based matchings because they can lead to extremely fast Tracking Speeds and significantly high Pixel Ratio values on higher scopes. For reference, before I subscribed to Premium, I only had access to the figures for the individual scopes and aiming methods, at the same in-game sensitivity value, rather than trying to match every aiming method to the same cm/360 value. The reason why I use the same sensitivity value for every aiming method and scope in PUBG is, while PUBG changes the sensitivity (cm/360) in line with the FOV of the aiming method of choice, it does not change the Tracking Speed of your mouse. In fact, Call of Duty: Warzone does the opposite by refusing to change the hip-fire sensitivity (cm/360) when you change your FOV, but it changes your Tracking Speed behind the scenes. I personally believe that keeping your Tracking Speed consistent allows for maximum consistency and I have observed this personally in my years of gaming experience. With that being said, when I am hip firing in PUBG, my cm/360 is 21.78; when I am ADSing with an AR, my cm/360 is 28.00, and when I am using the highest-powered scope (15x), my cm/360 is 294.05. Regardless of how I am aiming, my Tracking Speed remains constant.

Dead Island 2 is added. Aim sensitivity coming soon!

Actually most scopes are like this, the game is calculating the sensitivity scaling based on the FOV you see around the scope, not the FOV in the scope. So technically all scopes needs an update to reflect this.