Scca

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 ^^

You could use the CS:GO settings for that. I know this is 5 years late but maybe it still help. Anyway, the Calculator says that the FOV can be found in the file under the name "Field of View" which appears not to be the case. Also, does the "fov_desired" use the same as the value for that "Field of View" shown in the calculator? Because for some reason I have been using "74" as a value for that when I wanted a VFOV of 74 but I doubt that this has ever been correct.

Hellow ^^ I played a bit with the Calculator and found out that the calculated FOV for ADS/Scopes does not seem to be correct. The FOV of ADS is always the same (65 VFOV for the Clear Sight for example) but when using an Hipfire FOV below that value (50 VFOV for example, that is the lowest), the FOV simply doesn't change when using the ADS. The Calculator however does not recognise this and will always use the same FOV for the ADS, even when you use a Hipfire FOV that is below the ADS FOV, which results in the calculator displaying that you have a higher FOV in ADS than in Hipfire, which obviously is not true. I would assume that this also results in a false Sensitivity calculation, since I assume that the Sens is calculated based on the FOV (Unless when using cm/360° as a calculation method for ADS. I couldn't test the same with the Sniper Scope.

Wha about the Scope Sensitivity, do I have to do that manually too?

Hellow ^^ I played a lot of Valve engine games (They are mostly Hipfire Only, like CS or Garry's Mod) recently and were very good at them too, so when I went back to playing other shooters I figured that it might make more sense to match the FOV and Sensitivity between the Hipfire of CS:GO and my favorite Scopes in the other games. But the problem here is that I don't know how to do that or if it's even possible, as this for example didn't really work, especially because the "Multiplier 2" was locked in the Output. So basically my question is: Is there a way to enter desired values you want to have while in Scope and that the calculator then shows the settings you need to use in Hipfire in order to get them?

Hellow ^^ My thoughts are a bit difficult to explain so I made it into a picture seen in the attached file. I always assumed that the ADS/Scope sensitivity of the output game is calculated the way the blue arrow indicates: First the Hipfire Sensitivtiy is calculated and then based on these results the sensitivity of the ADS/Scope is calculated. But trying this out with a game that has a universal setting for all scopes like CoD with their coefficient setting, turns out that ADS/Sopes are calculated the way the green arrow shows: That the sensitivity for the scopes are based on the Hipfire FOV of the Input Game, not the Output Game. This can be seen here. Despite the Coefficient being calculated at 1.33, each scope still has a different value than 1, which I can only assume is because the calcualtor tries to match the sensitivity based on the 120 Hipfire HFOV of the Input Game rather than the 107 Hipfire HFOV of the Output Game because otherwise a value of 1 for each scope would suffice with the Coefficient already being at 1.33. My question basically now is: Is all of this that I just said correct or am I missing something? And Is there a way to make the calculator use the way that the blue arrow shows? Or to make it a bit more specific: Assuming that both Input and Output Games have different Hipfire FOV and a different Hipfire cm/360° BUT both games have a Scope that has the value of 100 HFOV, would the calculator make it so that the scopes have the same cm/360° in both games? Since I always matched FOVs on both games so far this never really mattered to me anyway but now that I start to play games with locked FOV (Shatterline/Destiniy 2) I thought I would need a big work-around to have the FOV calculated the green-arrows way since that would be my preffered way. But I guess if that is how the calculator already works then I would not need to worry.

Hellow ^^ Searching the Web brings no result other than Games from 2005, where I guess that kind of games were popular. Maybe someone has a multiplayer game in mind that uses a mechanic similar to Valorant and CS:GO (maybe without the "you need to stand still to have accuracy" part, and more runnign and gunning)

An Update just came out making the FOV changeable. Hopefully the calculator can be adjusted for that soon.

For me it's not working. It doesn't show any output or input at all

Name: S4 Xero Website: https://xero.gg Relesae Date: I guess a year ago Status: Released Availability: F2p I already sugested this nearly a year ago in the S4 League section, but it went unnoticed. S4 League got shut down long ago and private servers replaced it, S4 Xero being kinda the only one that is still in use.

Hellow, Despite pretty much every game having the same set of scopes (2x, 4x, 12x and so on), not every game calculates them in the same way, so having a 2x Scope with same Hipfire FOV in two different games will result in different magnifications and FOV when scoped in. But I still thought that the magnifications of each scopes in each game are somewhat calculatable and follow some sort of rule that can be set up, a rule that maybe can be applied to all scopes within a game itself. So I wondered if the actual magnification of a scope can be calculated by using the Formula "(VFOV Hipfire) / (VFOV ADS)" As an example in the case of Battlefield V, a 2x Scope and my usual 78 VFOV this would mean: "78/44.115426= 1,768089012673254" My thought there was that the 2x Scope actually scopes in roughly 1,77 times, and not 2 times as it should be. Weird but at least an answer. However, when using a different FOV, 90 for example, there is a different result with the same Formula: "90/53.164783= 1,692849945423458" So my question basically is: How do Scopes work? Why is apperently the magnification of scopes different when using different FOVs? And is there a way to find out how each game handles each magnification?

The games early access gets released on 13. April with hopefully a change to the fixed FOV and who knows what else, it will cost 22$ tho. So when can an update to the current calculations be expected, should there be any changes?