DPI Wizard

Correct, but this is more down to a personal preference. If you run around in buildings and through doors it will be easier to navigate if the 360 distance is the same and the FOV isn't too far off the hipfire FOV. But accuracy will most likely suffer since your crosshair is more sensitive, and tracking or flicking is harder.

Yes, everything will change when you put on a scope, but they all will be linked using MDH 0%, meaning the tracking speed is the same. Flicking and 360 distance will always be different. The numbers I gave you are without any scopes yes, but some guns even differ with ironsight think, I haven't yet analyzed them all. The will all be close to each other though.

Correct, I just updated the calculator to reflect this. That would be (for ironsight) 1 for tracking, 1.151579 for flicking (to the edge of the screen) and 1.409368 for 360 distance

Correct on two of them, don't know about the question marks though, never got them here. Do they re-appear if you delete them? This really depends on if you want the ADS sens (for 1X or ironsight) to be the same 360 distance, tracking speed or flicking speed. The default in Apex (zoom sens 1) is MDH 0%, i.e. the same speed for tracking a moving target. Meaning turning 360 degrees will be different. Also note that Apex for now only has one zoom/ads sensitivity, so whatever you set it to will affect all scopes.

They are exactly the same when the FOV is the same (90), they are based on the same engine and use the same sensitivity. However when you change FOV in CSGO (only possible with cheats enabled btw) you will also change your 360 distance (i.e. affected by FOV), this is not the case in Apex where you will have the same 360 distance for hipfire regardless of FOV (i.e. not affected by FOV).

That's not how computers and numbers work, and no - there's absolutely no difference

Are you playing CSGO stretched or with black bars?

How is you conversion setup configured? It seems like it is set to MDH 0%, which doesn't correlate to your setup in BF1 which is MDV 177%. So if you change both ADS and Scope to MDV 177% you should get the exact same sensitivity in BF1 and BFV as they are based on the same engine The conversion setup values are automatically converted to placeholder values for the Sensitivity 2 field (USA) that you can see slightly faded out in BFV in your screenshot. You can override this by entering a value as you have done in BF1.

Found an error in the in-game calculation, try again now.

Seems like somethings wrong indeed, I'll take a look now.

You can select another type if you want to convert the FOV, but the multiplier is the value you must configure in the config file.

When you convert using any "All" aim, the hipfire sensitivity is the source for all calculations. The only reason you have to specify the ADS sensitivity is so that the xfactor sensitivity for R6 can be calculated as well. If you want to convert directly from R6 ADS to another games ADS, you must select the "Iron sight / Red Dot / Holo" aim to convert from. Also R6 is actually quite bad as a source since the sensitivity for the sights like ADS and ACOG are not related to each other, meaning you can't find a conversion method that will match both of them. They scale completely differently, which is an issue for people used to their scaling since you can't have the same scaling in most other games. For games that do support scope specific sensitivity you'd have to manually convert from and to each scope (for instance R6 ADS to 1X and 2X, then ACOG to 3X, 4X and 6X).

Thanks, I'll take a closer look a bit later today.

Strange, what are your settings? The "Aim Lab" sensitivity option in the game is still the same Unity based sensitivity.

Of course there's support I've solved this for you, it seems like you signed up again in December when you already had a running subscription. It's sorted and refunded now.

The scalars 1-5 doesn't do anything at the moment, at least not the last time I checked. As for the conversion you are doing it correctly.

Vertical matching is not yet fully supported directly, but you can use the calculator in certain ways to calculate it any way. Some games in the calculator do have, but only as a multiplier where for instance the Y sensitivity is 70% of X. This feature in the works though. I'm not quite sure what method would be best for you, but try multiplying your vertical sensitivity by 1.397981 (the difference factor between old and new vertical FOV). This should give you a MDV 100% match.

GZDoom / Brutal Doom is in there

For ADS or hipfire? The FOV settings for ADS seem to be a bit broken atm.

They've never been added, but probably requested a few times. I'll put them on the todo list!

I actually see a lot of people preferring 360 distance for ADS in this game. Either way, any method should work but they all have their own pros and cons. 360 distance makes running around corners and precisely turning around etc easier. MDH 0% will make tracking moving targets the same, but it will be a lot slower in terms of 360 distance. MDH any other % will make flicking to that point on the monitor the same, 100% meaning flicking to the edge. Viewspeed Horizontal is about the same as MDH 70% and Viewspeed Vertical is about the same as MDV 133%. The difference between these and monitor distance is that they will vary a small amount depending on your input and output FOV (+/- 1-2% or so).

Either set it to 86.63 in-game, or the more accurate way by setting cl_fovScale 1.237600 in the file %USERPROFILE%\Saved Games\Respawn\Apex\profile\profile.cfg

It seems like you have set the ADS conversion to 360 distance. For it to be one you need to set it to MDH 0%. If you set the FOV in Apex to 104 (meaning the in-game FOV which is the same as the "Hdeg 4:3" FOV Type) the actual FOV will be 119.26, not 104. You can see this in the output as the Actual HFOV value

Yes, but you might have to experiment with the different conversion methods to see which one feels best for you.

If you're using 38 as the Ana/Widow sense, this is the same as simply using 1 as the ADS sens in Apex actually. Ideally you should also match the FOV, which will be 86.63 in-game or 1.237600 in the config file.