DPI Wizard

In-game and config file sensitivity added. View full update

Added. View full update

Strange, I'm getting 21.7 here. The game uses a standard Unreal Engine 3 sensitivity with the FOV directly affecting it. It does have issues with packet loss though, so it might depend on how you measure. This is extremely obvious if you set the sensitivity to 1, scope sensitivity to -10, go intro training with Strix and zoom in. Move the mouse slowly, and the cross hair doesn't move at all!

Added the Steam version of TERA.

Verified that the calculations are correct now. Here's a script you can use in the Logitech Gaming Software to verify the calculation for the config file sensitivity (0.019936): function OnEvent(event, arg) if (event == "G_PRESSED" and arg == 1) and GetMKeyState() == 1 then for i = 0, 62 do MoveMouseRelative(100,0) Sleep(10) end end end This will bind the script to G1 on your keyboard. Tell me if you are not sure how to add scripts This script moves the mouse 6300 counts, so it will move almost 1 count too far compared to the calculation (6299.3). But it's a lot more efficient to move this way, and it's close enough to verify. 6300 counts / 400 DPI * 2.54 (cm in inches) = 40.005 cm You can use this test in basically any game, but note that some games do not like scripts like this. Some will drop packets and some will accelerate the movement. The best way to know it's working is if you can execute it several times and the cross hair ends up at the same spot. If it varies, the game has issues.

Updated! Scopes and decimals added. Also removed the console option as it does not save the values you enter.

Paladins updated. Regular sens is the same, added scopes. Also removed the console option as it does not save the values you enter.

There's a couple of videos on the front page covering the basics. But what method you use to convert is most important (360 distance, monitor distance or viewspeed). Try the Simple Mode if you haven't already, it has some quite universal settings pre-selected to make it easier.

What do you mean is wrong here? All these calculations are correct.

This is added now. It's same as the first Vermintide btw.

Downloading these now!

Select In-game location, Battle Royale and the different aims, and the output will show you the Actual FOV

Ok, I'll verify it a bit later today and give you a script so you can double-check it.

What values are you using? Post a screenshot of the calculator. Also, do you have a Logitech G keyboard or mouse? If so I can give you a script to verify.

This is config file sensitivity, you are probably referring to in-game sensitivity when you say 20 and 30.

Will check it tomorrow.

Will update this tomorrow.

I have all the data and the formula for this, but the problem is that the calculator needs the code updated to support it. Currently it only supports multipliers for 2d conversion. It has high priority to get it integrated.

Ok, this is the same as Monitor Distance 0%, so that will probably work best for you.

What is your setting for zoom in OW?

ADS: fov_cs_debug 55.41 2X: fov_cs_debug 34.07 4X: fov_cs_debug 15.07 8X: fov_cs_debug 8.28 15X: fov_cs_debug 5

Free shooter just in! View full update

Mods for Doom added.