DPI Wizard

Does the value in the config file revert back to another value if you enter the game and exit again?

Iron sight: 66.6 (1.111x) ACOG: 25.9 (2.857x)

If they're set to the default value in-game they won't appear in the config file.

No need, the sensitivity is the same with and without. Raw input will improve latency etc, but not affect the sensitivity.

Answered your PM.

125Hz doesn't solve the acceleration issue unfortunately. This game has the same issue as Combat Arms Classic which uses the same engine.

It's already in the calculator

Is your configured FOV in CoD4 (i.e. cg_fov) 80? Of so you should indeed enter 112 (80*1.4) in the FOV field when FOV Type "Hdeg 4:3" is selected.

Remember that 80 (actually 80.69) FOV in CoD4 is for 16:9 resolution (FOV Type "Hdeg Res" in the calculator with 16:9 resolution). The configured FOV is 65 based on 4:3 resolution, (Hdeg 4:3), and the extra width for 16:9 is added on resulting in 80.69 shown in the calculator as "Actual FOV". Just for your info

Fov scale 1.4 should be the same as entering 91 (65*1.4) into the FOV field for CoD4 in the calculator. You cannot adjust the FOV in Fortnite however.

Certainly, but I don't play this much so it would be extremely helpful to know what aims/guns to analyze

Start by checking out the two videos on the front page

LOL controls WPS itself, and ignores the WPS setting from Windows. The sensitivity steps in the game are exactly the same steps as the 20 WPS steps. It is not technically acceleration in that it is 100% constant and unaffected by speed, for instance moving the pointer 2 pixels per count or 1 pixel per 2 count.

No, it was wrong in the calculator (hdeg 4:3 instead of vdeg). Since the game was added before the calculator even had FOV support it was assigned a default FOV type.

Updated Minecraft now. Removed the WPS affect and corrected the FOV type.

Indeed that's the principle. The challenge however is when the view does not rotate 360 degrees (like in a lot of vehicles) and/or the full view is obstructed by scope edges etc.

By analyzing each and every one of them with scripts simulating mouse movement Some of the scope FOV's are linked to their power, but they can be based on HFOV, VFOV or perceived zoom, while others have absolutely no relation to their zoom power name at all. Data mining done by others can help support the analysis, but due to the wast amount of different engines and protected source codes this is not a method to rely on. So to take out any guesswork they are each analyzed individually.

Yea, I've done pretty much what I can. The ADS is twice the 360 distance of hipfire even though the FOV doesn't change, and they are affected by the same settings... Bad design.

What distance do you get in Fear the Wolves with those settings?

Done, should be perfect now

I see now that they've updated scopes and ADS a lot, fixing it ASAP!

Hi! Where in the game are you testing and with what weapons/scope?

Added ADS options now, see if that works. Same sensitivity setting as hipfire though.

Do you mean for the regular iron sight aims?

Yes, that should work a lot better.