gzv Posted July 1, 2017 Posted July 1, 2017 (edited) I'm wondering why the calculator shows Reflex Arena's actual HFOV @ 124.59 when r_fov is set to 110. The in-game FOV seems much closer to 110, and adjusting r_fov = 94 so that actual HFOV = 110 does NOT look like 110 in-game; it looks like 94. I ask because I'm unsure if it's messing up my viewspeed conversion, e.g. Reflex 13.8 in/360 becomes 17.8in/360 in Overwatch (FOV 103), which seems much too low. Is this a bug or am I missing something? Edited July 1, 2017 by gzv
Wizard DPI Wizard Posted July 1, 2017 Wizard Posted July 1, 2017 Just check the game now, and the calculations are correct. But the graphic style does make the FOV look less extreme than it is.
gzv Posted July 1, 2017 Author Posted July 1, 2017 (edited) I discovered that when I change FOV type to Horizontal Deg. | Res. Base the calculator now gives me the expected behavior (r_fov = actual HFOV.) Is this the correct setting? Is calculator intended to auto-select the correct FOV type? The calculator defaulted to Horizontal Deg. | 4:3 base for 1920x1080, which I find strange. Hoping you can enlighten me, thanks! Edited July 1, 2017 by gzv
Wizard DPI Wizard Posted July 1, 2017 Wizard Posted July 1, 2017 The game uses Hor+, which is the same as Horizontal Deg. | 4:3 base. This means that any resolution wider than 4:3 will expand the FOV rather than stretching the configured FOV. So when you have an FOV of e.g. 110, this is correct for 4:3. But when you use a 16:9 monitor additional FOV is added on
gzv Posted July 1, 2017 Author Posted July 1, 2017 (edited) Thanks very much! That explains everything. Edited July 1, 2017 by gzv
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now