Converting One players Settings to a different FOV

[Springsgaming]

I have been trying to understand the whole fov thing and I truly want to get good conversions. I have tested a few settings in games and I am ballpark close but doesn’t quite feel the same. Here is a conversion of Shrouds apex legends settings but I want them to feel the same in my setup of 800dpi, 90 fov, and with a 23 inch monitor as the changes. Here’s my charts for reference.

1. I want to keep the same 360 distance since it works for me.

2. I want to have 90 fov setting in game but have the same feel.

3. Use this as a teachable moment or a sticky for fov in laymen’s terms

4. I have other games to convert after I get my baseline off this.

 

note, I see lots of pro settings and they leave ads multiplier at 1, would I really have to drop it due to a fov change?

[Drimzi]

You need to have the same fov in the same physical area as Shroud to be able to use the same 360 distance and have the same feeling. You basically lock the games projection, and then render more or less of the projection according to the monitor size and shape. The bigger the monitor, the more fov that is revealed, and vice versa. How zoomed in the game looks, how large enemies are, etc, all stay constant.

 

According to your screenshot, I'm assuming Shroud is using a 24.5" 1920x1080 monitor with 104 fov (note, the fov is not exactly 104, you actually need his cl_fovScale value for more accurate results).

 

The full 24.5" would have an fov equivalent to 104 apex fov. The 23" portion of a 24.5" monitor would have an fov equivalent to 100.4629 apex fov.

Also, 23" would be equivalent to ~1802x1014 with black bars on his monitor.

You simply need to set the fov as close as possible to 100.4629, and copy his 360 distance, to emulate Shroud's settings. For this, you would use 1.5 sensitivity instead of 3 sensitivity, since you have double his CPI.

To scale to 90, you would need to scale the 360 distance by 0% MDV, and then scale that result according to his zoom sensitivity, since that is how he prefers to have his sensitivity change according to fov (imagine he picks up a gun that zooms in to 90 fov, you would match this sensitivity). If he's at 1 zoom sensitivity, then simply convert 0%, which changes from 1.5 sensitivity to ~1.25 sensitivity.

For zoom sensitivity, just copy his value.

Edited April 14, 2019 by Drimzi

[Springsgaming]

I suppose this is where the complication is because I cannot follow how you came up with these answers. To answer your question on Shrouds fov it is the setting in game he uses and I don’t have access to any other information.  Do you mind showing your work with how you used the calculator with images and thought process for each step. I appreciate the response and trying to explain things.

Note, apparently apex legends does not have monitor size affect the fov which is part of my complication trying to translate to my settings or I have an incorrect source.

So I inspected more and it appears I just have to change the ads to properly convert to use the 90fov I want to run? I’m editing this post roughly 7 hours after studying your post and playing with the calculator more. I’m still interested in you showing your work and breaking down how you calculated a fov that translate or is apex legends literally just more you can see without sensitivity being effected. Like if shroud uses 104 fov and I want to use 90 fov it wouldn’t matter because my sensitivity is literally just half his and figure out if ads actually needs changed to play the same.

for the light readers that love lists

1. Can you show your work using the calculator or is this more advanced than using the calculator alone.

2. I’m having a hard time trying to figure out how you came up with 1.25 sensitivity down from 1.5 when changing from 104 fov to 90.

3. I want to see your work but I will post my overwatch settings which I want to translate to apex legends, links attached.

Edited April 14, 2019 by Springsgaming
Science

[Drimzi]

This is too advanced for the calculator alone. It requires manual calculations. The calculator doesn't use monitor size for anything AFAIK. It just looks at the fov values.

 

Here is an example of two monitors (one is twice the size) set to 90 field of view. The calculator will think that these two scenarios are the exact same thing, as it just looks at the 90 field of view, when in reality they are very different.

 

Here are two examples where the field of view is adjusted to result in the same projection. First image syncs to the large monitor, second syncs to the small monitor.

 

You want to match the projection, and make the field of view dependent on the size and shape of the aperture (the hole that you view the game world through, the monitor basically). In the first case, the small monitor is adjusted to 53.13 fov, and in the second case, the large monitor is adjusted to 126.87 fov.

On your current monitor, switch between ~53 fov, 90 fov, and ~127 fov, and you will quickly notice that the literal sensitivity of the mouse will be affected. You can't just keep the same cm/rev (distance for 1 revolution, aka 360 distance). The projection has to scale to accommodate the desired field of view, which zooms the game in/out. This is because the monitor doesn't magically grow or shrink to accommodate the desired field of view.

You have to scale the rotation with the projection. The cm/rev needs to scale at the same rate as the change in projection.

 

