DPI Wizard

The scope one is separate and only applies to the scope.

Use the one for the weapon you prefer. Since they all use the same sensitivity setting you can only calculate for one.

You can, just use the Vertical FOV in Kovaak's and the same value as in R6.

Is it 4:3 stretched in R6? If so do like this and check the output for Config FOV for Apex: If both games are 4:3 this is how you do it:

If you have the aspect ratio in R6 set to 4:3, then enter a 4:3 resolution. If the resolution is stretched you can only match either horizontal or vertical FOV with 16:9, not both. To match horizontal do like this:

The way you have done it works if your FOV in R6 is 73.74. It doesn't really matter which FOV Type you use as long as the Actual HFOV in the output matched. But it's easier to just vertical. If your configured FOV in R6 is 90 however, it is wrong the way you've done it. Do it like this if so: Note how the Actual VFOV of ADS in R6 is 81, and this value is used for Kovaak's with the FOV Measurement set to vertical.

Since your cloud sensitivity does not match any conversion method you need to do it in two steps, and use Advanced mode. First do hipfire to hipfire: Then do scope to scope using the calculated hipfire sensitivity for CSGO:

You are correct with the lower 360 distance, but what you keep instead is a consistent aim based on what you see on your monitor. What works best is down to personal preference though.

It works for most people, but there are some scripts that doesn't execute properly for everyone, looking into it.

Monitor Distance is generally more suited for scopes, as 360 distance does not work very well for them. But some do prefer Monitor Distance for hipfire as well, as it keeps either tracking speed (0%) or flicking speed (e.g. 100%) the same regardless of FOV. There's a video on the front page explaining Monitor Distance. Here's what 0% does (tracking speed):

Tested it a couple of days ago, and it actually didn't do anything. It will probably be fixed at some point, so if it actually changes the FOV let me know!

It isn't, it's using a different matching method. The first one you posted is correct for 360 distance, if you are reacting the the difference in 360 distance that's because of the limitations in the game, i.e. lack of decimals.

Did you sort it out?

Updated for Bloodharvest!

They changed a lot, updated it now with hunter and scavenger sensitivity

Done. Not easy to set it accurate though, as the game lacks sensitivity numbers. I have pre-purchased it, but don't see the beta available anywhere?

There's no numerical value to the sensitivity in this game, so see the notes on how to set it.

Interesting, I assume it must be something hardware related then. I'm getting the same sensitivity here with DX12 off and on. Same with DXR on and off too.

Fixed

BTW, it's only bugged when you use the "All" conversion, for the zoom aim it works.

Thanks for the report, I'll fix it soon!

Added.