Hi,

I've been playing around trying to figure out a good match between windows sensitivity and games that I currently play, which are CoD: Warzone 3 and Fortnite.

I tried to use the calculator and use same settings for Windows, but for both I get different results in terms of 360 distance, when I use Windows as source.

I would expect that using source as Windows for both games would give me their suggested sensitivity for the same 360 distance, or a sensitivity that when I would try to convert from for example CoD to Fortnite, would give me the same result.

For Cod I get 360° Distance: 32.6758
which gives sensitivity 5.3 for my settings

For Fortnite I get 360° Distance: 38.8228
which gives sensitivity 5.3% for my settings (I bet it is a coincident that it gives similar number).

When I convert CoD to Fortnite, which is trying to match 360 distance, I get 6.3%.

Am I doing something wrong?
And yes my source settings for Windows are exactly the same.

3 minutes ago, galfordus said:

I would expect that using source as Windows for both games would give me their suggested sensitivity for the same 360 distance, or a sensitivity that when I would try to convert from for example CoD to Fortnite, would give me the same result.

This is not what converting from Windows does, it converts based on monitor distance, i.e. how far you have to move your mouse to hit a certain point on your monitor.

For instance MDH 100% matches the distance you have to move your mouse in Windows from the center of the monitor to the edge, to the movement in-game to aim at something at the edge of your monitor.

For MDV 0% it matches the same tracking speed, which for Windows is how fast the pixels are moving under your cursor.

So this is all based on the FOV of the games, so with a different FOV you will also get a different 360 distance.

10 minutes ago, galfordus said:

which gives sensitivity 5.3% for my settings (I bet it is a coincident that it gives similar number).

This is indeed just a coincidence, but I guess it can seem weird at first.

Thanks for your quick reply.

BTW the distance to move mouse cursor across screen for Windows sensitivity shows 5.8522cm, when in reality for my provided settings is  20.8077cm to move from one edge to the other. I'm not sure if this is a bug or a different interpretation, in which case the description should be different.

Anyway, the provided sensitivity seems almost OK, but I would expect that in the end I should end up in same mouse movement distance on the pad to achieve 360 distance in both games, but maybe I'm wrong.

I would like to have consistent aim in windows (since I use it the most at work) and games. Perhaps I missed some guide on how exactly to use your calculator to get it?

Is there any specific guide I should follow to make sure I setup all games accordingly?
Until today I was picking up the game I played the most as source and converted to any game, which worked pretty well, but I wanted to make sure I'm doing this the right way and recently I came up with an idea that since I'm using windows the most, then it should be the source for all, but having that 360 distance so different worries me if it will ruin my aim.

15 minutes ago, galfordus said:

BTW the distance to move mouse cursor across screen for Windows sensitivity shows 5.8522cm, when in reality for my provided settings is  20.8077cm to move from one edge to the other. I'm not sure if this is a bug or a different interpretation, in which case the description should be different.

It's showing you the vertical distance since the conversion setup selected is vertical. Switch it to horizontal and it will show you the correct value for this axis: 

15 minutes ago, galfordus said:

Anyway, the provided sensitivity seems almost OK, but I would expect that in the end I should end up in same mouse movement distance on the pad to achieve 360 distance in both games, but maybe I'm wrong.

I would like to have consistent aim in windows (since I use it the most at work) and games. Perhaps I missed some guide on how exactly to use your calculator to get it?

Converting from Windows does not necessarily feel correct for everyone, even though it's mathematically correct. There are many different ways to go about the conversions, the best is probably to base everything off of a game you are comfortable in, that have proper sensitivity settings for different aim levels.

If you don't have this, basing it on Windows is a good option. However, as you found out, the 360 distance for hipfire will be different based on the FOV. So a good workaround is to find one game that are converted from Windows that feels good, let's say MW3, and use this as the source for all future conversion, but then do 360 distance for hipfire and MDV 0% for scopes. For scopes you can never expect the same 360 distance, so they will with this setup still be based on Windows.

Thanks, 

So to get consistent aim in all games and fov's is the 360 distance the correct approach?

Because I can't imagine to do 360 distance with a sniper rifle  

You mentioned MDV 0%, but being honest I don't fully understand horizontal vs vertical and those % to setup correct sensitivity.

If there is a guide or something that I can check I would appreciate.

Just now, galfordus said:

So to get consistent aim in all games and fov's is the 360 distance the correct approach?

Because I can't imagine to do 360 distance with a sniper rifle  

Just for hipfire (and in some cases maybe ADS), but scopes should use one of the other conversion methods that are FOV based.

The conversion methods are explained here

Thanks, that is exactly what I was looking for.

I'm surprised for such prompt response and really good answers, thanks !