Added!

View full update

Somehow the calculations for CoD: Ghosts don't seem to be correct; entering my desired value of 76cm/360° gets me to about ~42cm in-game.

What's your DPI, and do you use the FOV "hack"? And have you confirmed the the Pointer Speed in Windows is set to 6?

Yes, I'm actually using "foveley". DPI is at 450, pointer speed 6, win7/8 mouse fix applied, no acceleration. Will try again without the "hack"...

Ok, try that. Fovely didn't work correctly for me when I tried it, so the caluclations with FOV might be wrong. Is the distance correct if you leave the FOV at default in the calculator? I'll try with fovely again later today!

Same result without using Foveley unfortunately. Did another test with totally different settings:

 

1150dpi (Zowie FK mouse), aiming for 22cm in the calculator -> 18cm in-game.

 

(Other games I'm playing like BF3/4, CS:S, Quake Live are calculated correctly with my hardware/settings)

So with 450 DPI and 76 cm/360, the calculator says sensitivity 1.215311, but this actually gives you about 42 cm physical distance for a 360? And with 1150 DPI and 22 cm the sensitivity is 1.642831, but this gives you about 18 cm correct?

Do you have both a config.cfg and config_mp.cfg in the players2 folder? I think singleplayer and multiplayer use different files, so if you editing the config.cfg file it does not affect the multiplayer settings.

Exactly. The first one (76cm) was tested using foveley though, which actually seems to have an impact as well. Just did another test:

 

26cm without fov changer -> 22cm in-game (so it seems to be off by a linear amount)

26cm with fov changer -> 16.5cm in-game.

Hey,

 

I transfered the mousesensitivity from bo2 to bf4 and it worked out fine. But than i tryed from bo2 to ghosts but it isnt the same. Am i doing anything wrong?

Hey, are you playing Ghosts multiplayer or singleplayer? If you change the sensitivity in-game instead of the file, is the sensitivity in the file updated?

I am playing the ghost multiplayer. And i changed the sensitivity over the file, but i guess it doesent really matter because when i change the term in the file. it changes ingame. It tells me it need to be 2.5, but i know it needs to be under 2.

This is most likely due to inaccuracy in the mouse sensor. The distance calculated is a direct result of the DPI you put in. If your mouse is set to 450 DPI, but in reality is 430 DPI, you will get a different measurement than the calculated distance. Most mice I've tested are not delivering the DPI they are set to, some are off by as much as 10%! But the important thing to notice is that this inaccuracy is constant, so you will get the same distance in all games, altough not exactly what the calculator says.

Ah okay, that makes sense. Then that puts my Zowie EC1 eVo at ~470 DPI... god that's a little frustrating for someone who's obsessive compulsive about nearly everything, haha. Although when I do the Enotus mouse test, it says my sensor is at 400 DPI... Ugghh

Actually in ghosts they decided to mess with the aim multipliers, in previous games when aiming down sights your aim speed was halved. However in this title the un-aimed and ADS scaler is different. What I did was that I matched my ADS 360 distance as this was the value that was more important to muscle memory.

Calculations for ADS is coming in the app, so that will make this even easier

I find this pretty useful, thanks! One thing to correct: Ghosts FOV: "No possible to change without 3rd party applications." There's now an option to change FOV in game up to 80. It was added in one of the latest patches.

Thanks, I'll update it.

is Call of Duty Ghosts and other call of duty games using MDH %0 for campaing mode?