DPI Wizard

Checked it now, and it doesn't reset here. It might happen in some cases though, so if it does just be sure to set everything before setting the sensitivity.

Don't you have a calculation box between input and game info?

Nice, added now. Note that the game only reads the first two decimals, and going below 1 causes a lot of reports from the mouse being lost so I've set the minimum to 1.

Adding a game like this doesn't really work since you only move the mouse a little bit, then the max rotation speed of the starship dictates your movement.

This isn't software that does anything to your game, it's a calculator to match your sensitivity to other games and some tips and tricks to get rid of sensitivity issues if possible. For Horizon Zero Dawn there will be issues no matter what you do though, the game devs need to properly fix the input.

Do note btw, that copying sensitivity into Krunker doesn't work properly, it will be overwritten even though the numbers show up correctly. I don't know if this is the issue, but if you did copy it, try to enter it manually instead. And also note that Krunker will throw a .1 shortly after you input 0, so if you don't pay attention it will be incorrect when manually entering the sensitivity too.

I don't know what setting you have potentially messed up, but the Valorant and Krunker sensitivity in that output is exactly the same:

If your Windows Display scale is 100% and all other parameters are correct just setting the X and Y sensitivity should be enough. It's very important that the Windows Display scale is actually set to 100% in Windows though: Can you link your whole conversion with the purple share button?

Can you be more specific? Krunker should be 100% accurate if converted correctly.

Added.

Hi! Added Apex Aim Trainer now. It's slightly different than Apex Legends since it doesn't have the same rounding bug

While intended to use the same settings as Apex Legends, the aim sensitivity is slightly different due to a rounding bug in Apex Legends. View full update

It's only the same if you also switch FOV Measurement from Vertical 1:1 to Apex/Quake/Src/4:3 in the game.

Seem like it's Hdeg Res until it's above 16:9, then it switches to Hdeg 16:9. I'll check it and update. Edit: Updated!

For Vertical 1:1 yes

The only difference here is how the game measures FOV and what value you have to enter as your config FOV. The end result of the two settings (Apex/Quake/Src/4:3 at 76.329602 and Vertical 1:1 at 61.034115) is exactly the same as you can see in the Actual HFOV/VFOV in the output.

Actually you have entered the values in the wrong places. We haven't got in-game translations everywhere yet, so I realize it can be a bit confusing when not using English in-game. We are working on this though! Hope this helps:

Added!

Added the first one now, but unless the second one uses Unreal Engine 3 they're probably not the same.

Use the config file for best accuracy. View full update

No, you can still do the same ting, just pay attention to the config FOV in the output: https://www.mouse-sensitivity.com/?share=b50cd510b54b071a6d79042b1af2419c If you do change from 102 to 104 in-game that also works, but this is not hdeg 16:9: https://www.mouse-sensitivity.com/?share=d5e4a3067171689432799290a9847eee