Apex Legends

2 hours ago, zaiem93 said:

Hai, so i was watching fov to get 1 on 1 for ads zoom sens in apex, 

Apparently if i have cl_fovscale on 1.285714 the ads will match at 1 for the zoom scale sens, but if i put 1.28571 as the fov scale multiplier it becomes 1.000005

but lowering fov scale should in fact decrease the zoom scale sens not put it higher with monitor distance on no ? what's the formula behind this ?  

 

 

with 0% which is what we consider to be 1:1

1.0 ads in apex is 0% the reason it shows you slightly different number is because of apex and its rounding being off  this isnt something you have to worry about unless you wna t the exact numbers in which case you can simply change your ads numbers to fit those updated numbers in their respective config files .

use the fov you like  and adapt your settings or simply use 1.0

10 hours ago, DPI Wizard said:

Apex annoyingly rounds the input FOV to the nearest whole number before doing the calculation. This is just for the sensitivity calculation though, the actual FOV stays the same.

What i wanna know is what is the real number with monitor distance at 0% on for mouse_zoomed_sensitivity_scalar_0 "1.000005" if the fov is 1.28571, hence why i'm asking the formula behind that calculation is because i can put up to 489 digit in the settings.cfg file for sens values but your website limit it to 7 in total.  I want it to be as much precise as possible.

From what i've seen changing the FOV scale value have impact on the ADS values, and i think there is a mistake with the website value, why i'm saying the mouse_zoomed values should be lower than 1 when changing the fov is because, for a hipfire sens value from fov 1.285714 to 1.28571 i see the hipfire sens decreasing to 0.999995 with monitor distance at 0% but somehow for mouse_zoomed it goes higher from 1 to 1.000005 ? it's not logical for me.  i think the website calculation is wrong there no ? if you lower the fov scale it should lower zoomed sens as well as it is lowering for the hipfire sens.

I would love to put cl_fovscale 1.285714285714285714285714285714285714285714285714285714285714... and leave the zoomed values to 1 but the apex dev's doesnt let us put more digit than 1.28571 for that value...

How do I convert my 1x sens to 1:1 with my 2x sens in apex?

and how do I convert my 1x sens in apex to csgo hipfire

Apex Sens 1x:
Hipfire 1.9
1x zoom 1.12

Converted to CSGO Hipfire sens is? I would appreciate pictures that show how you calculate this to learn

@DPI Wizard

Im not getting any replies on my threads or even here. Been posting for soon 24 hours on this thread and made own threads aswell without any progress.

32 minutes ago, DPI Wizard said:

It depends on what you mean by 1:1, as you can only match one aspect of the sensitivity. 360 distance, tracking speed, flick distance etc.

flick distance and tracking speed, how would I go about doing that. Want to know how to try both one each.

Why is Apex Legends now listed as not being FOV affected when it use to be listed as that? 

So I'm back at it again and I've started considering doing aim training to improve mechanically in game.

Currently I have a 1.75 hip fire sensitivity a cl_fovScale of "1.47143" and every scope matched at 1.0

I started doing aim training just using the 1.75 or the 11.6883 inches/360 distance for my hip firing... but I realise I actually almost never hip fire if I can help it. And I'm wondering if it makes more sense to train at the 1x/ads sensitivity of 14.6147 inches/360 distance since this is likely what I'll be using more.

Also, if I do start training at that 14.6147 inches/360 distance what kind of implications does that actually have for all my other sensitivities? In some sense... my 1x 2x 4x 8x are all theoretically some ratio of my hipfire sensitivity. So if I start training at that 1x sensitivity what kind of horrors, if any, does that do to my 2x sensitivity/4x sensitivity so on....

Also kind of wondering if maybe there's a way out there somehow to make my hipfire and my 1x the same.... but have every other scope a 1:1 ratio of that. (I'm guessing probably not since there's some FoV magic/weirdness probably going on here that I'm not considering)

What are people's recommendations and thoughts?

Quote

So if I start training at that 1x sensitivity what kind of horrors, if any, does that do to my 2x sensitivity/4x sensitivity so on....

Quote

