My Problems with FOV

[Vampire]

I normally always use the highest FOV available in a game. I feel the most comfortable with it. When not using max FOV it feels cramped, restricted and somewhat claustrophobic. But when calculating to other games I never much cared for the advice that you should also convert the actual H,VFOV, thinking "I rather have a little imprecise result than not being able to use max FOV"

But today I found out that FOV not only matter when calculating from game to game, but it matter in the game itself too, and that brought huge confusion so I am now here in hopes of finding answers.
Whenever calculating things I usually use COD MW 2019 as a baseline because it has the "legacy" option which is 0% Monitor distance, it just feels right to use that for calculations.

The problem is as followed: I never changed the FOV when calculating because it said that FOV doesn't affect the sensitivity so it was set on the default "80", tho I actually use 120 in-game, because as mentioned above: always max. And only now I noticed that when changing the FOV, it also changes the calculated results of the scope sens, and not only by a bit, but that change cuts the calculated results for higher zooms almost in half.

This is the setting that I usually used with the default FOV,

and this is what it calculates when using the actual 120 FOV that I have in game.

Why would I need to change the Scope sens based on FOV when the legacy options should already be 0% on the scopes?
and why do the Ironsights of the different weapon types all have a different calculated result in MW 2019 while they all share the same setting in the config file?

Edited January 1, 2022 by Jega

[Acro]

Legacy scope settings for most games aren't at 0% monitor distance. Only game I know that uses 0% default is Apex (1.0 ads) and Siege (50 ads).

If you want 0% for COD/BF,  you need to use 0% relative. 

As for iron sights, they actually have different FOV values.

[Vampire]

21 minutes ago, Acro said:

Legacy scope settings for most games aren't at 0% monitor distance. Only game I know that uses 0% default is Apex (1.0 ads) and Siege (50 ads).

If you want 0% for COD/BF,  you need to use 0% relative. 

As for iron sights, they actually have different FOV values.

Makes sense as 0% relative appears to be the same for every scope other then the calculated settings for 0% Legacy, difference there being that 0% relative doesn't need to be "calculated" (it's all just "1" while legacy has odd numbers like "0.49042")

I do not really understand why that is as I remember DPI-Wizard themselfs saying that Legacy is 0% Monitor distance and people in Forum saying the same, stating that Legacy is better for muscle memory. But that appears to not be the case when looking at your statement right?

 

Edited January 1, 2022 by Jega

[DPI Wizard]

4 hours ago, Jega said:

The problem is as followed: I never changed the FOV when calculating because it said that FOV doesn't affect the sensitivity so it was set on the default "80", tho I actually use 120 in-game,

This is a big mistake and will make all calculations invalid. The fact that an aim is unaffected by FOV refers to the 360 distance. Meaning in MW2019 you will have the same 360 distance for hipfire regardless of FOV setting. Ironically for MW 2019 you will not see any change in the output when changing FOV and using the ALL conversion with MDV 0%, since they all scale the same to the hipfire FOV. But there will be a difference if you convert to another game, or if you enable Advanced mode to see all the 360 distances.

Not all aims have updated info about this, but aims will in any case be affected by the FOV and 360 distance of the source (hipfire) as well as their own FOV which may or may not be derived from the hipfire FOV.

[Vampire]

57 minutes ago, DPI Wizard said:

This is a big mistake and will make all calculations invalid. The fact that an aim is unaffected by FOV refers to the 360 distance. Meaning in MW2019 you will have the same 360 distance for hipfire regardless of FOV setting. Ironically for MW 2019 you will not see any change in the output when changing FOV and using the ALL conversion with MDV 0%, since they all scale the same to the hipfire FOV. But there will be a difference if you convert to another game, or if you enable Advanced mode to see all the 360 distances.

Not all aims have updated info about this, but aims will in any case be affected by the FOV and 360 distance of the source (hipfire) as well as their own FOV which may or may not be derived from the hipfire FOV.

So, easiest solution is just to always enter the FOV, makes sense and I should have kinda done that earlier.

But, speaking about MW 2019 I still or now am confused about the Legacy/Relative difference. Which one of them now is actual 0% MDV?

(By the way, does it even matter if MDV or MDH is taken for calculations? I always took MDH because horizontal makes more sense as you, well, often aim horizontally)

[DPI Wizard]

11 hours ago, Jega said:

But, speaking about MW 2019 I still or now am confused about the Legacy/Relative difference. Which one of them now is actual 0% MDV?

Legacy is MDV 0% with a locked source FOV of 65 4:3 Relative at 0 coefficient will instead scale the scopes to your configured FOV.

11 hours ago, Jega said:

(By the way, does it even matter if MDV or MDH is taken for calculations? I always took MDH because horizontal makes more sense as you, well, often aim horizontally)

