shaeofwar

That is close to what I was thinking about but it doesn't work if the game I'm converting to doesn't have the sensitivity range to support the dpi I'm converting from. I just get no result saying the converted sensitivity is too low or too high. I was thinking I could choose the in game sensitivity on the game I'm converting to and the calculator gives me a new DPI to match the game I'm converting from. Or maybe if the sensitivity is outside the range it gives the max or min sensitivity and the DPI to match.

A lot of games have terrible sensitivity sliders and options. Mouse software allows for and remembers custom dpi settings for games. It would be easier for and more precise for me to convert by dpi instead of sensitivity in some games. Would it be possible to have this feature? or does it already exist?

Why does this calculation not give me a result? https://www.mouse-sensitivity.com/?share=22c20d7bddb5a69f6f13cbbdf70fc6b1

The 0.2 option will allow you to change your sensitivity by smaller increments if you plan on ever changing your sensitivity but as far as converting your sensitivity if they have the exact same 360 distance then there is no increase in accuracy.

If you have the option to set both horizontal and vertical scales to 0.1 or 0.2 while calculating the hipfire sensitivity that would give 5x or 10x times more precision for hipfire sensitivity.

If you set your halo fov to 110 and Apex fov to 1.5. You can match your halo hipfire sens to match apex 1x perfectly. As in they will have same fov and 360 distance. Like this. https://www.mouse-sensitivity.com/?share=b28e63ebafe242679acacacefd79de6a Also every zoom level will be consistent to 0% mm

The 1x sights on the two games have different fovs. What is your preferred conversion method between different fovs?

Every time I use calculator I have to change from inches to centimetres. It's an option that rarely changes between between calculations. It's kind of a nuisance having to change it.

You are using monitor distance vertical and monitor distance horizontal both in the calculator. Use one or the other or you will get incorrect results.

I was thinking hardware and game Independent value like "angle turned * zoom / mouse movement distance " type of value. So pixels/count * dpi is the equivalent of above as long I don't change screen resolution?

I was thinking of 0%mm and how if you match your sensitivities by it, that your tracking speed is the same across all zoom levels. I was wondering what the value of that speed is. This value should be the same across games if I matched them by 0mm I also noticed that if I use a high FOV and match by 360 degrees and then match ads and zoom by 0mm, my sensitivity is too low when zoomed. So that means there is a lower limit to that tracking speed. I would find it useful to know what that tracking speed value is so I could l know when it goes outside an acceptable range for me. Could a game independent value like this be added to the calculator?