dsu

are the scope fovs in the calculator the inner or outer fovs?

turn speed modifiers are getting removed

Name: Citadel: Forged with FireWebsite: https://store.steampowered.com/app/487120/Citadel_Forged_with_Fire/Status: releaseRelease date: July 26, 2017Availability: free to try/sale for $16 USD until Feb 9, otherwise its $40 USD

Is there a reason why using auto FOV for Rust gives you 2 decimal places now (ex. 70.53) instead of what it used to (ex. 70.5328)? I know realistically there's no difference at that point but I always thought Rust reads up to 5 decimal places for FOV because I can see shadows moving in-game, so I'm just curious why it would ever change in the calculator, unless I'm wrong.

Here are some training servers where you can find all the guns super easily if you need them. Just join an "aimbots" or "targets" room in any of these servers. https://www.battlemetrics.com/servers/rust/6792417 https://www.battlemetrics.com/servers/rust/2068512 https://www.battlemetrics.com/servers/rust/3752176 It seems everything in the game is affected by FOV change including 8x and 16x scopes

I understand now

Oh for some reason I had this idea that putting the FOVs you listed into "Rust hipfire" in the calculator wouldn't give me the correct sens, woops. Ok well I understand how you got all your numbers now so I'm pretty much set. Thanks for sharing this. I'm still curious about this one thing. Where did you get 75vFoV и 65vFoV from and how did you know that this specifically applies to bow, m92, etc.?

What is the number in parentheses next to your sens supposed to be? Also could you share yaws that you used for these calculations?

Oh, it actually works when i type it into the console manually, but binding it to something doesn't seem to work for me. I tried bind 6 "exec rifle.cfg" and bind 6 "global.exec rifle.cfg" and neither worked.

I think I followed what you said exactly but when I press the bind in-game it doesn't do anything. I'm supposed to put rifle.cfg in Steam\steamapps\common\Rust\cfg correct?

@DPI Wizard Oh wow thanks. I actually forgot the calculator included the FOVs for the scopes as well for some reason lol.

Speaking of FOV, how would I go about finding the exact cl_fovscale if I want to match Overwatch's 103 FOV to Apex's 1x scopes rather than Apex's hipfire. Looking at this website it seems like 1.4438ish is probably super close already but it bothers me that I can't find out the exact cl_fovscale.

So before the "Multiplier" option was added in the calculator for Apex I tried to convert my 103 FOV in Overwatch to the cl_fovscale value myself, and 1.22868960125 was the number I got. It seemed to be the correct number because 103 Hdeg Res = 86.631971 Hdeg 4:3 = 1.22868960125 in the config. It seemed correct because when I tried to convert 10 Overwatch sens to Apex with my Apex FOV set to 86.631971 (Hdeg 4:3) in the calculator (MDH 0%) I got a perfect 3.000000 sensitivity instead of 3.000001 or something and that's what I based the 86.631971 number on lol. Now that "Multiplier" is an option, when I convert from 103 Hdeg Res it gives me cl_fovScale "1.2376". My 1.22868960125 value also converts to 102.3903 (Hdeg Res). Also, with 1.2376 (Multiplier) in the calculator, it gives me 3.000001 Apex sensitivity. I'm just curious why the correct conversion just so happens to be 1.2376 FOV with 3.000001 sens instead of 1.22868960125 FOV with 3.000000 sens.