You can use 0% MDV to scale by the relative change, as the monitor size is not required when it is constant. However when converting between different sized monitors, you have to do manual calculations.

To match Shroud's settings, you have to use the same cm/rev as him, and have the same field of view within the 23" portion of his monitor. This would be 100.4629 fov. Since you want a different field of view, you have to scale the cm/rev by the change in projection, which is where the 1.5 -> 1.25 comes in.

 

Convert with 0% MDV if you are just working relative to your own setup. 0% from Overwatch to Apex Legends. That will preserve the literal sensitivity of the mouse. This isn't always desirable though, as the required movements to accomplish tasks depends on the game and how zoomed in your are. For example, Fortnite is really zoomed in, and requires a lot of mobility and rotations for core gameplay. It would be more beneficial to just use an entirely different sensitivity, instead of converting with 0% MDV. A new sensitivity generated by using a different method, which preserves a desired property, or just picking a new one arbitrarily.

Edited April 15, 2019 by Drimzi

[DPI Wizard]

5 minutes ago, Drimzi said:

The calculator doesn't use monitor size for anything AFAIK. It just looks at the fov values.

Just to confirm your post:

It just uses the size to calculate the relation between the mouse movement and the crosshair movement. It is not used for sensitivity calculation at all as of now.

The calculator also assumes the FOV reaches the edges of the monitor, regardless of aspect ratio and size (i.e. stretched). So matching sensitivity between different monitor sizes is not currently automatically supported, you have to do it manually.

[Springsgaming]

Ok, is this a feature that is potentially in the works so using the calculator can be more accurate across rigs/events or even have find settings across games factored in.

Yesterday I found settings I liked off the rough estimation of shrouds for apex legends but I ended up liking the feel of a different game all together. I used overwatch settings and adjusted my apex legends via base 90 fov settings and I’m happy with that.

my new issue is trying to figure out a good conversion from Overwatch to the division 2 which is 3rd person. I’ll post again with what my overwatch settings are and the generic settings the calculator offers for the division 2.

[Springsgaming]

Finally getting to post, sorry for the delay. Here’s my settings I’m using for overwatch and apex legends. So my next step is to get proper settings for the division 2. I haven’t had a chance to log into the game but I know I am not using the ads setting that is listed.  Show me how you figure a fov between a first person to 3rd person and get an accurate  calculation for sensitivity.

[Quackerjack]

On 4/15/2019 at 8:08 AM, Drimzi said:

This is too advanced for the calculator alone. It requires manual calculations. The calculator doesn't use monitor size for anything AFAIK. It just looks at the fov values.

 

Here is an example of two monitors (one is twice the size) set to 90 field of view. The calculator will think that these two scenarios are the exact same thing, as it just looks at the 90 field of view, when in reality they are very different.

 

Here are two examples where the field of view is adjusted to result in the same projection. First image syncs to the large monitor, second syncs to the small monitor.

 

You want to match the projection, and make the field of view dependent on the size and shape of the aperture (the hole that you view the game world through, the monitor basically). In the first case, the small monitor is adjusted to 53.13 fov, and in the second case, the large monitor is adjusted to 126.87 fov.

On your current monitor, switch between ~53 fov, 90 fov, and ~127 fov, and you will quickly notice that the literal sensitivity of the mouse will be affected. You can't just keep the same cm/rev (distance for 1 revolution, aka 360 distance). The projection has to scale to accommodate the desired field of view, which zooms the game in/out. This is because the monitor doesn't magically grow or shrink to accommodate the desired field of view.

You have to scale the rotation with the projection. The cm/rev needs to scale at the same rate as the change in projection.

 

You can use 0% MDV to scale by the relative change, as the monitor size is not required when it is constant. However when converting between different sized monitors, you have to do manual calculations.

To match Shroud's settings, you have to use the same cm/rev as him, and have the same field of view within the 23" portion of his monitor. This would be 100.4629 fov. Since you want a different field of view, you have to scale the cm/rev by the change in projection, which is where the 1.5 -> 1.25 comes in.

 

Convert with 0% MDV if you are just working relative to your own setup. 0% from Overwatch to Apex Legends. That will preserve the literal sensitivity of the mouse. This isn't always desirable though, as the required movements to accomplish tasks depends on the game and how zoomed in your are. For example, Fortnite is really zoomed in, and requires a lot of mobility and rotations for core gameplay. It would be more beneficial to just use an entirely different sensitivity, instead of converting with 0% MDV. A new sensitivity generated by using a different method, which preserves a desired property, or just picking a new one arbitrarily.

Can you share the math?

I try to match fov from a 25.5 monitor 16:10 to 24.5 monitor 16:9