Call of Duty 4: Modern Warfare

8 hours ago, Valarri said:

What does that mean?

Basically, it means your crosshair is matched between FOV, since 0% of your monitor is the crosshair.
If you don't know what monitor matching is you should watch this video:

Hi guys, im pretty sure that COD 4 sensitivity converter is broken. i've just set the cod4 sensitivity to "1" at 1600DPI, 80 of fov and checked with kovak sensitivity matcher. on source engine like csgo the same sensitivity should be 1.317123 at 1600dpi so i ve used it for compare it with that tool and the results are off.

Actually i dont understand if it s an engine problem (like not stable fps) or just the calculator.

13 minutes ago, DPI Wizard said:

It's correct, when you change FOV in cod 4 the 360 distance will also change. In Kovaak's however the 360 distance is the same regardless of FOV. 

I'm not talking about Kovaak's game but about Kovaak's Sensitivity Matcher, it s a tool/script that he made for test matching sensitivity. and the result on cod4 are off to me.

1 hour ago, DPI Wizard said:

What exactly are you checking? Sens 1 and FOV in COD 4 compared to another game?

im comparing csgo sens to cod4 and by testing it with kovaak's sensitivity matcher the translation seems wrong

5 minutes ago, DPI Wizard said:

I haven't tried Kovaak's sensitivity matcher, but how many counts do you get for one 360 with sensitivity 1 and FOV 80 in COD4?

i cant tell it, it doesn t work like that. im gonna make a video, i dont know how to explain.

33 minutes ago, DPI Wizard said:

I haven't tried Kovaak's sensitivity matcher, but how many counts do you get for one 360 with sensitivity 1 and FOV 80 in COD4?

im uploading it, however i think that s not a conversion problem but it s cod that is inconsistent (at least for me). in the video you can see that i try 20 revolutions x 5 times, and 2 out 5 are off, i dont know why. i ve used this tool on other games, never had a problem with it.

Just now, DPI Wizard said:

Gotcha, that's acceleration or smoothing. Try this if you haven't already:

 

To disable acceleration, set "seta cl_mouseAccel" and "m_filter " to "0" in the config file or in the console. Also make sure "Enhance pointer precision" is off in Windows.

i know, both commands are set to 0 and even enhance pointer is off

1 minute ago, DPI Wizard said:

Ok, if you've already done that it's just the game being inconsistent.

is something that happens often? maybe with games affected by WPS?

Wizard, would it be possible to add a ADS calculator for this? I'm trying to convert my ADS to match destiny 2

Meant to post this a while ago, but it seems like ultrawide resolutions (really wide ones) affect the sensitivity??!  Or let me rephrase that, it seems like MWR doesn't really support ultrawide formats wider than 21:9 (not so sure that's the exact cutoff or even if 21:9 is "properly supported"),  and that  seems to affect the sensitivity somehow.

Here is what I'm rocking with, and you can tell something isn't right (sensitivity wise), even more so with what I would actually like to use. The latter is wayyyy off, and not quite super ultrawide for whatever reason. Images for reference:

So yeah, really weird behavior, guess there is a reason why people call MWR a bad port. Something similar I have experienced and is actually worth looking into (calculator wise) is in CoD2,  when you apply the ultrawide or multimonitor fix, it also seems to affect the sensitivity, but in this case, ultrawide formats wider than 21:9 work just fine.

Ohhh I see . Really weird on Raven Software or HMS to max the fov at 120 hdeg..... Pretty much any ultrawide resolution isn't even "properly" supported at the annoying 90 fov cap lol.

Though maybe there should be a special option in the calculator to remove it (call it single-player 3rd party tools/H1 mod?), because if I'm not mistaking, when I played the campaign like two years ago in a different ultrawide monitor than the one I have now, I didn't really experience this annoying 120 hdeg cap. And I also mention H1 again, because when it first released, I  had zero problems with it in my old uw monitor (I even used my CoD:AW/S1 client sensitivity & fov settings), though for whatever reason, it seems like either my H1 copy is bugged, or something within the client is bugged because it seems to be capped at 90 fov like the base game now?!?