DPI Wizard

Radical Heights is in!

It's not an error, but down to what the calculator is matching. For Drimzi's examples the first two calculations are matching 4.2203 cm for 56.25% MM, while the last one is matching 4.2204 cm. @jabbothehut can you post screenshots of your conversions?

Done!

Check again now

Added! It has some acceleration though.

Note that this game has acceleration issues.

Yet another battle royale game is added.

Gave this another try now, but there's too much acceleration / packet drops to be analyzed unfortunately.

Added it now.

The zoom in Islands of Nyne uses two values to calculate the sensitivity; ADS and the scope power (like 1.5X etc). You need to enter your ADS value for the multiplier to be calculated, using the default value should work fine.

It's back now, sorry!

Not knowing how your measure, I assume you are looking at the monitor when measuring. There is no way 5 different mice are measuring even close to each other. Based on measurements of several high profile mice with a 0.005 inch accurate device this is all but impossible. Maybe the instructions need an update, but the goal of the DPI Analyzer is not to hit 0% deviation. The goal is to move your mouse a set distance without looking at the analyzer, then look at the result. I suspect a lot of users are looking at the deviation and aiming for 0%, not caring about the actual distance moved (which is the most important part). Small adjustments make a big impact here. If you set i.e. 5 inches with 400 DPI, you need to click and hold the red cross hair, look at your mouse pad (where your presumably have a 5 inch target mapped out), move the mouse the 5 inches indicated on the mouse pad and release. THEN look at the result. If you do even small adjustments with your wrist trying to match 0%, the result will be invalid.

It's now back for any conversion that does not include a 2d portion (like Windows or League of Legends)!

I plan to add a auto-generated Logitech LUA script you can download for each calculation to confirm they are correct. Makes it a lot easier to verify the calculations and to pinpoint if an error is in the calculator or locally on the users computer.

If you mean mathematically, they are first converted to vertical degrees then to horizontal degrees based on either the entered resolution or a hard-coded 4:3 ratio.

Not that I can measure, turning X amount of counts is exactly the same between the two.

Just verified, no acceleration in BR regardless of the bDisableMouseAcceleration settings. Save the World still has issues though.

It's already in there, but it's stylized theHunter which makes it kinda hard to search for. I'll change the name!

Discrepancy for Viewspeed was removed in the last update because it didn't work correctly with 2D conversions. It shouldn't have been removed for 3D games though, so it will be back in the next update!

Correct, fixed!