conan1

Updated with MW3 info!
View full update

I guess it's likely, but we'll just have to wait and see. I will add it as soon as the open beta is out.

We now have a direct integration with 3D Aim Trainer in the calculator, so you can simply click an underlined sensitivity value in the output to test this exact sensitivity instantly!
Here's how it works:
If you click a hipfire sensitivity, you will get this sensitivity for both hipfire and ADS in the trainer. If you click an aim you will get this sensitivity for the aim in the trainer, and hipfire will either be derived from the sensitivity input or reverse calculated based on your conversion setup. The calculator input (resolution and DPI) must match your current setup for the sensitivity in the aim trainer to be correct. Note that currently the aim trainer does not have access to raw mouse input, so WPS will be applied if you have changed it. This is scheduled to change when browsers begin to support raw input next year.

A couple of notes just reiterating and confirming what the devs have said:
Hipfire is exactly the same as in MW. Relative coefficient works exactly like in MW. Scopes above 4X works exactly like in MW (meaning they have locked FOV not affected by anything), but they do not match in terms of their power, so a 4X in MW is not the same as a 4X in CW.
CW uses correct optical zoom for the FOV based on a locked FOV of 80 (or almost, it's off by a tiny bit), while MW uses seemingly arbitrarily assigned FOV values. Scopes below 4X and ADS have a very weird scaling when set to "affected", meaning they do not scale the FOV in an expected manner (they are less affected than in MW). This does however not affect the sensitivity, which still behaves as expected based on the FOV. Legacy works differently, as it is simply MDV 0% calculated based on your FOV. In MW it is MDV 0% to an FOV of 65 in Hdeg 4:3.  If you use Relative in MW you can use the exact same settings (including FOV) in CW and everything will be the same. For those not experiencing the same sensitivity in MW and CW based on the above there must be a bug in CW affecting some users.

Call of Duty: Modern Warfare coming tomorrow!

if someone has interest, here are the correct positions without clantag from the image above:
 

Yes.

It's a little bit off, but because the slider sets a multiplier value you can't see in the menus, not because it's plain wrong.
The displayed FOV is within +/- 0.5 degrees of the actual FOV, and you can see the multiplier in the config_mp.cfg file. And unless these numbers change, it's the value after "setcl -1170286343". Multiply that number by 80, and you get the correct FOV.

i think it's 107.8 but it would be great if dpi wizard could double check that.
 
for true fov 100 i've set it to 101.05 now.

I will check it, downloading now. But I won't be able to test until tomorrow, so I've removed the FOV affect for now.