DPI Wizard

Painkiller Hell & Damnation already has a proper config file calculation, you just have to change the location from in-game to config file.
I will look into updating Bulletstorm.

It depends on your preference really. To compensate for the size difference you need to use a different conversion method than 360 distance for hipfire, like for instance MDV 0%. Then the monitor size will be accounted for the conversion.

The game is a bit quirky, it will round to the nearest whole 4:3 FOV before calculating ADS FOV, as well as max out at multiplier 1.642857 (115 4:3 FOV), while the ADS continues to scale up until multiplier 1.7. For these reasons the ADS value will sometimes not be 1 although the conversion is set to MDV 0%.

This is correct, hipfire will be exactly the same both for FOV and 360 distance, and all the scopes will have the same tracking speed.

These are not in use anymore, unless they've recently added more scopes. Only the in-game options are actually available.

Since the FOV in PUBG is different, you need to adjust the scale to get 1 for the zoom sens in CS2:
https://www.mouse-sensitivity.com/?share=54d2ef86efce5056566a35872c2f914b

Kovaak's is wrong, that formula is not correct :)

Gotcha! I don't play much on consoles, but I'm guessing the issue is kinda the same as with mouse sensitivity, that the stick or dpad sensitivity varies a lot?
 
Maybe it's something that can be done in the future, but for now the focus will be on PC games

Try using MDH instead of 360 distance. 100% will match the movement to the edge, while 0% will match the tracking speed:

If the calculator is in simple mode, set it to default or advanced in the settings menu :)

No, this is not an issue. Around 3-4 on 1080p is where it starts to be really noticeable. And if you're on 1440p or 4k, then even 2-3 will not be an issue.
Even so, staying around 1 is usually preferred.

Ok, so the adblocker seems to block the actual mode switch. I will look into this.

If you turn ADS zoom off, the ADS sensitivity will be the same as hipfire, so just configure the hipfire conversion to match your ADS preference.

Yes, the one with only 1x.

The concept behind using the monitor size in the conversion, is to keep the movement within the old monitor size consistent. In other words, to cover a cutout of 23.6 inches on your new 27" monitor, the movement should be the same. So for instance if you use MDH 100%, the mouse movement to move to the edge of your old monitor, should match the movement on your new monitor where the 23.6" would have ended. For this reason the sensitivity has to be slower, as with the same sensitivity you will of course cover the size of a 27" monitor with this movement, which is too fast.
This is not a FOV based conversion, it's purely based on the physical size of the monitor.
Note that using monitor size in the conversion is a concept that does not feel right for everyone. Personally I prefer the same sensitivity regardless of monitor size, but this is subjective.

Hi!
There was an update earlier today, so you might have some old cached files in your browser. Have you tried to force a reload (shift+reload)? Does it work in a private/incognito window? And lastly, do you use any addons that might block scripts etc?
Can you show a screenshot of what it looks like?

They are not related.
You can see this in the calculator if you select the ADS aim, as it only has one sensitivity setting.

This is actually one of the main reasons fields are locked. A lot of people were typing in the wrong FOV because of the confusion with viewmodel FOV and then getting wrong results.
The viewmodel FOV of 68 (which also is the default value) is the rendering FOV of your weapon (basically how big or small your weapon appears), it has nothing to do with your actual FOV. The FOV in CS2 is locked to 90 unless you enable cheats (which you can enable in the calculator, but is irrelevant for this scenario).
So unless you play with cheats enabled, you can ignore the FOV setting in CS2

Are you using the default FOV of 90 in Delta Force?

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  

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

Is your FOV correct (120)? This impacts the conversion. Other than that you can adjust the Windows/2D conversion setup, but it's already at it's traditionally slowest. This matches the pixel-by-pixel movement between 2D and 3D.
 

Unfortunately this game is unsupported due to issues with too much smoothing/acceleration combined with a maximum turn speed.

The Sensitivity 1 field for Tarkov is the total change in turn speed due to armor, not the sensitivity (see the game notes section). The sensitivity goes into the Multiplier 1 field. Fix that and the conversion should work as intended

You are changing the source here, which is why you get different results.
In the last one the correct Apex settings would be 1x Optic 1.29, not 1.