DPI Wizard

There is a sensitivity where the pixel movement exactly matches the counts from the mouse, as you can see here from Battlefield 3. I've tried to make a universal conversion for this, but unfortunately this seems very hard, as games scale vastly differently. So you cannot simply take this sensitivity from BF3 and convert it to another game and get a pixel-perfect movement. Although it probably will be close.

Having raw mouse input turned on is the only thing you can do. The game must process the input no matter what, since it's based on degrees of movement, rather than pixels like in Windows.

Rinput is not my program, I have nothing to do with it. I just tested it But in CS:GO, the mouse does not work if you are using Rinput and have raw mouse input turned on, maybe it's the same problem with Quake Live. If it's already off, then I don't know.

Thanks for the heads-up! Will update it as soon as I am done with the new version of the calculator (hopefully before 2016!).

This is correct, but the ratio calculation is wrong. I'm soon done with the new update so everything will be right

Like this

You need to enter your current sensitivity setting for the calculation for work. It calculates the multiplier.

Ghost in the Shell is already added Verdun I've been working on earlier, but not done yet. Will be added.

What DPI are you using?

This might seem a little counterintuitive at first, but the reason is that the Desktop conversion matches your FOV to the desktop. So if you have different FOV, you will get different sensitivity. If you set the BF4 fov to the same as CS:GO, you will get the same 360 distance Desktop works by making the distance your crosshair have to move to a certain object on screen in the game, to the same distance your cursor have to move to the same point on the screen in Windows.

If you don't use the "Simple" aims, you need to fill in your current sensitivity as well. Are you doing that? Anyways, I'm almost done with an update to support all variables of Rainbow Six Siege, as it has no less than four for ADS.

Actually no, sensitivity is based on degrees of movement, not pixels

I didn't realize the sensor could fluctuate so much with the DPI. They are usually off compared to the configured DPI, but this has been a flat percentage regardless of DPI on the mice I've tested. Thanks for the heads up

That would be an entirely new calculation, I'll see if I can get around to do it.

I think this is the case, however I haven't seen any issues myself, going as high as 8200 DPI with 1000 Hz. What polling rate are you using? Maybe try going to 125 Hz if you haven't already, and see if the results are the same.

You should be able to keep dragging the cursor beyond the edge of the screen with the analyzer, it might depend on your browser though. EDIT: I might need to update something to make that work again actually...

I see, thanks for the video. Could you try a couple of things; For this, find the movement you need to do a 360 with both 400DPI/sens 4 and 1600 DPI/sens 1. Now with 400 DPI and sens 1, check that you need to lift and swipe 4 times to get a perfect 360, and with 1600 DPI and sens 4 see that you do exactly 4 360's with one swipe. Also, have your tried the DPI Analyzer at both 400 and 1600 DPI and checked if the real DPI discrepancy is the same? There is something going on either between the mouse and the game, or some 3rd party application interfering. Maybe you can try with vsync on?

1600 DPI + 1 in-game sensitivity and 400 DPI + 4 in-game sensitivity is exactly the same, just tested to verify nothing has changed. Tested with both scripting and physically moving the mouse. The math for Source games is well known, Counts/360 = 360/(SENSITIVITY*0.022). 1 = 16363.64 counts/360 4 = 4090.91 counts/360 If you are using Logitech, you can easily verify this by running these script (macro assigned to G1 on M1 on the keyboard), make sure raw input is on: For sensitivity 1, moving 16362 counts (shortened a little over 1 count to make the macro run faster) if (event == "G_PRESSED" and arg == 1) and GetMKeyState() == 1 then for i = 0, 161 do MoveMouseRelative(101,0) Sleep(5) end end For sensitivity 4, moving 4090 counts (shortened a little under 1 count to make the macro run faster): if (event == "G_PRESSED" and arg == 1) and GetMKeyState() == 1 then for i = 0, 408 do MoveMouseRelative(10,0) Sleep(5) end end Are you sure you have disabled acceleration? How much off are your measurements?

A few games uses radians instead of degrees, so you can easily convert between the two using the calculator.

I'm working on an update to the 4.0 alpha calculator now to support three variables, so the XFactorAiming can be accurately calculated.

Do you have the game through Steam?

It only matters if you have different DPI in Windows and in the game

Correct!

Squad and Ghost in the Shell added, enjoy

Added with both hipfire and ADS calculations. View full update