dsu

Name: Deadlock
Website: n/a
Status: alpha
Release date: n/a
Availability: invite only

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

turn speed modifiers are getting removed

14 hours ago, DPI Wizard said:

Added everything now into one calculation so it's easy to pick out what you want.

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.

14 minutes ago, DPI Wizard said:

I'll see if I can add all these. I won't be able to verify them myself since this game lacks a training mode as far as I know.

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

15 minutes ago, DPI Wizard said:

You mean just the 8X and 16X right? The rest is affected by FOV change?

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.

31 minutes ago, Vaccaria said:

1.1538461539 - multiplier between 75vFoV и 65vFoV

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.?

9 hours ago, Vaccaria said:

Made my calculations for my settings. The principle is one. Maybe someone will come in handy. "Simple Handmade Sight" needs to be calculated for each FOV weapon the multiplier is not accurate, there is a small error. Changed the command for the console so that the RMB is not deleted.

 

New Text Document.txt 3.16 kB · 1 download

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

3 hours ago, SmokingYoda said:

Yes, make sure you include filetype, example; "global.exec rifle.cfg" without quotation marks.

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.

On 11/8/2020 at 1:12 PM, SmokingYoda said:

You can also make config file and bind exec for it, this way you can in theory switch sensitivities on-the-fly.

 

Create 'rifle.cfg' file to Rust cfg -folder.

* 'rifle.cfg' will need contain following: bind mouse1 “+sensitivity <hip-fire sensitivity>;sensitivity <ADS sensitivity>;+attack2” *
bind 6 “exec rifle.cfg”

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.