DPI Wizard

The same issue is present here, although to a much lesser degree. The camera is still behind the center of rotation when scoping. The FOV is definitely 90, I measured again now to be absolutely sure nothing has changed. However, 3rd person FOV can feel very different to 1st person. Your normal feeling sensitivity of 1.48 is very close to a MDV 0% match (which matches the tracking speed between different FOVs).

Let me just add though, in case anyone finds this thread by searching, that fields are locked due to restrictions in the game, and this might change. CS2 as a competitive shooter will likely never change this, but for new games just released, a locked FOV might just mean the devs haven't implemented it yet, and FOV change is made possible in a patch. The reason we can't allow for FOV change before the game allows it, is because we don't know how it affects the sensitivity. So if it is different from what the calculator allows, make a post in the game thread using the link in the game info section and it will be fixed

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

Ok, thanks for the video, that helps a lot! I actually thought you meant the other way; when you turn the camera and there's a wall or an object blocking the path of the camera, the camera moves closer to you so it affects your view. What you are demonstrating is something else though, and I wonder if this is what causes so many to claim Rivals has acceleration? This has nothing to do with Rivals, acceleration or game settings, it's just an effect of the camera not being in the center of rotation (i.e. 3rd person). The pivot point is in the center of your character, so any object close to you will require more movement to target than seemingly overlapping objects far away. If you measure against an object "infinitely" far away, the movement will be the same, and in essence the same as in first person. There's nothing you can do about this behaviour though, as both camera distance and distance to target is at any point unknown.

This game doesn't have any sensitivity setting it seems.

Still unsupported.

I'm not sure if there's any general connection between your controller preference and mouse sensitivity, but if you have a preference in terms of DPI on your desktop you can use this as the base. Using this doesn't necessarily suit everyone, but it's at least a place to start.

It does not change the rotation/360 distance, but it changes how it feels. As far as I know there's nothing you can do about it unfortunately.

Good to hear we found a solution!

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

Here in the sav_graphic.sav file. You have to modify the FOV in-game for the value to show up:

You can force it higher in the config file, but I also get max 100 here. I'm just on the demo though, so I figured it might be different?

Before I look into this more, can you also show a screenshot of the bottom part of this page? I.e. From ADS Sensitivity Type all the way down to Sensitivity Transition Mode?

This will keep the same tracking speed within Rivals, but it will not match Black Widow. For that you need to do like in your first conversion, although I'm not sure where you got Mouse Horizontal Sensitivity 2.46 from for Rivals?

If you get two different numbers you have either changed source FOV (i.e. what you are converting from) or the conversion setup for the scope. If you link your two conversions using the purple share button I can see what's wrong.

Yeah, this probably depends on your locale settings in Windows, good to know! Updated!

As far as I know these lines are not in use.

The sensitivity is updated now!

It is completely different now, I'm working on updating it.

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

Beyond Citadel is added.

The sensitivity slider is not accurate, expect some discrepancy. Use the config file for best accuracy. View full update

These values control how the ADS and scope sensitivity is calculated, and should match your preference. You probably don't know what your preference is, so there is a reverse function that lets you find the correct conversion settings based on existing game settings. If you don't have an existing game you want to use as a base, starting with the default values is recommended. Be sure to check out the instructions as well, a lot is explained there.

There's been a lot of changes here, so nothing is correct currently. I'm working on an update now, but the aim and scope sensitivity is really complicated for some reason, so it takes a bit of time!