DPI Wizard

Note that the sensitivity slider is not accurate and the zoom sensitivity has a low range.

Done

Updated.

Yes. As I said above, to make the calculations correct for your entire monitor. For example if you convert using MDH 75% you want this: Not this:

This would be correct for stretch. This is all covered in the instructions btw, under resolution.

If you play all your games with black bar at the same aspect ratio you don't need to account for this. However if you play some with black bars and others in the full aspect ratio of the monitor you need to account for the black bars in the calculation. For instance converting MDH 100% from full aspect ratio to black bars. If you want to keep a consistent movement on the monitor you would not convert the movement to edge of the full aspect ratio to the movement to the edge of the black bar (where the image ends). You still want to convert the movement to the edge of the monitor, which means accounting for the black bars. When stretching the horizontal FOV takes up the entire monitor, so the calculations will be correct although vertical sensitivity will be different. As an example, CSGO with black bars should use the monitor resolution because the only thing that changes is that the game replaces some of the image on the edges with black bars. Everything basically stays the same, you just see less: However when you stretch you have an FOV of 90 covering the whole monitor, so you need to enter the resolution you play with, and calculate a new sensitivity (if not using 360 distance, which will stay the same regardless):

What's the issue? screenshot?

ADS sensitivity = XFactorAiming*AimDownSightsMouse. Neither affects hipfire, and the only practical difference between the values is that xfactor has a higher accuracy due to the decimal support.

This game can't be added due to how the sensitivity works with the mech.

Unfortunately this game can't be added due to how the sensitivity works with the mech.

Updated R6 calculations now to do all scopes simultaneously and support for in-game ADS when selecting config file. The Xfactor will not be calculated as it isn't necessary. You can use basically any value that doesn't throw the ADS sensitivity out of range.

EU. No issues with 1000hz polling rate with it on.

Sure, it just switches what value is calculated. I think I'll also mash all ads/scope calculations into one so it's quicker to do.

No actual changes in the sensitivity in the game other than it being consistent and easier to measure now. The old one is probably only by a few counts so it's hardly even measurable, but now I should be able to get it perfect. I'll check the polling rate also.

I'm still having the issue as shown in the before video. Stutters and is really inconsistent. I've tried disabling origin in the game and enabling Direct 3D11 without any effect. Maybe the patch is delayed here, I'll check again tomorrow!

Fixed the FOV now as it Hdeg 16:9 and not Hdeg Res. Sensitivity also need a slight update now that it works much better than at release.

This is not an issue with going from 1080p to 1440p, but going from 16:9 to 21:9. When you match using MDV 0% the sensitivity will be the same since the vertical FOV is the same on both monitors. However when you use MDH 0% the sensitivity will be different because your horizontal FOV is much wider.

There is no best way, everyone is different have have different preferences. If there was just one way the calculator would have been a lot simpler You should try both, one of them will probably feel wrong to you. So stick with the other one.

Done

Config file seem to not work properly indeed, so I removed it for now.

It's slow when converting from high FOV to low FOV like from hipfire to scope. But for hipfire to hipfire in your case you're going from low FOV (90) to high FOV (111.31), then it will be opposite.

This is correct. You will get a sensitivity that is not consistent with anything doing this, doing one or the other is better for consistency.

Just select Hdeg 16:9 and enter 90 for Halo as well, then see the output for the config FOV.

You can see the matching method in the conversion setup. Win/2D is the one used for Windows. The regedit should be applied instantly without need for reboot.