Leaderboard

No, you don't need to worry about that. Whilst it may appear that is a sound testing methodology (reproducible action / results over multiple runs etc) it is fundamentally testing the wrong thing. I wrote a reply about why it is not correct / useful here: https://www.reddit.com/r/MouseReview/comments/p49dld/gaming_mice_and_sensor_lag_new_testing/h96ctoj/

Sensitivity in this game is currently bugged as it emulates an analog stick, this calculation is just an estimate and will not be 100% accurate. View full update

Sorry this is a little offtopic but I have a couple tips that might be useful: 1) Getting your controller to work on PC 2042 wants to use your first game controller and only that one. Lots of devices have game controller abilities even if they aren't a controller (eg my mouse does) so your controller may not be seen by the game. You can use https://github.com/ViGEm/HidHide to hide all but the one you want to use like so: 2) Getting OBS to capture 2042 with an RTSS overlay: The new version of RTSS will work with BF2042 out-of-the-box, and OBS will capture BF2042 out-of-the-box, but combine all three, and OBS captures a blank screen. You need to edit the bf2042.exe.cfg file (C:\Program Files (x86)\RivaTuner Statistics Server\Profiles\BF2042.exe.cfg) and add these two lines to the hooking section: [Hooking] HookDXGISwapChainPresentVT = 1 HookDXGISwapChainResizeBuffersVT = 1 Enjoy.

Hipfire is added, aims are coming!

Bingo! Didn't see that at first. Here's how you would set up the calculator to convert the settings from ADS to low and ACOG to high (replace DPI and resolution with your own):