DPI Wizard

EDIT: I guess this is like games though Microsoft Store, you have absolutely no access to the game files. Unless the config file is located in a location like "My Documents" or %LOCALAPPDATA%, there is no way to feasibly access them.

Isn't UAT just a test client? Or is it a different version?

This game has a very limited sensitivity range, the only thing you can do is to set the DPI to 200 if your mouse supports it.

Hipfire to hipfire from R6 to CSGO using 360 distance and hipfire you can try without premium, so give it a go.

There's no numerical value to the sensitivity or FOV in-game, in any file I could find or in the registry. So this can't be added.

For this you use the Monitor Distance calculations. Which one is best for you is impossible to say, but most favor either MDH 0% (same tracking speed of a moving target) or MDH 100% (same distance to flick to the edge of the monitor). Try them both and see which one feels best.

You can see if the game have sensitivity affected by FOV in the game info It's not that uncommon actually, about 25% of games currently in the calculator are affected by FOV. The sensitivity in BL3 could definitely be better, especially aim sensitivity.

Did you enter your configured FOV for Borderlands? Just checked the calculations and they are spot on. Test with Kovaak's Sensitivity matcher if you have any doubt.

Done!

This Early Access game is added!

With BF1 that must be a hardware/driver issue. Some games do struggle with 1000hz though, it is usually noted in the game notes in the calculator if this is a known issue.

Key is requested, if I get access I'll add it tonight.

Not possible to add, mouse input is terribly optimized.

When you change this multiplier, all Multiplier 2 values will be calculated based on this, so in effect nothing changes as long as everything is within range.

It's probably correct, but if you show me some screenshots of the ones in question I'll answer exactly why it happens

It depends on the conversion method and whether or not the aim you are converting is affected by FOV. It also depends on what sensitivity variable you are adjusting. If it's just a multiplier used in the calculations, the end end result will just adjust itself accordingly.

You don't get a different result, it's exactly the same. Config FOV: 82.18 Actual VFOV: 66.37 Actual HFOV: 98.61 The only difference is that you input the FOV in a different type, which is converted accordingly. The correct option depends on what you want to achieve really. If you want to match the vertical FOV, you select Vdeg and enter 66.37. If you want to match the horizontal FOV you select Hdeg Res (or Hdeg 16:9 if that's your aspect ratio) and enter 98.61. These values are linked through your resolution, and the calculator will automatically convert any entered number into the FOV Type you select so it doesn't mess up your results.

FOV Type is not related to your aspect ratio, it is simply a way to express field of view. Games use different FOV Types, so the calculator will change according to the game you select. This is the value you type into the calculator is correct for the game you have selected. If you want to convert between different FOV Types, you can select the same FOV Type and value, and check the output for the Config FOV to achieve the desired FOV, like in this example: The important part is the the "Actual HFOV" is identical, like it correctly is in your screenshot. Special for Kovaak's is that the "FOV Measurement" selection affect the FOV Type.

Horizontal and vertical sensitivity added.

It says in the aim notes: These calculations are based on the Traveler's Chosen iron sight.

The issue with this is that every game potentially need some input (FOV, special options, multipliers etc), so the whole layout needs a redesign to account for this. It is on the roadmap to allow for this, however no ETA yet.