DPI Wizard

I've updated the vertical now. It's not exactly half, but close. As for the polling rate issues, I can't see any issues here up to 1000 Hz, but this might be affected by hardware or drivers etc.

Correct, for all other weapons except the R.357 the red dot and iron sights are the same.

They have changed the in-game scale indeed, I've updated the calculations now

This is the one that is already added, select any aim that is not hipfire (or use the "All" conversion), and this is the value that is being calculated. Do let me know if something doesn't look right on your end in the calculator though

The in-game and config values are completely different, so this is to be expected. "Mouse aim sensitivity" is already in the calculator. Or have they added more options lately?

The default value of 1 works fine here. Make sure to set everything as calculated or mentioned in the game notes. There's a lot of settings for this game, and just setting one of them different makes the sensitivity wrong. These are the settings: Mouse Sensitivity Horizontal Sensitivity Vertical Sensitivity Monitor Distance Coefficient 1-2X etc Default FOV Scope Magnification Scope Adaptation Sensitivity Transition Mode - ADS Transition ADS Sensitivity Type - Set Sensitivity Per Zoom + MDV ADS Sensitivity Multiplier - 1 ADS Vertical Sensitivity - 1 ADS Horizontal Sensitivity - 1

Here

The sensitivity slider is not accurate, expect some discrepancy. Use the registry for best accuracy. View full update

No, it scales differently. Select the in-game location in the calculator for the proper in-game calculation.

Good you found a fix! Are you talking about the MarkC mousefix? If so it does nothing on newer games, there's only a few 20+ years old games it actually fixes anything for (for these old games it is crucial though). Newer games ignores anything mouse related written in the registry, and reads the data directly from the mouse (for the most part). Other than that, reinstalling Windows can solve a lot of problems built over time that might for some reason impact the sensitivity.

No problem, DM me on Discord

Personally I base all the conversions off of CS2, use 360 distance for hipfire and MDV 0% for ADS and scopes. This doesn't mean it works for everyone though, MDV 0% might feel too slow and 360 distance might feel very different if you can't match the FOV, but for me this works. 360 distance is the most popular for hipfire at least, that's for sure.

Converting between a 3rd person game with a fixed FOV to a 1st person game with adjustable (and usually wider) FOV can be tricky to get right. Not in terms of the math behind it, but because they feel so different due to the perspective. 3rd person tends to give you an impression of the FOV being wider than it is. 360 distance for hipfire might feel more natural, and personally I prefer this.

Thanks for the links! It's not telling you to increase the sensitivity, because the Monitor Distance Coefficient of 1.78 matches the conversion setup of MDH 100%. So when you increase the FOV, the game will take this into account to scale it exactly like the conversion setup. I have not looked at vehicles in this game yet, it's on the todo list

In terms of sensitivity (i.e. 360 distance) these are exactly the same. 1" difference in monitor size shouldn't make any significant difference in feel either, but it might be heavily affected by the refresh rate. Especially in a game like CS2 which actually reaches 360 FPS easily. You could try to lower the refresh rate to 144 Hz on the desktop to see if that makes them feel more similar.

I've added special options for perspective and zoom scaling now. Zoom scaling does not affect first person hipfire though.

Quite a few games does this slight rounding/alteration of the config file values. While annoying, it is completely insignificant as this example only changes your sensitivity by 0.00000156%, which isn't even measurable. Read only might keep the file unaltered, but the game engine will most likely use the altered value anyway.

I haven't checked since they renamed to CS2, but m_pitch didn't work before. You can calculate m_yaw if you select this in the special option: I'll check if m_pitch works now a bit later today!

The hipfire entry had some invalid properties, so it didn't show up. I've fixed this now, thanks for letting me know

I just measured it now to be sure, and it is definitely a 16:9 FOV. Remember that the hipfire sensitivity is affected by the Monitor Distance Coefficient, so make sure these settings are the same in the calculator and in-game.

That should not happen in this game. If it's just slightly different, it's possible that the issue is the DPI settings on the mouse not being consistent, for instance 400 might be 380, 800 might be 815 etc. If the difference is big, it might be tied to polling rate, especially if you're using anything over 1000 Hz.

There's no way of knowing which games actually use the default or common values, so as mentioned, they need to all be analyzed individually.

See the post literally above yours