Apex Legends

[strreamix]

On 2/5/2019 at 10:57 AM, DPI Wizard said:

Config file is added, which supports at least 6 decimals.

Also updated with holo, 6x and 10x.

It is a bit inaccurate, which is why scope calculations will be off by a few counts.

When I add the 6 decimals in the config file and load game, it rounds to the nearest single decimal?

Am I getting the actual cfg sensitivity or the menus sensitivity?

For example, I enter "0.385672" into the config and inside the game I am shown 0.4 in the mouse/keyboard menu. I figured it would atleast round to 0.39? 

(I set the game to 0.2, then set cfg to 0.385672, then opened game, and it rounded to 0.4) -- Just to make sure cfg file was working.

Thank you.

[epitome89]

4 hours ago, Oofta said:

So I think I'm doing this correct? If my CSGO sens is 2.01 then my Apex is 2.01 if I play with 90 FOV?

Yes, but the ingame FOV-slider seems off, so you should do 90 / 70 = cl_fovScale "1.2857" in the C:\Users\[your user]\Saved Games\Respawn\Apex\profile\profile.cfg

[Oofta]

1 hour ago, epitome89 said:

Yes, but the ingame FOV-slider seems off, so you should do 90 / 70 = cl_fovScale "1.2857" in the C:\Users\[your user]\Saved Games\Respawn\Apex\profile\profile.cfg

Will do. Thank you!

[cammie]

Do the different mouse sens scalars eg:

mouse_zoomed_sensitivity_scalar_0 "1.0"
mouse_zoomed_sensitivity_scalar_1 "1.0"
mouse_zoomed_sensitivity_scalar_2 "1.0"
mouse_zoomed_sensitivity_scalar_3 "1.0"
mouse_zoomed_sensitivity_scalar_4 "1.0"
mouse_zoomed_sensitivity_scalar_5 "1.0"

affect different scopes? If so what scalar is responsible for which scope. Thanks!-+-

[syncfx]

6 hours ago, epitome89 said:

Yes, but the ingame FOV-slider seems off, so you should do 90 / 70 = cl_fovScale "1.2857" in the C:\Users\[your user]\Saved Games\Respawn\Apex\profile\profile.cfg

Does this include different games outside of source engine? Like Fortnite or PUBG.  Or does the cl_fov not matter

[The Archlich]

22 hours ago, DPI Wizard said:

Tell me what are your settings in PUBG and BFV? Because if you have the same 360 distance on hipfire and 15x/10x scopes you have a very special preference.

Yes, you cover the same degrees pr. inch mouse movement, but with for instance the 15x scope in PUBG your entire screen only covers 6.67 degrees compared to (usually) 103 degrees in first person hipfire. This means that if moving the crosshair 10 inches on the monitor require 1.6 inches in hipfire it will only require 0.1 inches with 15x scope if the 360 distance is the same. And that is insanely fast.

It's twice slower for the 15x (12x actually) for me, cause it went out of scale, but it never drops anyway (I have almost 900 hours and I got it once). All other scopes match ADS on 360 distance.

I use:

1.0101inch 360 distance for Hipfire

2.2957inch 360 distance for ADS, 2x, 3x ,4x ,6x, 8x

6.8871inch 360 distance for ADS, 2x, 3x ,4x ,6x, 8x with DPI shift

4.5914inch 360 distance for 15x

