DPI Wizard

Where the point is depends on several factors like resolution, FOV, 360 distance and game engine. It's hard to say where the benefit of high DPI stops for each scenario, but in my opinion you should have at least pixel accurate sensitivity. By that I mean 1 count from the mouse moves the crosshair 1 pixel. Maybe 10 counts pr pixel is better, but 100 counts is probably overkill.

Do you mean the "Enhanced Mouse Input V2"? Can't be added at the moment, as it is really unstable and inaccurate.

Thanks a lot for the kind words

Some games have issues with 1000Hz, that might have been the problem. But I haven't checked it so not sure.

Updated!

Added! View full update

Battle royale! View full update

Welcome to the Stone Age! View full update

Just added this with calculations for 3rd person and different zoom levels!

Added with both 3rd person and aimed calculations. Action Stations! View full update

If you enter the monitor size, you will see the ratio It will not be the same for other games as it depends on the FOV, as stereo3D points out. I assumed default FOV for H1Z1. Here's what you can do now as a workaround until I get the ratio calculator integrated. By using Windows as the "Convert from" game, you preserve the ratio in the conversion. So first convert from CS:GO go to Windows. With sens 2, 400 DPI and default FOV you will get 350 DPI in Windows. Now this value is rounded to nearest 50, so you will need to adjust it slightly. As you can see here, the ratio for CS:GO is 3.8977. Note that the ratio will change depending on monitor size and FOV even though DPI and sens are the same, and the monitor size needs to be same for both games! Next, select Windows as your "Convert from" game, and adjust the DPI to get it as close to 3.8977 as possible. By selecting CS:GO as the "Convert to" game and entering 400 DPI, you can check that it converts back to sens 2 in CS:GO: Now that you know 318.0118 (in this example) is your ratio, you can use this for any game But a game like The Division has such a narrow sensitivity range that you need to go down to 250 DPI for the conversion to work: It's a little tedious for now, but I'm working on the ratio calculator

The calculation only takes the total 360 distance into consideration. But since the camera pivots, the parallax changes and make it feel different. Not a direct comparison, but consider how much faster it feels to move around with 120 FOV compared to 60. But we can try to match the ratio instead, this way the distance covered by the crosshair is matched instead of the 360 distance. I've done this manually now, but I plan on implementing it as a separate calculation. So for CS:GO with sens 2 and 400 DPI, the corresponding sens in H1Z1 should be 0.09788 with 400 DPI to preserve the ratio. Check if that feels more like CS:GO

This game uses the same sensitivity as the first one, but you can now check the value in the config file (but not set it as it will be overwritten). View full update

Hi! Yes, 1st to 3rd person conversion is a match of the 360 degree turn distance. As you point out, the camera pivots around the character, which makes it feel different. This also makes calculations with FOV (meaning the distance needed to move the mouse for an object to move from far left to far right of the monitor) very hard, since it varies depending on where the object is in relation to you. Does it feel too fast or too slow?

It should be possible, but only for one type of zoom since there is no separate setting. What weapon/zoom would be most desirable?

The thing with FOV and 3rd person views is that... well it varies. Depending on where the object you look at is, the FOV (by that I mean the distance needed to rotate the camera so the object moves from far left to far right compared to the full 360 degree distance) will change. You will not necessarily get a fisheye kind of distortion as in a first person FOV even though it is high. Also remember that the FOV I have listed as default is really just meant for the 2D to 3D conversion to work relatively good. It will never be perfect since the FOV is not constant.

Just added! View full update