For that reason, i would recommend using GEM instead. The sad part is it locks the minimum fov to 45 for some stupid reason, so is not a viable option unless you have a huge screen and put it really close. Gplshift seems to be able to move the pitboards to make them still visible. No longer is distance horribly distorted as it was using an incorrect FOV (effectively like watching the game through a camera, rather than 'being there').Ī downside is that pitboards aren't really very viewable at very low FOVS. You will find that doing this will greatly improve your driving experience and really help you to appreciate the reality of distance, especially for things like braking areas. You need to set this calculated FOV in GEM and then switch car in switch back in order for it to activate (you dont need to launch, just choose a different one from the dropdown box and then change back). So, to get the horizontal field of view, you need to do the aspect ratio conversion inside the FOV calculation formula.Ģ * arctan( (screen height * horizontal resolution / vertical resolution ) / (2 * distance from screen) ) = Total horizontal FOV It is still useful to use the vertical height though, as this is easier to measure accurately rather than worrying about bezels etc. My silly assumption that you could simply ratio the FOV via aspect ratios was partially incorrect - you can but not from the FOV - only from the screen height value, redoing the calculation. (this assumes your pixels are square - if not, then use aspect ratio instead - though if using 3 screens you will need to measure the width so that bezels are taking into account). Vertical Fov * horizontal resolution / vertical resolution = Horizontal FOV

Thankfully, it is very easy to calculate a horizontal FOV from this - even with bezel compensation if you use the bezel compensated res width in your calculation. You can then use this for all games that use a vertical FOV value. (arctan is the tan -1 thing, the inverse tangent) The distance from your eyes to the screen.Ģ * arctan(screen height / (2 * distance from screen) ) = Total vertical FOV.This doesn't always seem to be the case.Īnyway, if you got bored of the rest of my ramble, read and try at least this part:įirst we will calculate your vertical field of view. With more modern applications, you would hope they would use a vertical fov in order to calculate the horizontal, based on your aspect ratio. This isn't ideal, as it means if you get a wider monitor / 3 screens then you have to calculate the fov again, as you have changed your horizontal viewing area. This won't work for you though, as you are using a very incorrect FOV.įor 3 screens, gpl appears to use a horizontal FOV (for one screen probably too, though when i tried it here at home, the 1 screen fov seemed too wide if i did it horizontally :|).Ī lot of old games use a horizontal FOV value and then calculate (base) the vertical one on that, according to your aspect ratio. You are supposed to be viewing the direct centre of that image, and therefore due to how your eyes see, any distortion towards the edge is not picked up by your eyes and is 'corrected', due to the angles involved. Strictly speaking, if multi-view is not supported, then the 3 screens should be laid out horizontally, with no angle, as the image being displayed is meant to be one large flat image. Maybe some flight simulators, but i wouldn't know. It's sad because no non-racing games support 3 screens properly that i am aware of.

If you have a really high FOV then as you get further and further to the edge, things get more and more stretched. Viewing stuff on a flat surface is not natural - it's not how your eyes see - or in fact cameras. With 3 separate viewports, you can sort of half-emulate a cillindrical FOV, which is a lot more natural. There is no way around this unless the game is coded to support 3 separate viewports (like iracing, rfactor2 (multi-view) and assetto corsa). The reason things look elongated in the further you get from the centre is due to rectilinear distortion.

Rfactor 2 fov