but have every other scope a 1:1 ratio of that. (I'm guessing probably not since there's some FoV magic/weirdness probably going on here that I'm not considering

You are, unfortunately, right on the money. There is horror, and it is due to the FOV magic/weirdness.

TL;DR if you're using MDV 0%, the horror is that at lower FOVs/higher zooms, the parts of the screen that are far away from the center will become slower and slower.

At low FOVs/zooms (in other words, hipfire), the center of your screen moves very slowly and the edges of your screen move very fast. At high FOVs/zooms, all parts of your screen move roughly the same speed. Therefore, you can only ever match the speed of your screen at some set distance from the center:

• The recommended choice is to match the speed of your aiming reticle at every zoom level (otherwise known as MDV 0%), because if you can only train muscle memory for one part of your screen, the reticle seems like the obvious choice. However, because the center of your screen is the slowest part, as a consequence the speed of the edges of your screen are drastically mismatched. As you zoom in more, your sensitivity for the majority of your screen will slow down.
• The other common choice is to match the speed of a circle of pixels whose radius is 75% of the horizontal distance from your reticle to the edge of the screen:
  
  This is how counterstrike and battlefield do it by default. The circle is a nice distance from both the edges and the center. It basically tries to minimize the mismatch, so neither your screen edges nor your reticle are that mismatched. As a consequence, your sensitivity feels roughly the same at all zoom levels.
  However, this is not recommended - it feels good, but in reality, only the pixels that lie along the red circle have a 1:1 ratio at every sensitivity, so that part of the screen is the only part you can truly build muscle memory for. This is arguably useless - how often do you need these exact pixels to move the correct distance?

The reality of the situation is that you have to train your aim on every FOV/zoom individually to truly gain the muscle memory - you can't train on just one FOV. However, you can cheat a ring of pixels of your choosing, and gain muscle memory for that ring of pixels for all FOVs. Arguably the most important pixels are the center, which is why I recommend MDV 0%.

Also, for some reason, Apex's rifle/lmg/sniper zoom sensitivity setting is the same as the smg/shotgun/pistol ironsights sensitivity setting, despite the two having different FOVs: This means that if you choose to not use MDV 0%, then either your rifle/lmg/sniper ironsights or your smg/shotgun/pistol ironsights sensitivity will be incorrect.

On 8/26/2021 at 12:03 AM, KimiNoKataware said:

You are, unfortunately, right on the money. There is horror, and it is due to the FOV magic/weirdness.

TL;DR if you're using MDV 0%, the horror is that at lower FOVs/higher zooms, the parts of the screen that are far away from the center will become slower and slower.

At low FOVs/zooms (in other words, hipfire), the center of your screen moves very slowly and the edges of your screen move very fast. At high FOVs/zooms, all parts of your screen move roughly the same speed. Therefore, you can only ever match the speed of your screen at some set distance from the center:

• The recommended choice is to match the speed of your aiming reticle at every zoom level (otherwise known as MDV 0%), because if you can only train muscle memory for one part of your screen, the reticle seems like the obvious choice. However, because the center of your screen is the slowest part, as a consequence the speed of the edges of your screen are drastically mismatched. As you zoom in more, your sensitivity for the majority of your screen will slow down.
• The other common choice is to match the speed of a circle of pixels whose radius is 75% of the horizontal distance from your reticle to the edge of the screen:
  
  This is how counterstrike and battlefield do it by default. The circle is a nice distance from both the edges and the center. It basically tries to minimize the mismatch, so neither your screen edges nor your reticle are that mismatched. As a consequence, your sensitivity feels roughly the same at all zoom levels.
  However, this is not recommended - it feels good, but in reality, only the pixels that lie along the red circle have a 1:1 ratio at every sensitivity, so that part of the screen is the only part you can truly build muscle memory for. This is arguably useless - how often do you need these exact pixels to move the correct distance?

The reality of the situation is that you have to train your aim on every FOV/zoom individually to truly gain the muscle memory - you can't train on just one FOV. However, you can cheat a ring of pixels of your choosing, and gain muscle memory for that ring of pixels for all FOVs. Arguably the most important pixels are the center, which is why I recommend MDV 0%.

Also, for some reason, Apex's rifle/lmg/sniper zoom sensitivity setting is the same as the smg/shotgun/pistol ironsights sensitivity setting, despite the two having different FOVs: This means that if you choose to not use MDV 0%, then either your rifle/lmg/sniper ironsights or your smg/shotgun/pistol ironsights sensitivity will be incorrect.

So one thing I question about this....

I'm assuming that with MDV 0% the pixels closest to the cursor are close, but are not all actually 1:1 and then just magically not 1:1 past a certain distance right?

So if the 75% distance thing feels good, but also isn't precise or exactly 1:1 is there really that much more of a drawback to using it?

I swear I'm not trying to pick a fight, I just kind of feel like I'm slowly reaching the despair/conclusion that maybe it's actually impossible to be precise or build a full true muscle memory profile, and maybe just maybe... whatever feels good is the better sensitivity to use. <_>

------------------------------------------------

thinking about this more....

If I play in a 3440x1440 resolution...

and say a 1x zoom cuts my screen by X percentage, wouldn't it be better to match the distance by that cut percentage, because in theory that would be the closest approximation to all points on the screen? Is that what mdv 100% does internally?

6 hours ago, BustyLoliChan said:

MDV 0% the pixels closest to the cursor are close, but are not all actually 1:1 and then just magically not 1:1 past a certain distance right

what you are describing here is closer to what happens at most other values

what 0%(focal length or zoom ratio) does is matching the zoom giving you a similar experience independent of the fov while not rely ing strictly on one point   which is in theorie much more mathematicallysound than most other values.

------------------------------------ this part below is just an my opinion------------------------

in my experience  mdh 100 / mdv 100 or other values tends to give you an easier initial feel making many feeel like they are " better " because they are distance based and you dont have te get used to a new system of  Sens but they end up not really benefitting you as much as getting used to 0% would

the only downsight really is that different 1x scopes zoom different amounts so going fully distance based is misguided when you should focus more on the zoom aspect

--------------------------------------------------------also ---------------------------

6 hours ago, BustyLoliChan said:

maybe it's actually impossible

there is no magic pill that will make you better if you arent willing to put in the effort of learning the games you are playing / recoil patterns gunplay

you might be looking at it from the wrong perspective if this was your thought.

---------------------------

iy you want a more natural feel take takes both distance and velocity into acc you could try using accel

I basically agree with Fortunate Ree.
 

Quote

I swear I'm not trying to pick a fight

No worries.

Quote

I'm assuming that with MDV 0% the pixels closest to the cursor are close, but are not all actually 1:1 and then just magically not 1:1 past a certain distance right?

Correct.

Every pixel on your screen has the same angular sensitivity. This is true because, if you spin your camera in a full circle, every pixel will have traveled 360 degrees, not just the one in the center. If this weren't true, then every time you spun in a circle, your screen would get all fucked up, with different pixels not completing the full 360 degree turn and ending up in their original location.

However, angular sensitivity isn't important. What is is the linear sensitivity. How do we get linear sensitivity from angular sensitivity? Well, if we spin in a full circle, then we have a circle, and we turn to our good friend, Circumference = 2 * pi * radius:

angular sensitivity of each pixel = (360 degrees)/(mouse distance required to spin in a circle)
linear sensitivity of a pixel = (Distance that pixel has traveled during the spin)/(mouse distance required to spin in a circle)
linear sensitivity of a pixel = (2*pi*radius)/(mouse distance required to spin in a circle)

That seems like a lot, but we don't actually care about most of that. The whole point of that is to isolate what exactly makes two pixels have different linear sensitivities - the only difference would be the radius.
That is, the linear sensitivity of any given pixel is based on its 'radius', or rather, the distance of that pixel from the camera. Finding the difference between two pixel's sensitivities is basically just comparing how far each pixel is away from the camera.
Do note that 'the camera' is not 'your eye'. We have to calculate the radii based off of FOV.

First, we find the radius of the pixel under the reticle:

  

That is, (Radius of center) = X/(tan(FOV/2))

Now, for the radius of any other pixel:
 

(Radius of center)/(Radius of other pixel) = cos(theta)
theta = arctan(Y/(Radius of Center))
theta = arctan( (Y/X)*tan(FOV/2))

(Radius of center)/(Radius of other pixel) = cos(arctan( (Y/X)*tan(FOV/2))


And this is the calculation for the difference in sensitivities between the reticle any spot on your screen, in hipfire, for Apex legends.

If you're curious about different zoom levels besides hipfire, the difference would be the choice of FOV and X.

But you probably don't care about all of that, lol. The important part is the cosine function: the ratio of speed between the center pixel and any other pixel is a cosine function that starts at zero and increases in value as you move further and further away from the center pixel. If you choose really small values for Y, then cosine of a small number is nearly 1 - this is what you intuitively understood to be, "the pixels closest to the cursor are close, but are not all actually 1:1".
 

Quote

Is that what mdv 100% does internally?

What MDV 100% does internally is, "It will take the exact same amount of mouse movement to aim at something at the top-center or bottom-center of my screen, no matter how zoomed in I am". In other words, draw a circle around your reticle that barely fits inside your screen. Now imagine you trained your muscle memory perfectly for hipfire at this setting, such that you shroud style insta snap to foreheads in hipfire. This means that, no matter what scope you are at, you now have muscle memory for insta-snapping to foreheads as long as they lie along or near this circle. At pixels closer to your reticle, and your hipfire muscle-memory will overshoot at high zoom levels. A pixels further away, your hipfire muscle memory will undershoot at high zoom levels.

The idea behind MDV 0% is two-fold:
1. say you over or under shoot and barely miss some guy's forehead - now that your reticle is close to their head, the MDV 0% muscle memory will kick in and your next shot will be legit.

2. say you are aiming at some guy and they start moving. At MDV 0%, the speed of your reticle will always be the same. Your muscle memory will help you stay on the guy as they crouch strafe.

At least, that's how its supposed to be. To gain true snap-on-heads accuracy at every pixel, every zoom will still require hard work no matter what you choose. But picking an MDV allows you to cheat certain pixels at every zoom level.
 

4 hours ago, KimiNoKataware said:

foreheads as long as they lie along or near this circle

problem with this will always be when your crosshair is not centered at the initial point of your snap that wont be the case and adjsutment s mid flick wont be trained ( a big reason to go against the whole flicking is good aiming theory) while being able to hit shroud like flicks is considered an impressive feat its not actually good aim in the sens of consistency that might not be as flashy as the previously mentioned flick heavie style but prove more efficient overall .

4 hours ago, KimiNoKataware said:

cheat certain pixels at every zoom level

that actually is a nice description for the " higher mdv/ mdh values initially feel better" arguemnt that has been made in the past since you have got that one point of accuravy instead of a truely uniform this makes you think that you aim better while allowing you to ignore the benefits of 0%

i dont like the use of the term muscle memory since its oftwen miss used or missinterpreted in gaming apart from that this is retty accurate

Was there a recent change to Apex or is my calculator bugged? On MDH 0 the calculator tells me to use an ADS of 1.009xxx for all of my sights, but in the past it would always say 1. (I've check and my Hipfire and FOV are the same, so I didnt misinput anything.)

21 minutes ago, SpeedySteve said:

Was there a recent change to Apex or is my calculator bugged? On MDH 0 the calculator tells me to use an ADS of 1.009xxx for all of my sights, but in the past it would always say 1. (I've check and my Hipfire and FOV are the same, so I didnt misinput anything.)

its a weird rounding thing apex does, this has nothing to do with your settings

its miniscule so you wont notice much of a difference to begin with

If I want to match the tracking speed and/or flick of my Modern Warfare settings to Apex, what would be the correct setting?

Is this correct? https://www.mouse-sensitivity.com/?share=e89358cbdb5852351e18048a920d325f

If I have to choose between which aim to prioritize, I mainly use ironsights/mini-reflex on SMG's and AR's on Modern Warfare 2019 if that helps.

I'm hoping to improve my tracking speed/target acquisition with Apex.

I use monitor distance 0% in conversion. Is the number "1.008953" accurate? Default value is "1".

mouse_zoomed_sensitivity_scalar_0 "1.008953" (1X Scope / ADS (SMG, SG, Pistol))
mouse_zoomed_sensitivity_scalar_0 "1.008953" (ADS (AR, LMG, Sniper))
mouse_zoomed_sensitivity_scalar_1 "1.008953"
mouse_zoomed_sensitivity_scalar_2 "1.008953"
mouse_zoomed_sensitivity_scalar_3 "1.008953"
mouse_zoomed_sensitivity_scalar_4 "1.008953"
mouse_zoomed_sensitivity_scalar_5 "1.008953"
mouse_zoomed_sensitivity_scalar_6 "1.008953"

According to the previous answer, if my fov is an integer, this value will become exactly 1, right? Looks like 105 (multiplier 1.5) is a good choice.

Another question: Is it necessary to set the parameter "mouse_use_per_scope_sensitivity_scalars" to 1?