DPI Wizard

No, for some reason they limit the ADS sensitivity to max 100, while the scope goes to 200. So the the best you can do is to set it to 100, or lower your FOV in ARC to 60 so it more closely matches the horizontal FOV in CS2, this will make nearly all ADS within range.

The sensitivity is based on FOV, and it will only be the same 360 distance if the FOV is the same with the default settings. BF6 does have 1x scopes which will match hipfire in every aspect (FOV and 360 distance), but all ADS in BO7 has zoom applied, so the 360 distance will be adjusted accordingly. If you want the same 360 distance, you can set the ADS conversion to 360 distance, this will make anything below 2x the same 360 distance as hipfire. For scopes more powerful it's usually not recommended to do this as it will make aiming precisely very hard since the scope will be very sensitive.

If you enter a different monitor size, it will be taken into account for anything not using 360 distance in the conversion setup. This doesn't necessarily match your preference, and when halving the monitor size, you also double the sensitivity. This generally only works if you do a small monitor size change, like going from 24.5" to 27, and you want to keep the 24.5" portion of the new 27" inch same. When going from 32" to 16", the impact will be massive, and probably not what you are after. I would suggest not entering a monitor size if this is the case, as it then will be ignored. In your case the sensitivity will be the same since the aspect ratio is the same, and this game is not affected by resolution.

Thanks for letting me know, this bug is fixed now.

That depends on what you mean by 1:1. If you have an existing game with ADS sensitivity, it can be based off of this. If not, the best place to start is to set the coefficient to 0 and see how that feels. This will keep the tracking speed consistent between aims.

It's exactly the same as all the other game modes.

The FOV will use the default value unless you have turned on Auto FOV.

These two games use the same FOV Type though (as long as you set it in the config file), so you can just use 85 for BF6 as well.

Thanks that helped a lot!
It was actually the apostrophe in "Director's Cut" that caused the issue, it should be resolved now.

Is all your zoom sensitivity in BF4 set to 100%? If so, this will be the correct conversion.

By default, only hipfire is matched using 360 distance, as this is usually not desired for ADS (unless it's a really low zoom), and is terrible for scopes as it will make aiming impossible.
Instead, the ADS and scopes are matched using the FOV to calculate a consistent aim based on what you see on your monitor. This will make movement such as tracking a target or snapping to a target the same regardless of zoom, instead of keeping a consistent 360 distance which does not make sense in terms of aiming.
You can however change the settings to your liking by selecting for instance 360 distance for ADS and scopes, but for most games this won't even be possible for the more powerful scopes since the sensitivity will be out of range.


As for measuring 360 distance, a tool that works in a lot of games is Kovaak's Sensitivity Matcher. This will send inputs exactly replicating a specific movement so you can verify that the sensitivity is correct. Do note that it does not work for all games, and for some it might require tuning of the speed (partition movement and frequency) to work correctly.

Unless there a specific game that has had the sensitivity changed recently, all the calculations should be spot on mathematically.
There are a few things that can affect the feel, and if the game has any issues it should be mentioned in the game notes in the info section.
These are usually things like:
Acceleration or smoothing that has to be disabled.
Polling rate has to be set to a very low value to avoid smoothing that can't be disabled.
Specific settings like vsync or frame rate limitation has to be adjusted.
Other than that, the calculator will provide you with the closest possible match for your conversion. For hipfire and 360 distance specifically, you should also match FOV whenever possible, but do note that some games render the view very differently (for instance more barrel distortion), and when comparing first person and third person your preference, especially for FOV, might be different.

I have manually deleted this now, let me know if there's any more issues.

I've updated the path now, but the big issue is that they introduced smoothing when going to Unreal Engine 5. I can't find a way to disable it in the config files, so the only solution that works is using a polling rate of 125 Hz or lower.

As mentioned before, this is because of rounding.
1.522727 in CS2 is 10746.2706 counts/360.
Converting this to Enlisted, a perfect conversion would be 0.62037025925926, but this is rounded down to 0.620370, which in Enlisted is 10746.2751 counts/360.
When you are reversing the conversion from 0.620370 in Enlisted to CS2, the perfect match in CS2 would be 1.52272636363640. Because of rounding, this becomes 1.522726 which is 10746.2776 counts/360.
So no, there is no error in the calculation, this happens because of rounding and different sensitivity schemes.

I see. So if I understand correctly, you want to enter a specific degree, and have the monitor distance that matches this degree to be applied to the conversion?
I will play around with it to see how it works in practice.

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 :)