DPI Wizard

None of the games here are tested on consoles, only PC. Mouse support on consoles tend to be poorly implemented and riddled with issues. If you're lucky the sensitivity is the same as on PC, but that's probably the exception.

Are you not able to select the ADS option?

It means you probably have to go lower, like 200. The calculator should tell you if the calculation is out of range. If so just try with a lower DPI for this game.

Not much unfortunately.

Updated it now, Y is locked to a different axis speed than X and is unaffected by prescale.

This game seems dead, let me know if it gets revived!

Postal 2 is in!

Use the config file sensitivity for best accuracy, but note that FOV must be set in-game.

This game has the same issue as so many other RE games, the mouse emulates an analog stick.

The mouse emulates analog stick movement in this game so it cannot be added.

The calculator supports the in-game value as well, and treats it like a multiplier. But the accuracy is pretty bad, so the config file is definitely better. Use 6 decimals for the config file. It might be changed a little bit by the game, but it's the most accurate you can be.

For the DPI the calculator already does this. Like in this example: So using the suggested 700 DPI solves the range issue in this case: This function does not work in all cases however, but it usually does.

Finally got the TS-1 Horizon, it is added

The result is the same for that specific aim, your coefficient should match your scope scaling preference. 1.6 is MDH 100% for your resolution, but that was just an example.

360 distance for hipfire is what most expect and are used to. For Windows to game 0% tend to be fast for most. Both based on a poll and analyzing data. But there's no way of getting easy mode to suite everyone, then it would be too complicated which would defeat the purpose. There's a ton of variables, and everyone have their own preferences and opinions.

Do you have ADS Field of View set to affected?

DPI actually doesn't matter for the conversion as long as it's the same both in and out, but it's important for the distance calculation.

Updated the post, attached wrong image

Like this should work then: You should pick a coefficient that matches your scope preference. Here I just did MDH 100% as an example.

That depends on what you mean by exact same sensitivity. Since the FOV is different you can only match one aspect of the sensitivity. That being either 360 distance, tracking speed (MDH 0%) or flick distance (MDH xx%).

The math is more complicated than that. 50% MDH is not the same as half-way between 0 and 100 in terms of FOV, it's quite a bit more. Here's what it actually looks like for a FOV of 120: ' Also how the game scales sensitivity to FOV matters.

This is an issue with some games on some system. Not sure what causes it, but setting the file to read-only does work in some cases.

Also verified Mount & Blade: Warband now, it is spot on in 360 distance which is what you are matching. Note that 3rd person games can feel slower due to the view, but if you measure 360 distance it should be exactly the same.