Leaderboard

This is due to the difference in the FOV of your source. A monitor distance based on say 55 vdeg will be different than one based on 120 hdeg. For this reason you should stick to one source for all your conversions. Ideally you should match the hipfire FOV of all your games, but that's not possible as a lot of games have locked FOV. You would want a scope with a FOV of for instance 20 hdeg to feel the same for any game, regardless of what the hipfire FOV is, that's why you should use the same source. Note that if you use monitor distance for all conversions (hipfire, ads, scope) then it doesn't matter what your source is as long as it is derived from the same conversion (although rounding and lack of decimals may play a part). The issue only comes when you use 360 distance for hipfire and monitor distance for ads and scope.

It does have these issues, I checked it three years ago and deemed it not worth adding. Checked it again now, and it's unfortunately the same story. It's actually quite stable when testing with scripts, but any variation in count size or frequency changes sensitivity quite a lot. This will probably translate to different sensitivity for people depending on their DPI, preferred sensitivity and how fast they move their mouse. In other words to many variables to manage, and the variation is too big.

Name: Sanctum and Sanctum 2 Release dates: 16 April 2011, 16 May 2013 Availability: Purchase Older games but they still get featured at LANs I attend. Would be great if you could help out with them, thanks