DPI Wizard

Try using MDH 100% instead. 0% is generally not suited for 2D to 3D the way it is from hipfire to scope.

Like this (with your own settings):

Select the scope and enter your configured FOV, then check the output for the Actual HFOV.

Done

The actual sensitivity values in this game have nothing to do with each other, there's no connection between aim/zoom and sensitivity. So it's not unlikely to get a very high or very low number for a conversion that in many other games produce similar numbers for all aims. There might be small variations based on the exact weapon and aim etc, what exactly are you testing with?

Sensitivity is currently all over the place in this game, I'll check again for release. If they don't fix it it can't be added.

It's basically where you match the crosshair between aims. 100% is the movement to the edge of the monitor, 50% is halfway, 0% is the tracking speed i.e. the rate at which you have to move the mouse to track a moving target. In terms of how fast and slow it feels, 0% is the slowest, 100% is fast and 360 distance is the fastest (assuming you go from a higher FOV to a lower FOV).

I'll see if I can add a "show discrepancy" button or something for this. Showing it by default will probably clutter up the output too much. I'll also check the vertical FOV, but this is usually not done unless there's an option to change it. They haven't added this have they?

Ideally you should use the same method for both. But some prefer 360 distance for ADS since you might ADS while navigating around etc.

Correct.

For the 100% to take effect you also need to select Monitor Distance - Horizontal. Viewspeed is locked to a scaling based on geometry.

MDH 100% will have a more progressive scaling. If it's too fast try a slightly lower percentage.

Indeed.

If you are using 360 distance as the conversion method, the sensitivity will not change when changing resolution. If you try a different method like MDH 0% or 100% it will change according to your resolution change

None of those settings make any sense based on the scaling. He keeps saying same sensitivity or absolutely matching hipfire sensitivity, but there is no such thing for different FOV's. It's only possible to match one aspect of the sensitivity between FOV's, be it 360 distance, tracking speed, a specific flick distance or a geometric variable like viewspeed. His numbers doesn't do any of this In addition FOV is cruical for the ADS and scope sensitivity, as they will all scale to this unless you are using sensitivity 1 for all of them.

The game uses MDH 0% as a scaling factor, so if you have chosen this as the conversion method for ADS and scope you will get the same value for all of them. If they feel too slow, try a higher MDH value. First try 100% and see if that feels good or is too fast.

There is no 1:1 if the FOV is different. You have to choose between 360 distance or monitor distance X%. With each one of these one aspect of the sensitivity will be the same while everything else will be different. So the "best" method depends on your preference, basically if you want the same 360 distance, same tracking speed or same flick distance.

What m_yaw and sensitivity settings are you using?

Fixed Everything seem to have it's own unique scaling btw, very bad for the experience...

Already added

The FOV is only lower for the hunting rifle. All others just move the camera closer to the character with the same FOV.

Updated

Other than ADS, I think every scope power should be equal on every gun. Haven't tested this extensively though.

Not for all games no, only for the selected game. Since you need to input values such as FOV, maybe WPS, sometimes an existing sensitivity value or a specific special option, this wouldn't work very well unfortunately.

Hired Ops is added!