Questions about Sens and FOV.

[KLAZMOI]

Hi!

I was trying to understand Monitor Distance Matching, and questions about Sens and Fov popped up in my mind so I need a second opinion.

If I am practicing my aim in Kovaak's, with sens being 10, Fov being 80, i am aiming two pixels that are 3 cm (mouse movement, not monitor distance) apart:

 so If I don't change my sensitivity, but change my Fov from 80 to 30, even though moving around with the same sensitivity feels faster/more shaky, but I still only need to move exactly 3 cm (mouse movement) to switch between the pixels. Is this correct?

Any feedback would be appreciated

 

 

Edited January 18, 2020 by KLAZMOI

[fortunate reee]

28 minutes ago, KLAZMOI said:

Hi!

I was trying to understand the monitor distance matching, and questions about Sens and Fov popped up in my mind so I need a second opinion.

If I am practicing my aim in Kovaak's, with sens being 10, Fov being 80, i am aiming two pixels that are 3 cm (mouse movement, not monitor distance) apart:

 so If I don't change my sensitivity, but change my Fov from 80 to 30, even though moving around with the same sensitivity feels faster/more shaky, but I still only need to move exactly 3 cm (mouse movement) to switch between the pixels. Is this correct?

Any feedback would be appreciated

 

 

i generally like to match my fov to stay close to csgo so i do not really struggle with that anymore .

but i used to use 360 distance for all options in my early mouse sensitivity . com stage and i got pretty good with it .

However as you already mentioned there is instability connected to this method of conversation ,

since aim is not purely hand eye coordination this method has its limits compared to other options  i still use 360 distance for the equivalent rotation independent of fov and other quirks that might come from games . (different fov for scopes across most games makes it near impossible to perfect aim )

 

generally the consensus is that you want to use monitor distance for your conversions (it allows for far greater consistency compared to a mouse movement based options and Especially fine tuned aim ) 

 

this would be my currently active setup (have recently lowered my sense and have not really suffered from inconsistency )

as mentioned before i like to match "csgo 90 fov " aka 73.74 vertical and 106.26  hor ( using max fov is overrated )

 

i can do about 1 360 when going across my mouse pad ( mouse movement based movement =good)

and my aim is pretty much on point since i use (0%monitor distance) for any aim related effort .

 

if you just want consistent movement in hipfire  360 is the way if you want to retain good hipfire aim you need to match the fov of the game or use monitor distance 

the instructions pretty much teach you most things 

 

 

 

 

 

 

 

 

Edited January 18, 2020 by fortunate reee

[KLAZMOI]

22 minutes ago, fortunate reee said:

i generally like to match my fov to stay close to csgo so i do not really struggle with that anymore .

but i used to use 360 distance for all options in my early mouse sensitivity . com stage and i got pretty good with it .

However as you already mentioned there is instability connected to this method of conversation ,

since aim is not purely hand eye coordination this method has its limits compared to other options  i still use 360 distance for the equivalent rotation independent of fov and other quirks that might come from games . (different fov for scopes across most games makes it near impossible to perfect aim )

 

generally the consensus is that you want to use monitor distance for your conversions (it allows for far greater consistency compared to a mouse movement based options and Especially fine tuned aim ) 

 

this would be my currently active setup (have recently lowered my sense and have not really suffered from inconsistency )

as mentioned before i like to match "csgo 90 fov " aka 73.74 vertical and 106.26  hor ( using max fov is overrated )

 

i can do about 1 360 when going across my mouse pad ( mouse movement based movement =good)

and my aim is pretty much on point since i use (0%monitor distance) for any aim related effort .

 

if you just want consistent movement in hipfire  360 is the way if you want to retain good hipfire aim you need to match the fov of the game or use monitor distance 

the instructions pretty much teach you most things 

 

 

 

 

 

 

 

 

Thank you for your reply!

I understand what to do to be consistent, like you said:

match actual fov between games and match monitor distance 0% for on screen flicks/muscle memory.

But I am still curious about my question mentioned above, it's more for understanding properties of fov and sens:

"If I am practicing my aim in Kovaak's, with sens being 10, Fov being 80, i am aiming two pixels that are 3 cm (mouse movement, not monitor distance) apart:

 so If I don't change my sensitivity, but change my Fov from 80 to 30, even though moving around with the same sensitivity feels faster/more shaky, but I still only need to move exactly 3 cm (mouse movement) to switch between the pixels. Is this correct?   "

What do you think?

[fortunate reee]

25 minutes ago, KLAZMOI said:

Thank you for your reply!

I understand what to do to be consistent, like you said:

match actual fov between games and match monitor distance 0% for on screen flicks/muscle memory.

But I am still curious about my question mentioned above, it's more for understanding properties of fov and sens:

"If I am practicing my aim in Kovaak's, with sens being 10, Fov being 80, i am aiming two pixels that are 3 cm (mouse movement, not monitor distance) apart:

 so If I don't change my sensitivity, but change my Fov from 80 to 30, even though moving around with the same sensitivity feels faster/more shaky, but I still only need to move exactly 3 cm (mouse movement) to switch between the pixels. Is this correct?   "

What do you think?

this whole question makes very little sense in the context of 0%/ focal length matching , that somewhat confuses me  

your question makes it sound like as if you keep swapping values ignoring what the calculator spits out for you if you  (while the fov doesn't matter with 0% you still want to use the proper values if the game / aimtrainer doesnt offer scaling.

 

you should match your main game to kovak and then train 

Edited January 18, 2020 by fortunate reee

[KLAZMOI]

24 minutes ago, fortunate reee said:

this whole question makes very little sense in the context of 0%/ focal length matching , that somewhat confuses me  

your question makes it sound like as if you keep swapping values ignoring what the calculator spits out for you if you  (while the fov doesn't matter with 0% you still want to use the proper values if the game / aimtrainer doesnt offer scaling.

 

you should match your main game to kovak and then train 

So forget about aim training for a second, and forget about using the calculator as well.

The question is not for improving aim training, it's to satisfy my curiosity -- a "what if that's the case, then what would happen" type of question.

Rephrasing and simplifying my question:

"If I need to move my mouse exactly 3 cm between 2 pixel size targets under a sens and fov setting, now if I decrease the fov to 1/10 the value before while the sens remains the same. Do I still only need to move my mouse exactly 3 cm between the 2 pixel size targets".

Edited January 18, 2020 by KLAZMOI

[fortunate reee]

11 minutes ago, KLAZMOI said:

So forget about aim training for a second, and forget about using the calculator as well.

The question is not for improving aim training, it's to satisfy my curiosity -- a "what if that's the case, then what would happen" type of question.

Rephrasing and simplifying my question:

"If I need to move my mouse 3 cm between 2 pixel size targets under a sens and fov setting, now if I decrease the fov to 1/10 the value before, do I still only need to move my mouse 3 cm between the 2 pixel size targets".

this is @Drimzi or @DPI Wizardlevel stuff  

i like using the calculator to improve my aim so that is out of my area of expertise 

Edited January 18, 2020 by fortunate reee

[DPI Wizard]

1 hour ago, KLAZMOI said:

If I am practicing my aim in Kovaak's, with sens being 10, Fov being 80, i am aiming two pixels that are 3 cm (mouse movement, not monitor distance) apart:

 so If I don't change my sensitivity, but change my Fov from 80 to 30, even though moving around with the same sensitivity feels faster/more shaky, but I still only need to move exactly 3 cm (mouse movement) to switch between the pixels. Is this correct?

No, not for Kovaak's since the FOV does not affect 360 distance. In your specific case take this example, where 35% MDH = 3 cm mouse movement and 10.46 cm crosshair movement (your pixel to pixel).

If you just change FOV to 30, this will happen:

So you now only have to move about 1 cm to cover the same pixel to pixel distance, which obviously makes the sensitivity very fast and hard to aim with.

The proper way for this exact scenario to keep the relative sensitivity would be this:

I.e. setting the sensitivity in Kovaak's to 3.4333471 and the FOV to 30 would keep the exact same ratio for 3 cm mouse movement.

[KLAZMOI]

39 minutes ago, DPI Wizard said:

No, not for Kovaak's since the FOV does not affect 360 distance. In your specific case take this example, where 35% MDH = 3 cm mouse movement and 10.46 cm crosshair movement (your pixel to pixel).

If you just change FOV to 30, this will happen:

So you now only have to move about 1 cm to cover the same pixel to pixel distance, which obviously makes the sensitivity very fast and hard to aim with.

The proper way for this exact scenario to keep the relative sensitivity would be this:

I.e. setting the sensitivity in Kovaak's to 3.4333471 and the FOV to 30 would keep the exact same ratio for 3 cm mouse movement.

But wouldn't the same pixel targets in 70 fov be closer to each other when you view it after switched to 30 fov ? so you can't really calculate with respect to the same 35% MDH if we assume the same pixel targets remain on the screen the entire time. 

Thank you for the reply, i really want to get an answer

[DPI Wizard]

40 minutes ago, KLAZMOI said:

But wouldn't the same pixel targets in 70 fov be closer to each other when you view it after switched to 30 fov ? so you can't really calculate with respect to the same 35% MDH if we assume the same pixel targets remain on the screen the entire time. 

Thank you for the reply, i really want to get an answer

Ok, I get what you mean now  I thought you meant absolute monitor pixel distance. If you're talking about aiming for instance from one side of a box to the other in different FOV's, then yes you are correct.

[KLAZMOI]

1 hour ago, DPI Wizard said:

Ok, I get what you mean now  I thought you meant absolute monitor pixel distance. If you're talking about aiming for instance from one side of a box to the other in different FOV's, then yes you are correct.

Thank you, and one last question to bother you with,  since I am planning to write a short essay on this one

So would you agree that from a Mouse Movement(E.g. measured in cm ) point of view, as long as the sensitivity/DPI & resolution all remain the same, lowering(or raising) the FOV doesn't actually change your mouse movement( amount of cm moved) required to switch aiming between the same two targets.

But however lowering the FOV does mess up your spatial awareness since our eyes perceive monitor distance(2D) instead of degrees turned(3D), (which in this case,  remains the same? or does it?)

Meaning your hand's muscle memory to move a certain distance between the same two targets can remain perfectly accurate(E.g. I can move my mouse 3 cm to the right perfectly even after lowering Fov), but after lowering the FOV, targets now has a shorter monitor distance between them(and appear larger), since they now appear to be closer to each other, one can wrongly overestimate the corresponding distance to move his mouse, since our eyes are not accustomed to the new 3D space/messing up our hand-eye coordination instead.

Edited January 18, 2020 by KLAZMOI

[DPI Wizard]

1 hour ago, KLAZMOI said:

So would you agree that from a Mouse Movement(E.g. measured in cm ) point of view, as long as the sensitivity/DPI & resolution all remain the same, lowering(or raising) the FOV doesn't actually change your mouse movement( amount of cm moved) required to switch aiming between the same two targets.

You could look at it another way: If you keep the same 360 distance while lowering the FOV, you will also keep the same degrees per cm mouse movement. This is not good for aiming though, only for navigation (turning around corners etc).

You are not reacting to how many degrees you should turn,  you are reacting to how far you should move the crosshair.

[KLAZMOI]

11 hours ago, DPI Wizard said:

You could look at it another way: If you keep the same 360 distance while lowering the FOV, you will also keep the same degrees per cm mouse movement. This is not good for aiming though, only for navigation (turning around corners etc).

You are not reacting to how many degrees you should turn,  you are reacting to how far you should move the crosshair.

Can you elaborate some more on why it's not good for aiming?

Edited January 19, 2020 by KLAZMOI

[fortunate reee]

3 hours ago, KLAZMOI said:

Can you elaborate some more on why it's not good for aiming?

360° Distance
This will simply match the distance you have to move your mouse to do a full 360 degree rotation. Most commonly used for hipfire/look aims and sometimes targeting/ADS. Using this for more powerful scopes will make them very sensitivity and make it difficult to aim precisely.
The strength of this conversion is that you will have exact same movement for navigating around, for instance turning 90 degrees around a corner or 180 degrees to look behind you. The drawback is that precisely aiming at something on your screen will be different depending on your FOV. This conversion is not available for Windows or 2D games.

 

its all in the instructions i linked you earlier