DPI Wizard

The settings are correct, but you need to set the sensitivity in the config file.

Added hipfire and ADS sensitivity, scope coming soon!

Added now!

No numerical value to the sensitivity in this game, check the notes for instructions.

No, how it works is quite complex, but it works as expected all things considered.

I'm guessing that's the datamined value? The data and reality doesn't add up in this game I did a few more tests and adjusted it by 0.01 degrees, measured both 360 and FOV within 1 count of the calculation now. If 41 is used in the calculation the 360 distance will be off by about 6%.

Updated the game now, so the FOV calculations are pretty much 100% correct, scale correctly with aspect ratio and will correctly max out at 113.69. So to i.e. find the correct FOV to match CSGO, go up/down on the entered FOV until the Actual FOV matches.

It's basically the same, just round anything below x.49 down and anything over x.50 up.

Do you mean the decimals? It's on the PTR and coming the the live version soon.

Been waiting for this for a long time, hope it's actually released tomorrow

The 360 distance is always the same, and the FOV barely changes if it changes at all. The "problem" is that the camera moves very close/far away from the beats and pivots with the pivot point behind or in front. This makes the FOV feel different for everything right in front of you. I can perhaps make an option where it scales to the apparent FOV of the beats.

I can do thorough analysis of the FOV and see if there's any chance of adding a modifier to the FOV calculation so it is correct in the calculations.

I'll take a look at it a bit later today.

Yes, the FOV is off by 3.2-1% (always too low) and maxes out at 113.63.

Since it doesn't have a numerical value attached to the slider it hasn't been added. But it is possible to adjust it accurately using the arrow keys so I'll see if I can add it using the clicks as the value. It will be the Full Clip Edition, not sure if it differs anything from the original release.

Yes, BO3 is 0%.

Ok, how are you changing FOV? The calculations are done for the default 3rd person view:

This looks correct. There must be something else affecting the sensitivity, I'll play around with the settings and see if I can replicate the issue. How far away from a 360 are you with the whole mousepad, and how large is the mousepad?

Just checked the game now, and calculations should be correct. How are you setting the sensitivity?

Aspect Ratio, the proportional relationship between your monitor and/or resolutions width and height. Typically 16:9 (1920x1080) for new monitors.

I feel the exact same way. My goal is to add something like one option to compensate for AR and one for size that you can turn on or off. Both off is like the calculator is today, with the slight drawback that say converting from 4:3 to 16:9 using monitor distance 100% means the edge of 4:3 will be matched to the edge of 16:9. On the plus side this means that converting using stretched resolutions works fine. Compensating for AR means 100% on 4:3 will match 75% on 16:9. Adjusting for size will be based on PPI.

I'm honestly not sure. If it's a question about how much of your vision the monitor takes up, the distance to your monitor should be considered as well. But personally I don't feel the sensitivity being wrong if I move 50 cm back or forth, which has a lot more impact on the apparent size than a few inches of increased monitor size. I'll add the function to the next release though (not with distance to the monitor, but with monitor size), but it's probably not suitable for everyone.

Correct, unless you also want to compensate for the size change in sensitivity. By this I mean if you overlay the old size over the new, the sensitivity in the old size portion stays the same, and if the new monitor is bigger it will require more movement to reach the edge.