Struth

I might not be interpreting negative monitor match correctly, but it looks like ironsight isn't being appropriately affected by changes to the %. 0% MM https://gyazo.com/7aa496aac6dff5757f301067ba84c8a7 - 100% MM https://gyazo.com/d93fc7241eceb38ba049e77ad2a64122 The 2x and 4x are significantly changed, but the ironsight only changes by the slightest amount. For context I was playing Sector's Edge before the scope conversions were out so I had to experiment to find which performed best, and now that we have the conversions I wanted to check if the settings I chose aligned with a particular %MM.

That's exactly what I was looking for, thanks!

Thanks, any idea what sequence i'd go through to get the hipfire sens (0% monitor match) from that old 50 fov to 103? Problem I have is that 0 scope multiplier isn't 0% monitor match. The old sens was 3 in-game, 800 DPI, 103 FOV, 0 scope multiplier.

Does anyone happen to know what FOV Kinessa's scope used to be before they changed it? Wanting to try a calculation from an old sens I used awhile back.

I'm curious if people think their physicality influences their aim and preferences like sensitivity, mouse weight etc. Height, arm length, gender, hand size, muscle mass, fat %, fast twitch/slow twitch, reaction time are some of the characteristics that come to mind.

Yeah I meant 56.25% thanks for the fast reply

When using the calculator I usually use 56.5% match for the monitor distance. Would I use 156% in Uniform Soldier Aiming?

I've been using the monitor match at 56.25% on a 16:9 monitor which has worked out great for most games but i'm running into an issue on 3rd person games like Fortnite and Realm Royale which have a low FOV (80 and 90). My 'best' sensitivity is from Paladins at 115 FOV which is 54.28cm/360. When converting this to Realm Royale with the monitor match method my suggested value is 77.06cm/360. This is prohibitively low for me and feels terribly slow. Any advice on where to go from here, what to try next?