13.7742inch 360 distance for 15x with DPI shift (though I don't think ever actualy used it)

 

Mouse base DPI = 3600

Mouse DPI shift = 1200

Hipfire FOV = 103

MouseSensitiveList=

Spoiler

 

((MouseSensitiveName="Normal",MouseSensitivity=67.000000,LastConvertedMouseSensitivity=0.034605),

(MouseSensitiveName="VehicleDriver",MouseSensitivity=67.000000,LastConvertedMouseSensitivity=0.034605),

(MouseSensitiveName="Targeting",MouseSensitivity=67.000000,LastConvertedMouseSensitivity=0.034605),

(MouseSensitiveName="Scoping",MouseSensitivity=67.000000,LastConvertedMouseSensitivity=0.022405),

(MouseSensitiveName="Scope2X",MouseSensitivity=67.000000,LastConvertedMouseSensitivity=0.035287),

(MouseSensitiveName="Scope4X",MouseSensitivity=67.000000,LastConvertedMouseSensitivity=0.078416),

(MouseSensitiveName="Scope8X",MouseSensitivity=67.000000,LastConvertedMouseSensitivity=0.142129),

(MouseSensitiveName="Scope15X",MouseSensitivity=67.000000,LastConvertedMouseSensitivity=0.117624),

(MouseSensitiveName="Scope3X",LastConvertedMouseSensitivity=0.058812),

(MouseSensitiveName="Scope6X",LastConvertedMouseSensitivity=0.117624))

 

 

PS: I don't have BFV, I just now it can do it.

Edited February 8, 2019 by borysn

[faveya]

Hey  , maybe someone can help me . im pretty new to all this sensitivity stuff. So im coming from CSGO playing on 400dpi , 2.15 ingsens , 0.89 zoomsens . so i used the calculator and it says for apex same sensitivity for hipfire . But i dont get it how i can calculate my 0.89  ( SG 553 / AUG ) zoomsens to the apex zoom sens. Hope someone can help me . Sry for my bad english its not my main language

[stereo3D]

1 hour ago, faveya said:

Hey  , maybe someone can help me . im pretty new to all this sensitivity stuff. So im coming from CSGO playing on 400dpi , 2.15 ingsens , 0.89 zoomsens

setting everything to MDV 76.9488 % in the conversion setup, results in 

zoom_sensitivity_ratio_mouse "0.890000" for csgo and

mouse_zoomed_sensitivity_scalar_0 "1.046497"  for apex legends.

[Rakzix]

i play fortnite in 1440x1080, what should use fov in apex legends?

Edited February 8, 2019 by Rakzix

[Pyroxia]

is it possible to adjust my Hfov 106.52 in config file? (90.27)

[DPI Wizard]

10 minutes ago, Pyroxia said:

is it possible to adjust my Hfov 106.52 in config file? (90.27)

Set it to 1.289571.

[Pyroxia]

2 minutes ago, DPI Wizard said:

Set it to 1.289571.

ah ok thank you wizard

[Drimzi]

On 2/9/2019 at 9:19 AM, stereo3D said:

setting everything to MDV 76.9488 % in the conversion setup, results in 

zoom_sensitivity_ratio_mouse "0.890000" for csgo and

mouse_zoomed_sensitivity_scalar_0 "1.046497"  for apex legends.

I don't think it's that easy, since Apex is not scaling the 360° distance using angles like CS:GO. This won't replicate anything.

 

On 2/9/2019 at 7:34 AM, faveya said:

Hey  , maybe someone can help me . im pretty new to all this sensitivity stuff. So im coming from CSGO playing on 400dpi , 2.15 ingsens , 0.89 zoomsens . so i used the calculator and it says for apex same sensitivity for hipfire . But i dont get it how i can calculate my 0.89  ( SG 553 / AUG ) zoomsens to the apex zoom sens. Hope someone can help me . Sry for my bad english its not my main language

 

With your settings, when you zoom, your zoom sensitivity is faster than the hipfire sensitivity by a factor of:

SG 553 / AUG = 1.07433...
Zoomed 1: AWP, SSG 08, G3SG1, SCAR-20  = 1.08678...
Zoomed 2: SSG 08, G3SG1, SCAR-20 = 1.12670...
Zoomed 2: AWP = 1.13031...

You effectively have 4 different zoom sensitivities (that don't have any correlation to each other in terms of feel). You can try one of these values directly, or alternatively, you can replicate the scaling behaviour.

 

Assuming Apex is at 90 fov (cl_fovScale 1.285714) to match CS:GO, these will be the values that replicates CS:GO's scaling system with your 0.89 multiplier:

Holo (77.14 fov) = 0.956606...
ADS (70.71 fov) = 0.985569...
6x Scope (17.12 fov) = 1.12474...
10x Scope (10.3 fov) = 1.13013...

Averaged Magnification (47.2 fov) = 1.06836...

Since you can't set a unique value for every weapon, you just have to settle for one of them. If you match Holo or ADS, the Scopes will be slower than CS:GO. If you match to Scopes, the Holo & ADS will be too fast. A compromise will be to use the averaged magnification, which will be the most balanced option. Choice is up to you whether or not to make one weapon perfect, or balance all weapons.

 

Either choose the direct sensitivity multiplier that you have been using in CS:GO (the first box of values), or choose a sensitivity multiplier that uses the CSGO scaling method (second box of values).

 

Calculations:

SG 553 / AUG = 0.89 * 45/90 * tan(90 * pi/360)/tan(45 * pi/360)
Zoomed 1: AWP, SSG 08, G3SG1, SCAR-20  = 0.89 * 40/90 * tan(90 * pi/360)/tan(40 * pi/360)
Zoomed 2: SSG 08, G3SG1, SCAR-20 = 0.89 * 15/90 * tan(90 * pi/360)/tan(15 * pi/360)
Zoomed 2: AWP = 0.89 * 10/90 * tan(90 * pi/360)/tan(10 * pi/360)


Holo (77.14 fov) = 0.89 * 77.14/90 * tan(90 * pi/360)/tan(77.14 * pi/360)
ADS (70.71 fov) = 0.89 * 70.71/90 * tan(90 * pi/360)/tan(70.71 * pi/360)
6x Scope (17.12 fov) = 0.89 * 17.12/90 * tan(90 * pi/360)/tan(17.12 * pi/360)
10x Scope (10.3 fov) = 0.89 * 10.3/90 * tan(90 * pi/360)/tan(10.3 * pi/360)

Averaged fov = (360 * atan(1/4 * (tan(10.3 * pi/360) + tan(17.12 * pi/360) + tan(70.71 * pi/360) + tan(77.14 * pi/360))))/pi

 

Edited February 10, 2019 by Drimzi

[strreamix]

@DPI Wizard Any chance you can help with my question above? I'll copy it here to make it easier.

 

When I add the 6 decimals in the config file and load game, it rounds to the nearest single decimal?

Am I getting the actual cfg sensitivity or the menus sensitivity?

For example, I enter "0.385672" into the config and inside the game I am shown 0.4 in the mouse/keyboard menu. I figured it would atleast round to 0.39? 

(I set the game to 0.2, then set cfg to 0.385672, then opened game, and it rounded to 0.4) -- Just to make sure cfg file was actually working.

Thank you.

[DPI Wizard]

Just now, strreamix said:

@DPI Wizard Any chance you can help with my question above? I'll copy it here to make it easier.

The values in the config files are the ones that are actually applied. The menus show wrong values, like so many other games. It's quite incredible that so many companies mess this up tbh!

Just like the default FOV, it shows 90 in the menus but it's actually 89.0512035...

[Lunis]

Does anyone know if there is an option for Raw Input?  It feels like it's not on by default.

My fast swipes do not end up in the exact same place everytime... there's definitely some acceleration even with it turned off in the options.

[Angst!]

Casuals don't seek this level of precision. The depth of these calculations are only truly needed for the preservation of head shot aim across varying scope and ADS FOV's and developer sensitivity scales. Coding this game in the Source engine took that headache away for everyone except the Fortnite and Overwatch kids who've never played CS or Quake.

If you can only body shot, three digits will suffice. You probably wouldn't even realize that it was off. 

 

 

[DPI Wizard]

14 minutes ago, Lunis said:

Does anyone know if there is an option for Raw Input?  It feels like it's not on by default.

My fast swipes do not end up in the exact same place everytime... there's definitely some acceleration even with it turned off in the options.

If you have the mouse acceleration setting off that should do it, raw input is on by default with no option to turn it off I think. I haven't really stress-tested it with rapid movement yet, but everything I've tested with "medium speed" was acceleration free.

BTW, what DPI and sens are you using?

[Angst!]

13 minutes ago, Lunis said:

Does anyone know if there is an option for Raw Input?  It feels like it's not on by default.

My fast swipes do not end up in the exact same place everytime... there's definitely some acceleration even with it turned off in the options.

Yes, I think their toggle is broken for accel as well. I was thinking of downloading povohat's driver and using the command line exe in game to see if it detects any acceleration. I don't know if it only detects the driver's accel though?

[DPI Wizard]

Just did some tests now with the equivalent of about 312 inches/sec at 400 DPI and it had zero packet loss and no acceleration. It was dead on pixel perfect every time.

And" acceleration on" had a huge impact like expected.

Other factors like vsync, drivers and hardware might impact this though, but I can't detect any issues here.

[Angst!]

7 hours ago, DPI Wizard said:

Just did some tests now with the equivalent of about 312 inches/sec at 400 DPI and it had zero packet loss and no acceleration. It was dead on pixel perfect every time.

And" acceleration on" had a huge impact like expected.

Other factors like vsync, drivers and hardware might impact this though, but I can't detect any issues here.

I had updated the gpu driver and it defaulted Nvidia control panel settings.

[stereo3D]

@Drimzi i also thought about calculating MDH 75 % and multiplying that with 0.89 to match csgo's behaviour, but i'm not sure if it's necessary or even all that useful to replicate something the user never experienced in the first place.

we don't know if he would have ended up with 0.89 if the zoomFOV in csgo was ~77 instead of 40 and since the results for ADS and holo are slower than even MDH 0 % i'm not sure if doing it like this is such a good idea.

Edited February 9, 2019 by stereo3D

[faveya]

12 hours ago, Drimzi said:

I don't think it's that easy, since Apex is not scaling the 360° distance using angles like CS:GO. This won't replicate anything.

 

 

With your settings, when you zoom, your zoom sensitivity is faster than the hipfire sensitivity by a factor of:

SG 553 / AUG = 1.07433...
Zoomed 1: AWP, SSG 08, G3SG1, SCAR-20  = 1.08678...
Zoomed 2: SSG 08, G3SG1, SCAR-20 = 1.12670...
Zoomed 2: AWP = 1.13031...

As you can tell, it's different for each weapon. Increasing as the fov decreases. To carry over to Apex, you absolutely must scale to Apex's weapons.

 

Assuming Apex is at 90 fov (cl_fovScale 1.285714) to match CS:GO, these will be the values that replicates CS:GO's scaling system with your 0.89 multiplier:

Holo (77.14 fov) = 0.956606...
ADS (70.71 fov) = 0.985569...
6x Scope (17.12 fov) = 1.12474...
10x Scope (10.3 fov) = 1.13013...

Averaged Magnification (47.2 fov) = 1.06836...

Since you can't set a unique value for every weapon, you just have to settle for one of them. If you match Holo or ADS, the Scopes will be slower than CS:GO. If you match to Scopes, the Holo & ADS will be too fast. A compromise will be to use the averaged magnification, which will be the most balanced option. Choice is up to you whether or not to make one weapon perfect, or balance all weapons.

 

 

Calculations:

SG 553 / AUG = 0.89 * 45/90 * tan(90 * pi/360)/tan(45 * pi/360)
Zoomed 1: AWP, SSG 08, G3SG1, SCAR-20  = 0.89 * 40/90 * tan(90 * pi/360)/tan(40 * pi/360)
Zoomed 2: SSG 08, G3SG1, SCAR-20 = 0.89 * 15/90 * tan(90 * pi/360)/tan(15 * pi/360)
Zoomed 2: AWP = 0.89 * 10/90 * tan(90 * pi/360)/tan(10 * pi/360)


Holo (77.14 fov) = 0.89 * 77.14/90 * tan(90 * pi/360)/tan(77.14 * pi/360)
ADS (70.71 fov) = 0.89 * 70.71/90 * tan(90 * pi/360)/tan(70.71 * pi/360)
6x Scope (17.12 fov) = 0.89 * 17.12/90 * tan(90 * pi/360)/tan(17.12 * pi/360)
10x Scope (10.3 fov) = 0.89 * 10.3/90 * tan(90 * pi/360)/tan(10.3 * pi/360)

Averaged fov = (360 * atan(1/4 * (tan(10.3 * pi/360) + tan(17.12 * pi/360) + tan(70.71 * pi/360) + tan(77.14 * pi/360))))/pi

 

@Drimzi 

thank you man ! i guess im going with the 1.06 but i still have one question about "fov" so in csgo viewmodel doesnt matter to fov if im right so im playing on both games 16:9 1080p , so csgo fov is always 90. Do i have just to set 90 fov aswell in apex ( ingame menu) ? because i cant find "cl_fovScale 1.285714" in my configs not in csgo and not in apex. im confused

Edited February 9, 2019 by faveya

[stereo3D]

%USERPROFILE%\Saved Games\Respawn\Apex\profile\profile.cfg

[Motarde]

mouse_zoomed_sensitivity_scalar_1 "1.0"
mouse_zoomed_sensitivity_scalar_2 "1.0"
mouse_zoomed_sensitivity_scalar_3 "1.0"
mouse_zoomed_sensitivity_scalar_4 "1.0"
mouse_zoomed_sensitivity_scalar_5 "1.0"

Do we have to change these?