DPI Wizard

Filcher and Vein added.

Use the config file for best accuracy. View full update

See the game notes for instructions on how to disable smoothing. View full update

See the game notes for instructions on how to set the sensitivity. View full update

STALCRAFT is updated to the release version for hipfire. Aims coming soon!

That's already what the calculator does, it gives you the sensitivity and multiplier values that are closest to 0% discrepancy within the limits of the game. If you are talking about the multiplier values and a calculation with a lot of decimals so the discrepancy is 0%, that's not done because the game doesn't support it (in this case), so it's sort of useless.

Monitor Distance 0% is a good place to start, note that these kind of 2D to 3D conversions might feel correct depending on your preference.

This is correct, there was a bug in the calculator with different aspect ratios after the game was updated to Overwatch 2. I've fixed this now so everything should be correct.

This is great, while 1000 Hz worked fine here before, 8000 Hz was a complete mess so it's good that they address this. Note that these changes do not affect the calculations, as they reflect the true sensitivity without any of these issues.

No, it's working exactly as intended.

I just checked again to be absolutely sure (I think I have done this previously as well), and it's 100% for sure Hdeg 4:3, not vertical. I know it even says "vertical" in the info section when you set the FOV in-game, but it is wrong. My best theory is that to not "confuse" players with unknown jargon, they just say the FOV is vertical (since the vertical FOV stays the same regardless of aspect ratio) and hope no one notices/cares.

These emulators all have terrible mouse input with smoothing and negative acceleration, so they can't be added.

The bug is definitely still there. I just tested now with your exact settings, this is the 6X scope doing perfect 360's when the mouse_zoomed_sensitivity_scalar is 0.644131: Here the mouse_zoomed_sensitivity_scalar is 0.64 which would be correct if the bug was fixed, but as you can clearly see the 360 is now completely off:

Just select 360 distance for both hipfire, ADS and scope. Note that you probably have to use Relative ADS Mouse Sensitivity and a high coefficient like 5 for the aims to be in range. Also your high power scopes will be insanely sensitivity and likely skip many pixels making aiming very hard.

I don't have any issues here at the moment (Ubi version), but raw input has been bugged in the past so it wouldn't surprise if there's still issues in certain cases.

This is exactly what the monitor distance conversion are for. For any game and any FOV it will keep the relative monitor distance the same.

I think you misunderstood the packet loss issue. It's not packet loss in terms of server latency and packet being lost from the PC to the server. It's packet from the mouse to the game client not being registered, i.e. lost. I just tried making my own server now, and the issue is the same. When I send a packet from the mouse to the game to move X counts, the packet is very often missed so the game doesn't move the camera at all. In practice this will feel like negative acceleration, where the camera moves less than expected.

It should work now, I cleared some broken entries in the database. Your notification counter is reset for now though, but will show up again when you get new ones.

Ok, I'm able to reproduce the error here, so there's nothing wrong with your browser or network etc. I think it's a bug in the framework though, which I won't be able to fix on my own. I'll look more into it.

Added!

See the FOV notes for instructions on how to change FOV. View full update