DPI Wizard

Updated for Bloodharvest!

Aimtastic is added!

Another aim trainer just added!

If you can match the FOV, it doesn't matter which conversion method you use as they all will give you the same result. Matching FOV is the best way to keep a consistent sensitivity. When FOV can't be matched use Viewspeed indeed. For Zoom remember to set Sensitivity 2 to your cg_zoomfov value, and enter the regular FOV into the FOV field.

If you select the same FOV Type for Quake Live as Overwatch uses (Hdeg Res) and enter the value from Overwatch (100), the output will show you the FOV you need to configure in Quake Live to get the exact same FOV (set cg_fov "83.58")

Use 360 distance and match the FOV's so the sensitivity and FOV will be the same.

FOV calculations for Fortnite are now updated to correctly account for FOV's wider than 16:9.

Correct if you prefer Viewspeed 2. 360 distance (which will result in the same sensitivity as the input) might be more natural though since the horizontal FOV is the same and the image is stretched.

This is how it is supposed to work. Viewspeed and monitor distance calculate the sensitivity using the FOV of the games. So if the FOV is different the 360 (hence also the 180) will be different.

Quake Champions (and Fortnite) updated with correct FOV scaling for hipfire and aims!

More and more games are doing this, basically what should be a Hdeg 16:9 option in the calculator, where the FOVis locked to 16:9 and any other FOV is added or subtracted to this. Issue is that games do this inconsistently like PUBG where the FOV is a real mess. I'll take a closed look at Quake Champions tomorrow!

What is your FOV in BF1?

1 is Affected and 0 is Independent ADS Field of View

Preferably on, but the settings depend on what you have in PUBG.

Snug as a Bug on a Drug!

The FOV type will automatically change to the type the game you select uses. This means that the value of i.e. 60 will result in a different actual FOV for games that use vertical degrees compared to ones that use horizontal degrees. The FOV type itself does not affect the sensitivity, but if you want the same actual FOV in different games you need to pay attention to this.

Yeah, a side note saying 0% is legacy would suffice indeed.

Correct!

Can't find anything changed, be sure to set the correct FOV and do the sensitivity in the config file as the sliders are inaccurate

Click the sensitivity value and enter the exact sensitivity It supports the same decimals as the config file so there's no need to edit the file.

Probably not, all Assassins's Creed games have been console ports with terrible mouse input (acceleration, packet loss etc). I haven't tested Origins yet, but I suspect it might be the same. If it isn't though it can be added