Scca

Input lag or similar is pretty much always the selling point for gaming keyboards and monitors, but for mice it's always the sensor that can do 20K DPI or whatever. But I rarely see input lag being a point for sell. Does that mean that it isn't that much of an issue?

Does the value that you used in the hex editor (0,968325) also gets reverted after trying to change it?

Sensitivity is influenced by FOV in this game so make sure you set that correct in the calculator as well. 0.418354 is correct when using the default FOV of 71(in-game) but when you change that, you change the cm/360 as well.

Since the game does have (I think 3?) different zoom levels for third person, I was wondering if the shown 50 VFOV when setting the calculator to third person applies for only one of those levels or all of them? Since the camera basically just moves farther behind, is there even a FOV change?

I did, and when that didn't work I also changed the settings in the 2 other files that contains the config, Tho now I have fixed it my creating an autoexec.cfg file and placing the sens there.

Whatever I do, my config file changes won't change the ingame settings. I have copied the settings in all possible files that contain the settings but nothing works, ingame it always remains 1.25 Sensitivity and 1 Zoom Sens. Also I couldn't find "zoom_sensitivity_ratio_mouse", only "zoom_sensitivity_ratio"

Is adding the rest on a to-do list?

CoD 2019/CoD 2/Warzone etc all have different sensitivities for Handgun/SMG/Rifel etc Ironsight plus the individual scopes if they happen to have a different FOV. Although I can't confirm this rn but doesn't Vanguard also have different FOVs for the different Ironsights and Scopes?

Hellow ^^ I saw this note in "Ironsight" first but also on a few other games but I wondered what to actually expect from this note. Does this mean that the output that the calculator gives might be inaccurate (for example it says 40cm/360° even when in reality it might be 42cm), or is it simply a note referring to the possible high discrepancy that the calculator might show, tho what it shows still being correct (for example the output says 42cm even when it should be 40cm but due to the inaccurate slider, that discrepancy of 2cm is the closest it can get)

The game is back! Hosted by Papaya Play and even with a Zoom Sens setting. Link

Hellow :3 I have always liked to mix Math with Bias feelings, it's the only way to satisfy both halfes of my brain. That is why I have come up with a way of calculating my ADS way that does result from math but is also the result of a Bias story. Now my question is: Does using this formular actually result in some sort of consistency when applied to all form of scopes and ADS? Or is it just something that is mathematical nonsense? Furthermore, I know that 0,0219% Discrepany is very little in this case but, is there a formula that calculates the Scale-Percantage needed to have a 0% Discrepancy, when 235,504cm is the target value? This would also help to to understand how the Scale function works a little better. -Thanks for any suggestions and also a little sorry to DPI WIzard for always coming up with stupid things and questions like these ^^

Can it just be a text file? Because I have no idea on how to create a config file

Hellow ^^ So I thought that the value for the "actual zoom" number is just the Hipfire VFOV divided by the zoom VFOV since I figured that is how a factor for magnification works but apperently not. So for instance I play on a Hipfire VFOV 74° in R6 and the 1x Scope has a VFOV of 66,6°. 74/66,6=1,11111111. So I thought the actual zoom is 1,11111111 but the calculator says that it's 1.147176. What am I missing?

There are multiple Sniper Scopes with different Zooms but the calculator only mentiones one "Scope", is ther a reason for that?

Hellow ^^ Some games have their sens changed by different FOV and the calculator gives suggestion as to what to change your DPI into to have a 0% discrepancy. So I thought, why not, if possible, include the FOV as a way of suggestion to limit discrepancy in games that have their sens changed by a different FOV. This feature can be helpful when you use distance as a conversion source as I assume that most who use that feature would favor a matching cm/360° over a matching FOV. Maybe this can be taken into consideration ^^