Leaderboard

@DPI Wizard I just wanted to say a big thanks for all the work you put into finding the sensitivity settings in this game. You're seriously the real MVP! Your attention to detail and determination to get it right has made a huge difference for so many players, including me. Thanks for being so patient and sticking with it, even when it was a long and tough journey. Your efforts are not going unnoticed and you're making a big impact on the gaming community. Thanks for all you do, You're a legend and you deserve to know how appreciated you are. Cheers!

Finally done, this took forever! I've added all scopes in the game (I think), very few actually group together so there's no less than 41 different aims to choose from. I couldn't find any weapon that have a different sensitivity and FOV than the "ADS - No attachment" entry, but I only tried a few weapons in each class. Let me know exactly which weapon doesn't line up with the calculations if you find one. Also, now that pretty much every scope is analyzed, we can graph the relation between actual scope power (not the stated in-game power) and 360 distance. For most games this graph is either a line or a nice curve. For Tarkov on the other hand, we got this beauty:

Usually the recommended way to match ADS and scopes is using a different method than 360 distance. All the other methods are matching the sensitivity based on what you can see on you monitor, for instance MDV 0% will match the tracking speed between all aims. MDH 100% will match the flick distance to aim at something at the edge of your screen. However, for low powered ADS aims it some prefer to use 360 distance as you in many cases run around while ADS'ing, and by matching 360 distance you have the same movement when turning around corners etc.

Added! Note that you have to use a low polling rate to disable smoothing.

You need to set the ADS conversion to 360 distance if this is what you want to match:

Thanks for the offer, but I got everything working in the single player mod now, and have finally found a workflow that is consistent when analyzing the aims. I did all scopes yesterday, and will try to do the rest today/tomorrow and update the calculator.

When you convert between different monitor sizes, the 360 distance is not what is matched. Say you convert from a 17 inch to a 25 inch monitor using MDH 100%; on the 17 inch your would for instance have to move your mouse 5.2142 cm to move the crosshair 18.8173 cm to the edge of the monitor. So this is matched to the 25 inch so you still have to move your mouse 5.2142 cm to move the crosshair 18.8173 cm, but since the monitor is larger this is no longer to the edge, resulting in a different 360 distance. There is a bug with the monitor size conversion however, as it will use horizontal even though vertical is selected. This is being fixed in the next update.

Note that there's a bug in the beta where scopes are only affected by the "high" setting, and not the appropriate scope power setting.