DPI Wizard

Update with ADS and 30 mm scope now, will add more as I get them.

I'll update the calculations for what I can get my hand on a bit later today. Hopefully there's a more logical scaling to the aims now.

As long as you don't change resolution, the pixel/count is your tracking speed. As an independent value you could use Windows / Desktop as a source instead of a game, but the drawback of this is that you can't match 360 distance for hipfire.

I don't think it uses any common scaling unfortunately.

Are you entering the correct FOV and made sure smoothing is off?

Other than digging through source code, the only method is by using scripts and math. Quite easy if the game has good mouse registration (i.e. no acceleration or smoothing). The approach is to first measure the 360 distance, then the whole field of view (i.e. moving what's on your left edge to the right edge). Alternatively half the distance (crosshair to edge) and doubling it. So if the 360 distance is 8181 counts and crosshair movement from left to right is 2415 counts, this means your FOV is 2415/8181*360=106.27 degrees. This method have a few caveats though. For 3rd person you need to measure against an object as far away as possible. Skybox if possible (if it's static). In terms of distance, at least 1-2 km (over 1 mile). Also some game have your first person POV slightly in front of the center of rotation, this may throw off any measurements as well.

It's the dealers I had access too, not the flea market. I'll have to play up to level 10 then I guess

That would be amazing! Yes, I've played just enough to access the flea market if I recall correctly.

Great, will check when the patch is done. I don't have access to much in this game yet, but I'll see what I can do!

Then it's tan(fov2/2)/tan(fov1/2)

Nothing to worry about, it happens because of rounding and doesn't cause any practical difference in this case.

Man, they're catching on quick!

Set ADS and scope to MDV 133.3333%.

They are different values, MDV 100% will match the movement from the crosshair to the top of your monitor, MDH 100% will match the movement from the crosshair to the left/right edge. MDH and MDV 0% is the same as long as the aspect ratio is the same.

This is MDV 100%

That's one way of doing at, getting the base calculated and just let the accel do what it does. Raw input off is another thing though, it can just make the input registration unstable.

This is the issue I guess. Unless you have both seta cl_mouseAccel "0" and seta m_filter "0" there will be acceleration, and the problem is that sensitivity can't be calculated with acceleration on. The distance you get will vary depending on how fast you move your mouse and DPI etc.

When you convert from CSGO the FOV is 106.26, but when you convert from Overwatch it is 103. This FOV is the base for all conversions, so you will get a slightly different result for FOV based conversion. This is why you should either stick to one game as source for all conversion, or (if it suits you) also use a FOV based matching method for hipfire (like MDV 0%), then converting back and forth like this will yield the same result except for some rounding errors.

And yes, it is for the zoom sens, if you select "Advanced Plus" mode you will see the discrepancy for each aim

Max discrepancy in your example is 0.0001%, that's basically nothing and only caused by rounding.

For the zoom sens not to be the same value yes

The sensitivity is the same in your example (0.999091). If you're thinking about the ADS/zoom sensitivity these two games use completely different methods for this. Quake uses MDV 0% while Aimgod uses a multiplier.

Not when "All" is selected. All is a way to convert to all aims for the game in a single operation. Select the zoom under aim

Only added aiming sensitivity for ironsight for now. Is there scopes, and if so how do I get them? Random loot?