Noticed a bug with call of duty fovscale commands

[randomguy7]

So I was testing rather extreme fovs in the following games:

Rim/t7x: [AlterWare] A fork of https://github.com/alterware/t7x - [Latest] Call of Duty: Black Ops 3 Client | Compatible With BOIII Client - t7x - Self Hosted Git Service (rimmyscorner.com)

 

BO1, BO2, MW3, WaW redefined. - Plutonium Project

 

AlterWare | Official Home of IW4-SP, IW4x, IW5-Mod, IW6-Mod and S1-Mod

 

Releases · auroramod/h1-mod (github.com)

 

and I was mostly playing something crazy, 120 fov with a fovscale of 2. I was playing mostly on black ops II, and had my dpi at 400 and sensitivity at 0.47 but I found that despite the crazy fov I actually really liked that sensitivity. I was wondering if I could perhaps translate that sensitivity to another game like quake where the fov is uncapped and I could perhaps convert that sensitivity to something else in, say, viewspeed vertical or 0% mm

[randomguy7]

so, from analyzing a screenshot with the kovaak's tool and by using sensitivity matcher, I found what I was looking for.