For 0% it's the same. For any other value it is different, as MDV 100% is targeting the top/bottom of your monitor while MDH 100% is targeting the left/right edges.

[Vampire]

1 hour ago, DPI Wizard said:

Legacy is MDV 0% with a locked source FOV of 65 4:3 Relative at 0 coefficient will instead scale the scopes to your configured FOV.

So if I am understanding it correctly, Legacy is not true 0% MDV when using anything else then 65 FOV 4:3, which is the case for me, so I should use Relative instead from now on and for future calculations

[DPI Wizard]

Just now, Jega said:

So if I am understanding it correctly, Legacy is not true 0% MDV when using anything else then 65 FOV 4:3

Correct, legacy is there for... well legacy reasons. So you can get your weapons to feel exactly like they did in the old games.

[Vaccaria]

Also, no need to worry if you have a skill in the game, it's not going anywhere. So all that's left is to learn how to level out the distortions in the game settings. 

[Vampire]

Okay so at this point I truly don't know if I am just straight up completely incompetent, overseeing some major detail (or both) or if soemthing just isn't as it should be, some detail missing, something not working properly.

IF I understand Monitor Distance correctly it should be as following:

There is a tree at a specific point on my screen and I need 10 cm of mouse-movement to get my crosshair on that tree, 0% MDV now means that if I zoom in on my scope and due to the changed FOV there is now a car on on the same specific point on my screen, I would again need 10 cm of mouse-movement to get my crosshair to that car.
It is always the same mouse-movement towards whatever is on a specific point on my screen, no matter the zoom FOV, hence the apperently "good muscle memory" because it always requieres the same input to reach a certain point, no matter what your zoom FOV is. 

For 50% Monitor Distance it is the same movement for whatever is currently half way from your crosshair to the edge of the screen, and it is therefore restricted to that one specific point of your screen

And 100% is the same but  for whatever is on the edge of the screen, and it is therefore restricted to that one specific point of your screen

 

My problem has been so far that I am unable to proper track enemies when in scope, it just feels so slow. I also can't react to what happens a bit further away from my crosshair, like 30% Screen distance.

And it is completely impossible to react whatever happens beyond that, let alone next to you. And you see all the pro players flicking 360 degrees around them while in ADS with pin point accuraty while using something like 35 cm for a 360° turn

Edited January 2, 2022 by Jega

[Vaccaria]

You don't have to look up to the pro players, because your tasks are different. Study this post, it will tell you with examples. Also start studying how FoV and Sens work in games, you always aim for the highest, but it is not effective, the fisheye effect distorts the image, as FoV 120 looks and plays well on 21.9 diagonal, and FoV 103 on the diagonal 16.9. So your settings feel distorted.

https://www.mouse-sensitivity.com/?share=57296e0e4a776914943f09208a19647d  Try these settings. If they turn out to be fast or slow at 400 DPI, then decrease or increase the DPI by 50 or 100, if you have a mice zowie then rawaccel is the only way out. Let's pretend that these settings are your starting point for researching yourself. Affected ADS or independent ADS plays a very important role. With independent you cannot turn 180/360, a big approximation in ADS. Almost all people use each other's settings, they vary by some margin of error. But if you imagine, all the settings are carried over from 2D, as our first sense of cursor movement was on the desktop. Someone uses 800 dpi at 4-6 multipliers and someone uses 400 dpi at 8+. But I'm talking about "Pro" players. Since using 400 dpi on 2k or 4k monitors is not reasonable, so there is a difference between ordinary users and nerds.

[Vaccaria]

Now about tracking. You have to train everything, but where and how? Up to 8.0x you can train in Aim Hero, there is a limit of up to 10 VFoV, below you can not do FoV. To train more than 8.0x already need to trick in KovaaK 2.0. Make the map size larger, unblock the entrance to ADS and Scope.

https://www.mouse-sensitivity.com/?share=64056521cfbb6648feea9bdef99a0c30 Aim Hero

The complexity is adjusted through them: size, speed, acceleration.

https://www.mouse-sensitivity.com/?share=cc0e40fec1117fe5ccdaffc4c36fd67f KovaaK 2.0

looking for something that fits our request. I found.

Download and press EDIT.

Go to FN AR. 

Change to:

Going to Char in FortniteMainJetpack

Change to:

If desired, you can change the Run Speed, for example to 600.

Save with the name for example AX-50. Now the map is ready, so it can be used with other weapons, now you do not need to unpack it, you can change everything in the Settings "Weapon"

This will allow you to check different settings more quickly, as well as adapt to the selected ones.

Place the file in the path: Steam\steamapps\common\FPSAimTrainer\FPSAimTrainer\Saved\SaveGames\Scenarios

AX-50.sce

Edited January 3, 2022 by Vaccaria