Leaderboard

A new version was just published that contains two new features: 1. Focal length This is a function available in the Aspect Ratio box of the output game. What this does is calculate the correct resolution you need to set (with black bars) to keep the same focal length based on your FOV. This is useful for games that does not support FOV change. 2. Monitor size conversion When you enter a different monitor size and/or aspect ratio the calculator will now account for this based on your setup. 360 distance will be the same, as it doesn't change based on monitor size or aspect ratio. Monitor Distance Horizontal and Viewspeed Horizontal will take into account the horizontal size of the monitor. Monitor Distance Vertical and Viewspeed Vertical will take into account the vertical size of the monitor. This means that if you go from a 24" to a 27" 16:9 monitor, both horizontal and vertical will give you the same result. However if you go from a 27" 16:9 to a 35" 21:9 the vertical sensitivity will stay about the same, while horizontal will account for the extra width. Please report back if any of these features are acting weird!

I see now, you want to keep the same 360 distance and just change the resolution so it acts like you just put some black tape over the edges. I'll fix!

Valorant is locked to 103 Hdeg Res, so when you add height i just adds more FOV to the height. Same with width, if you go 21:9 your Vfov will be very narrow at 47.36. CSGO is locked to 90 in Hdeg 4:3, so it will keep the vertical FOV the same regardless (unless you go below 4:3).

Fixed!

Yes, it rounds up to the nearest 50 if I remember correctly.

Focal length support added!

Support for this is now added, let me know if it works as expected!

That depends on how consistent you want to be in relation to your aim as well. If you do hipfire 0% and aims 100% your kinda mixing the FOV based methods and lack consistency. It might work for you though, nothing is really set in stone

No, 0% should work for basically anything.

100% because you have 4:3 stretched to fit 16:9. If you didn't stretch (i.e. black bars) or played in full resolution then 75% would be correct.

That depends on what you want really. 360 distance is more consistent for navigation in hipfire, but less so for aiming.

100% because that is what your zoom sens is (zoom sens 1 in 4:3). So to keep it consistent I also did this for hipfire.

If you want to match both your hipfire and aim to the monitor distance, do like this: https://www.mouse-sensitivity.com/?share=4c5385b43f57abe436ec2a0db8920743 If you want hipfire matched using 360 distance and aims using monitor distance do like this: https://www.mouse-sensitivity.com/?share=936bde139aa10c000c515d6223947d99

Drivers do not support steps in 10 even though you can do this for many of them. If you set it to 220 it would in fact be 200, and when you set it to 225 it would step up to 250, hence why it feels much faster. 200 seems like your best option here.

I checked top tier aimtrainer players fov cm/360 DPI and WPS settings and calculate them from reach windows to game I noticed almost every one of them around %100 and %230 mdh if we calculate their windows sensitivity to game. Just a information.

What zoom sens do you have in CSGO? 1?

shouldn't be afraid of voicing your ideas in regards to aim im pretty sure that most of the active users here are more than interested in optimizing their setup / alternatives crowd sourcing ideas is the fastest way to achieve progress after all out of interest does your setup look like this then ? https://www.mouse-sensitivity.com/?share=c4e4d2bcac8450a57fb351583346e199 or do you manually convert desktop to hipfire with 110 then on another instance match hipfire with focal length 0% to not get the scopes affected by windows 100+ 0% in theory the scopes should have the same number unless they get affected by 100% btw i just noticed that the value i keep going back to when it comes to hipfire 41/43 cm/360 is pretty close to 100/110% mdh on 400dpi ironic