DPI Wizard

I'm assuming it's black bars and 1920x1080 in the middle? If this is the case, you need to do a little trick if you want to convert to other games that use the whole monitor. The calculator doesn't know that you have 1080p in the middle of a 32:9 monitor, so to make it work correctly switch FOV Type to Vdeg while you have 1920x1080 as the resolution (it will then show 70.5328), then change the resolution to 3840x1080. You will see an "Actual HFOV" in the calculations that are wider than your FOV is in reality, but this is so the calculator also includes the black bars in the calculation.

Added both this and Extinction!

Dino and hipfire sensitivity added.

Done!

This game has some acceleration and smoothing issues resulting in slightly varying sensitivity.

Only in-game sensitivity added, changing the sensitivity in the config file does not work.

GTFO is added!

This game lacks a numerical sensitivity value. The sensitivity can only be set with an unnumbered slider.

This game lacks a sensitivity option.

Config file and in-game sensitivity added.

Is this an issue with other games? Have you tried to reload the page?

Resolution doesn't matter per se, but aspect ratio does. If you use a 16:9 resolution the calculator will assume your entire monitor is covered by an FOV of 106.26. This is not the case if you stretch 4:3, your entire FOV is then 90 which is why you must enter a 4:3 resolution. For 360 match it's doesn't matter, but if you match ADS or scope to your stretched resolution using monitor distance it will make a difference.

Gradual will have a transition period where your sensitivity and FOV changes. With instant it happens instantly so I would recommend that.

In R6 specifically ADS and scopes works very different than in any other game, so how you convert from that game depends very much on your settings and preferred scope. CSGO is more straight forwards. Correct, use relative 0%. Legacy is broken in that it uses the coefficient when it shouldn't.

Yes, since legacy doesn't work like intended it's better to just use relative with 0% so you are sure what is applied.

Aye, updated.

I guess the game was made for 4:3 and they didn't bother doing the proper math to 16:9.

For this you need to enter the 4:3 resolution (1280x960). This is so the the FOV calculation is correct as the calculator assumes the resolution covers the whole monitor.

Those two games are very different, and it depends on you setting in them. Legacy is broken, it applies the coefficient as if it's set to relative.

That's under the UnrealEngine folder, not Unreal Engine. The space makes a big difference