HOW TO: Proper Triple Screens Setup FOV & Monitor Angles

I started this tutorial several years ago on other forums and have been tweaking it on occasion and will continue to do so as the technology and its application move forward. The bulk of it is mostly aimed to the titles with proper triple screen support such as rFactor, rFactor 2, Game Stock Car, Automobilista, Assetto Corsa and iRacing; but it is still useful and very relevant to all titles.

A proper and mathematically correct setup is the Holy Grail of simulation since it allows for the 1:1 correlation between the real world and what can be reproduced and then experienced through the various platforms.

It's always been an arduous and lengthy process of research and trial and error to understand it and implement it, but hopefully this tutorial can facilitate and expedite this into a much less tenuous journey.


INTRODUCTION
A single screen ordinarily does not allow for a proper 1:1 mathematical field of view to be implemented.

That is because on a single screen you'd have to go either for a very large sized TV or to set up a projector screen; although neither will still be able to covering your peripheral view regardless of how good they are.

As a rule of thumb, usually¹ you must try to get as close as possible to the screen as to make its image relatively larger in relation to you, otherwise you're likely stuck having to find some middle-ground between your mathematical field of view and the other one that offers you with an enough and more comfortable view of the sides of your vehicle.
OBS¹: Keep in mind, however, that this rule is not always absolute for triple screens. There are particular instances where you'll be better off moving away from the screens. That is because you want to avoid being too crowded by the resultant screen angles, a scenario which will lead to the screens going past too much your real life physical field of view. Far from ideal, wasteful and simply unnecessary.

If you're on a single screen you'll almost always have to reach a certain compromise, but the closer you are to your screen (and the larger they are) the smallest the compromised for your true FOV.

Which leads us to what I repute as the best solution for the FOV: the triple screens.

Be it monitors, TVs or projectors each will have its application depending on budget, room characteristics and designated applications. And no, I'll not be talking VR (Virtual Reality) at this point in time as I still don't regard any of the available sets as a fully developed solution that truly surpasses proper triple screens and without huge drawbacks. So please do not cry yourself dry.

Therefore whenever any kind of triple screens is employed, for any kind of simulation, only a mathematically correct "RIG" with a proper 1:1 field of view should be acceptable, otherwise it puts to waste all of the labor, time and money invested in it.


1. FIELD OF VIEW (FOV)
For starters I DO NOT RECOMMEND the various often mentioned website calculators. Mostly because in my view one should not rely on third party when better results can be achieve by doing it oneself but also because they are far from infallible. While I do appreciate its practicality and utility; particular if you're casual about your sim racing, the implementation of the MATHS is generic and with instances it won't provide the exact results you're after.

With that out of the way, the first rule of sim racing is: you do not talk about FOV as it being a matter of taste. The second rule of sim racing is: you do not talk it about it being a matter of opinion. Third rule: you do not say it's about personal preference.

There is no subjectiveness regarding FOV. None! To state otherwise is wrong and, frankly, moronic.

A mathematically correct FOV does never feel off as it does represent exactly what the real world feels and looks like. Therefore if your screen real estate and setup configuration allow for it you'll want to use only a proper FOV. Trust me on this!

The FOV has many more important implications than people realize, as it directly affects the way depth and height are displayed and perceived. If the FOV is too high, for example, then the straights will look way longer than they are, turns will look less sharp and heights will look shallower. An incorrect field of view provides the so called "greater sense of speed" only because distances that appear longer are traversed in the same amount of time, tricking your senses and thus defeating any purpose of simulation itself.

The vertical FOV is calculated by taking half the height of the image (counting out the bezels and the rest of the frame of the device; and only measuring the actual display panel) and dividing it by the viewing distance (the distance between the observer's eyes and the center of the screen). You then apply the inverse tangent function (arc tangent or atan) to that result and multiply this by two.

The reason only half of the image height is used is because you are supposed to line the center of the complete image with your eyes. That half height divided by its distance to your eyes provides the viewable angle when the inverse tangent is applied. It only describes the triangle on half of the image so the other half must be added which is equal to the first since the angles are the same as long as your eyes are lined up with its center.

For reference: MY RIG currently produces an image height (again counting out the bezels and the rest of the frame of the device; and only measuring the actual display panel) of 53,00cm, with my viewing distance being 89,00cm from the center of the screens, which renders my vFOV at 33º (~33,16º).

How to calculate the proper vertical FOV (vFOV):
vFOV = 2 x {invTan x [(ImageHeight ÷ 2) ÷ ViewingDistance]}

Therefore:

53 ÷ 2 = 26,5

÷ 89 = 0,2977528089887640449438202247191

Inverse Tan = 16,581047847739573955007058070902

x 2 = 33,162095695479147910014116141804


vFOV = 33º


OBS¹: When I say "viewing distance" I'm meaning the distance from your eyes to the center of the screens.

OBS²
: InvTan (arc tangent or atan) can be found in any scientific calculator. Windows has one which you can set to scientific under file. To use it just press the buttons "Inv" and then "Tan").


1.2. HORIZONTAL FIELD OF VIEW (hFOV)
This applies to titles like iRacing that employ a horizontal field of view calculation.

And going back very quickly to the right triangles, we already know that "A = invTan(a/b)" and that we need to double "A" in order to get the entire screen angle and to halve the width of said screen in order to get to "a". All of that gives us the formula: ScreenAngle = 2 x {invTan x [FullDeviceWidth ÷ (2 x ViewingDistance)]}.

That means you can simply calculate the total horizontal FOV by multiplying A by 6 instead of only by 2. As in 3 screens times 2. That happens because there are three screens but we are only calculating half of the viewing angle.

How to calculate the proper horizontal FOV:
hFOV = NumberOfScreens x 2 x {invTan x [FullDeviceWidth ÷ (2 x ViewingDistance)]}

Therefore:

89 x 2 = 178

97,7 ÷ 178 = 0,54887640449438202247191011235955

Inverse Tan = 28,761344358730505421853306646369

x 2 = 57,522688717461010843706613292738

x 3 = 172,56806615238303253111983987821


hFOV = 173º


1.3 vFOV ADDENDUM FOR RACEROOM RACING EXPERIENCE
The vFOV implementation in the SimBin titles has a few particularities.

One of which is that it only allows you to choose among a set of fixed multiples of its default FOV; which is 58º for single screens and 40º for the triple screens. That is obviously not ideal as it will not let you set your own exact mathematical FOV unless you're lucky enough to fall into one of the nine presets multipliers 0.5, 0.6, 0.7, 0.8, 0.9, 1.0, 1.1, 1.2, 1.3.
Triple Screens

1.0x = 40º

0.5x means: 40º x 0.5 = 20º

0.6x means: 40º x 0.6 = 24º

0.7x means: 40º x 0.7 = 28º

0.8x means: 40º x 0.8 = 32º

0.9x means: 40º x 0.9 = 36º

1.1x means: 40º x 1.1 = 44º

1.2x means: 40º x 1.2 = 48º

1.3x means:
40º x 1.3 = 52º


As said, unless you're lucky to automatically fall into one of the presets an approximation is not good enough. If only you could set your exact mathematical FOV... Oh but wait you can, not within the title, but with some legwork.

What you have to do is to go to "\Documents\My Games\SimBin\RaceRoom Racing Experience\UserData" and open the "graphics_options.xml" file in the notepad.

Simply take your mathematical vFOV and divide it by 40. Take this result and place it inside this line
from: <custom type="float32">1.00000000</custom>

to: <custom type="float32">0.825</custom>

for vFOV 33º in this instance


2. TRIPLE SCREENS' ANGLES
There is a unfortunate and widespread notion out there that the gMotor2 engine locks the screen angles at 45 degrees.

This couldn't be more INCORRECT as the gMotor2 engine has never locked the screens at any set angle but quite on the contrary has used a mathematical formula based off your set FOV to calculate what screen angles you should be using.

This "45º myth" probably started because a "common" distance that a good number of people have their screens at works out to more or less around 45º... And because you'll only start noticing a bigger discrepancy when you either begin going really close or really far away to the screens. Regardless it is definitely set improperly for most of the people and your brain can tell it even if you don't realize right away what it is telling you.

The higher your FOV the higher the side screen angles you should use.

It can't be emphasized enough: just like the FOV, the screen angles also are NOT a matter of subjectivity, taste or opinion. They must be set following the application of the MATHS (Mathematical Anti-Telharsic Harfatum Septomin).

Even for titles that allow for the angles to be customized you should still be using the proper ones that are dictated by the formulae because this way you're ensuring to be at the same distance from all three screens.

The closer the screens are from you the higher the vFOV, the higher the vFOV the higher the side screen angle, it is all linked together along with your viewing distance and panel's width obviously.

For reference: MY RIG currently has its screens set at a mathematically dictated angle of 57,50º (~57,52º), with my viewing distance being 89,0cm from triple 97,7cm wide screens.

How to properly calculate the angles you should set your screens at:
ScreenAngle = 2 x {invTan x [FullDeviceWidth ÷ (2 x ViewingDistance)]}

Therefore:

89 x 2 = 178

97,7 ÷ 178 = 0,54887640449438202247191011235955

Inverse Tan = 28,761344358730505421853306646369

x 2 = 57,522688717461010843706613292738


Screen Angle = 57,50º


How to calculate the distance you should sit in order to be able to run certain angles:
ViewingDistance = FullDeviceWidth ÷ {2 x [Tan x (ScreenAngle ÷ 2)]}

Therefore:

57,50 ÷ 2 = 28,75

Tan = 0,54861878662666752691655773919409

x 2 = 1,0972375732533350538331154783882

97,7 ÷ 1,0972375732533350538331154783882 = 89,041792207604790779151852844296


Viewing Distance = 89cm


2.1 TRIPLE SCREEN'S ADDENDUM FOR RACEROOM RACING EXPERIENCE
After many years of waiting RaceRoom Racing Experience has finally received the proper triple screen support it so much needed.

Again somewhat a convoluted method to set up but it works after the additional necessary legwork.

Ultimately you'll have to enter a line of arguments containing all the measures and characteristics of your triple screens and rig in the "SET LAUNCH OPTIONS" on the title properties within the Steam Client.

It's going to look something like this:
-triScr 890 0 977 570 0 977 570 0 57 977 570 0 57

Color coded they stand for:
RED: Your viewing distance to the middle of the central screen.
BLACK: The vertical offset, if any, of your gaze from the middle of the screen center. This value can be either positive or negative.
BLUE¹: The width of your screens (bezels included).
ORANGE: The height of your screens (bezels included).
GREEN¹: The bezels width.
PINK: The screen angles.
OBS¹: I've found that by accounting for the bezels in the nVidia Surround will allow you to fill the argument line with zeros for the bezels. If you don't correct your bezels in the Surround you can choose to do it solely in the argument line, but you'll likely have to account for the Image Width instead of the full Screen Width.

OBS²:
You can use any unit of measurement (inches, cm, mm, etc) as long as you keep it consistent. You can also enter decimals by adding a dot.


3. ADDITIONAL TIPS AND ADJUSTMENTS
It goes without saying but in case you're in doubt, yes, the screen bezels' width must be corrected within the NVIDIA or AMD control panels regardless of the other calculations or adjustments in order to achieve a seamless transition between the screens.

Raise or lower your screens and/or seat in order to align your eye line with the middle of the screens that way you won't be constantly looking up or down in search for the horizon but facing forward in natural line as you should and as you do in real life. Ideally your eye line must align to the middle of the screen up to 20% above of that (or between 50% to 60% up from the bottom of the viewable area) but no more.

Always¹ try to get AS BIG OF SCREENS AS POSSIBLE and sit as close to it as you can since the closer your eyes will be to the image the lower the FOV you'll be able to use and the best visual experience you will get.

OBS¹: Catch-22 here! The larger the screen and the closer you sit in relation to it the higher your vFOV will be. And the higher your FOV the higher the side screen angles should be... which can represent a problem after a certain point, say 50" or larger; or if you're sitting "too close" even smaller screens will require attention! When your screen angles begin to get too high you then begin to experience a few problems, most noticeable the worse accessibility in and out of your seat and the increase of reflexes from the other screens (better mitigated on projector setups). Also you will now have (depending on your screens' size) a certain amount of your side screens going past beyond your field of view, detracting from the full potential of the rig. All the measures talk to each other, always be mindful of that.

Turn off things like "virtual arms" and "virtual steering wheels", since you already have your real ones in front of your eyes and don't need - not want - to have it doubled...

Level the horizon for the cockpit view of your cars in your vehicle camera (.CAM) files:
OrientationOffset=(0.0, 0.0, 0.0)


Remove all the artificial cockpit vibrations in your .PLR files.
Cockpit Vibration Mult1="0.00000"

Cockpit Vibration Freq1="0.00000"

Cockpit Vibration Mult2="0.00000"


Cockpit Vibration Freq2="0.00000"


Turn off or set to 0% any look to apex and lock to horizon options you may have in-game or in your .PLR files.

Stabilize the camera pitch and roll of your cockpit view in your vehicle camera (.CAM) files:
OrientationRate=(999.000000, 999.000000, 999.000000)


This is not at all essential but I'd recommend you to customize and to attach some hood and skirts to your screens as it will improve your experience by blocking potential distractions and by eliminating or reducing reflections (and will make your rig look even cooler). I cut MY OLDER ONES out of simple 10mm styrofoam sheets and the NEWER ONES out of 5mm K-Line (card polyethylene foam) wrapped in carbon fiber styled vinyl, but you can use a whole bunch of different materials to achieve similar or even better results.


4. HOW TO SHOP FOR THE BEST TVS FOR SIM RACING
TV technology is ever evolving and the larger TVs that once were far too expensive for dedicated simulator use are becoming more and more accessible. PAUSE. I'll still be adding more information on what to look for when choosing the right TV for sim racing as well as how to improve the overall eye candy factor for the various sims.

-------------------------

That's all for now. Mathematical perfection for practical application at its best!

Enjoy! ;)

Also posted here on the Reiza Studios's Forums.

GTSpeedster's AMS MODs
 
Last edited:
Thanks @ConanMcloud! My current was pretty close after recomputing, but from this, I should have a lower vFOV of 22, as I was using 29 (triple 23"s). My problem with lowering the vFOV is the seat in some cars (ex. Boxer) could no longer be moved further back.
 
@JoelGL You can move even further the seat position, inside the folder of the car, in the cockpitinfo.ini file.
Thanks. Something wrong with my outcome, can you pls help, @ConanMcloud ?

Trying my computed vFOV of 23 and this is how it looks like. The right panel shows the dash curved curved too much that I no longer see the right side mirror. You'll also notice the left mirror is quite far at the back. This is at the bezel-corrected resolution 5835x1080.

Also, can you post a sample in AMS? As your Rig shows AC only, in w/c I can set my triples correctly, no issues.
 

Attachments

  • GRAB_007.JPG
    GRAB_007.JPG
    483.9 KB · Views: 3,277
I love fov discussions, should be great to watch.
Personally I've just about given up on my triple 27's as I can't go back from nvidia 3d vision 2 on center monitor. Depth for me adds the greatest immersion and makes it more real than triples.

What do you mean? You could just grab a couple more panels that also allow for 3d vision, no? I'm not a huge fan of 3d but I've used a few times in my own rig without bigger issues as far as I could tell.
 
Last edited:
Thanks @ConanMcloud! My current was pretty close after recomputing, but from this, I should have a lower vFOV of 22, as I was using 29 (triple 23"s). My problem with lowering the vFOV is the seat in some cars (ex. Boxer) could no longer be moved further back.

Thanks. Something wrong with my outcome, can you pls help, @ConanMcloud ?

Trying my computed vFOV of 23 and this is how it looks like. The right panel shows the dash curved curved too much that I no longer see the right side mirror. You'll also notice the left mirror is quite far at the back. This is at the bezel-corrected resolution 5835x1080.

Also, can you post a sample in AMS? As your Rig shows AC only, in w/c I can set my triples correctly, no issues.

Deeply sorry for the absence @JoelGL.

You are running it with multiview on, right? That is absolutely crutial for each screen to be wrapped around properly. Just make sure you got that on.

Other than that I believe what you're seeing, from the screenshot you provided, is indeed the correct portrayal of what the vFOV of 23º should looks like.

HOWEVER, since you mentioned you're running triple 23" screens, I believe that's probably not the FOV you should be or would want to be using, unless you're sitting a bit further away than you should be from the screens. I'm running a vFOV of 35º with screens twice as larger as yours and if I'm guessing right we're probably sitting at more or less the same distance from the screens (I sit at 82,5cm measured from my eyes to the center of the screens).

Each rig is unique in its measures and therefore it is very hard to judge what the real issue might be without the actual numbers regarding the screens width, image height and viewing distance. Could you tell me what those are so I can get a proper picture of your rig?

But in any case, in general my advice is to always sit as close as you physically can to your monitors. The smallest they are the more import this is since by doing so will allow you to run higher FOVs which for smaller screens is almost a necessity. And you must follow those two formulas I provided in the first post regarding FOV and Monitor Angles to the letter!

Once you get your own mathematically correct FOV set and you're looking at screens that wrap around you without distortions, only then, if the result are still not ideal, you might begin considering compromising a bit your FOV.

A compromise is sometimes indeed necessary for setups with small screens where you're not getting a good view of mirrors, a proper sense of the dimensions of the car and so on. But in my experience that is rarely the case if you follow the instructions and such compromise regarding mathematical FOV should be taken only as last resort if your rig prevents you from physically move things around.

This is my panoramic view of 35ºvFOV (screens at an angle of 60º):
PLHpwWV.jpg

In game screen shot of 35ºvFOV:
pmJJeSx.jpg


And this is my panoramic view of 23ºvFOV (screens at an angle of 60º):
zThpxNO.jpg

In game screen shot of 23ºvFOV:
MygdNAB.jpg


Hope it helps! Cheers! ;)
 
Here's a website that is dedicated to this question, and it's got a calculator that does the maths for you. You just have to input which sim you're using, seating distance and monitor size, triples or single monitor:
http://www.projectimmersion.com/fov/

I don't mean to sound repetitive, let alone bash that tool as it has, like I said, some merit. But the truth is that everything you need to set up your FOV are here plain and simple in those formulas I've posted, and it has to be said that their mathematical accuracy surpasses a good measure the one provided on that website. Plus, you don't need to rely on anything or anybody else but on pure math. :thumbsup:
 
Deeply sorry for the absence @JoelGL.

You are running it with multiview on, right? That is absolutely crutial for each screen to be wrapped around properly. Just make sure you got that on.

Other than that I believe what you're seeing, from the screenshot you provided, is indeed the correct portrayal of what the vFOV of 23º should looks like.

HOWEVER, since you mentioned you're running triple 23" screens, I believe that's probably not the FOV you should be or would want to be using, unless you're sitting a bit further away than you should be from the screens. I'm running a vFOV of 35º with screens twice as larger as yours and if I'm guessing right we're probably sitting at more or less the same distance from the screens (I sit at 82,5cm measured from my eyes to the center of the screens).

Each rig is unique in its measures and therefore it is very hard to judge what the real issue might be without the actual numbers regarding the screens width, image height and viewing distance. Could you tell me what those are so I can get a proper picture of your rig?

But in any case, in general my advice is to always sit as close as you physically can to your monitors. The smallest they are the more import this is since by doing so will allow you to run higher FOVs which for smaller screens is almost a necessity. And you must follow those two formulas I provided in the first post regarding FOV and Monitor Angles to the letter!

Once you get your own mathematically correct FOV set and you're looking at screens that wrap around you without distortions, only then, if the result are still not ideal, you might begin considering compromising a bit your FOV.

A compromise is sometimes indeed necessary for setups with small screens where you're not getting a good view of mirrors, a proper sense of the dimensions of the car and so on. But in my experience that is rarely the case if you follow the instructions and such compromise regarding mathematical FOV should be taken only as last resort if your rig prevents you from physically move things around.

This is my panoramic view of 35ºvFOV (screens at an angle of 60º):
PLHpwWV.jpg

In game screen shot of 35ºvFOV:
pmJJeSx.jpg


And this is my panoramic view of 23ºvFOV (screens at an angle of 60º):
zThpxNO.jpg

In game screen shot of 23ºvFOV:
MygdNAB.jpg


Hope it helps! Cheers! ;)
Hi, no problem at all. Yes, I have multiview enabled.

For my reference, to see if I come up with similar values as you would compute using my values, here are my values (3 x 23" monitors, 16:9):
a. distance from my eyes to center of monitor = 69cm (nearest I can manage due to triple stand's foot),
b. Monitor width =59cm
c. image height = 29cm (so half =14.5cm),
d. side monitors angled at around 40º.

This results to vFOV = 23.7 or 24, and like in your last 2 images, results to the right-side mirror no longer in view. In this case, what are the best compromises I could look at?

Some clarification though. I tried calculating w/ these values again. First for MonitorAngle, and it results to 46º, w/c is weird because they have my side monitors too inward. The current 40º makes them more straight to my view at this viewing distance. Distance results to 81cm, w/c is farther than my current setup of 69cm.

Thanks again.
 
Hi there GT Speedster , i want to ask you about Assetto Corsa`s triple screen support in game.Is the calculated fov mathematically correct ? Can i relay on that, and using the fov for similar sim racing games such as Dirt Rally. I`m asking you coz my rig is similar to yours (distance to screen 83 , side monitors angles 65) and Assetto corsa`s triple screen support shows me 56 vFov , but if i calculate it by your formulas below , it cames out 37 +/-.

Thanks in advance


GT SPEEDSTER'S TRIPLE SCREENS SETUP GUIDE

Whenever triple screens are employed for any kind of simulation only a mathematically correct RIG with a proper FOV should be acceptable, otherwise what is the point of all the labor, time and money invested on it?


1. MONITOR ANGLES


There is a unfortunate and widespread notion out there that the gMotor2 engine locks the monitor angles at 45 degrees...

This couldn't be more INCORRECT as the gMotor2 engine has never locked the monitors at any set angle but, on the contrary, has used a mathematical formula based off your FOV to calculate what monitor angles you should be using.

This "45º myth" probably started because a "common" distance that a good number of people have their monitors at works out to more or less around 45º... And because you'll only start noticing a bigger discrepancy when you either begin going really close or really far away to the screens. Regardless it is definitely set improperly for most of the people and your brain can tell it even if you don't realize right away what it is telling you.

The higher your FOV the higher the side monitor angles you should use.

It can't be emphasized enough: just like the FOV, the monitor angles as well are NOT a matter of subjectivity, taste or opinion! They must be set following the application of the MATHS (Mathematical Anti-Telharsic Harfatum Septomin).

The closer the monitors are from you the higher the vFOV, the higher the vFOV the higher the side monitor angle, it is all linked together along with you viewing distance and panel's width obviously.

For reference: MY RIG currently has its screens set at a mathematically dictated angle of 60º (~60,22º), with my viewing distance being 82,5cm from triple 95,7cm wide screens.

How to properly calculate the angles you should set your monitors at:



How to calculate the distance you should sit in order to be able to run certain angles:



OBS¹: When I say "viewing distance" I'm meaning the distance from your eyes to the center of the screen.
OBS²: InvTan (arc tangent or atan) can be found in any scientific calculator. Windows has one which you can set to scientific under file. To use it just press the buttons "Inv" and then "Tan").



2. FIELD OF VIEW

Keep in mind that FOV is not in any way subjective or a matter of opinion! A mathematically correct FOV does never feel off as it should represent exactly what the real world feels and looks like. Therefore if you're a triple screen user you'll want to use only a proper FOV, believe me!

FOV has many more important implications than people realize, it directly affects the way depth and height are displayed and perceived. If the FOV is too height then the straights will look way longer than they are, turns will look less sharp and heights will look shallower. An incorrect field of view provides "greater sense of speed" only because distances that appear longer are traversed in the same amount of time.

So, first of all I DO NOT RECOMMEND this "Project Immersion" calculator. I've seen it being mentioned many times and I think it has merit but its implementation of the maths is a tad too generic. Do not follow this but instead calculate yours yourself with the proper formula.

vFOV is easily calculated be taking half the height of the image (image, not screen!) and dividing it by the viewing distance (the distance between your eyes to the center of the screen). You apply inverse Tan on that result and then finish it by multiplying this by two.

The reason half the screen height is used is because you are supposed to line the center of the screen with your eyes. That half height divided by the distance to your eyes provides the viewable angle when inverse tan is applied. It only describes the triangle on half of the screen so the other half must be added which is equal to the first since the angles are the same as long as your eyes are lined up with the center of the screen.

For reference: MY RIG currently produces an image height (image, not screen!) of 52,25cm, with my viewing distance being 82,5cm from the center of the screens, which renders my vFOV at 35º (~35,14º).

How to calculate the proper vertical FOV:




3. HORIZONTAL FIELD OF VIEW

This doesn't really apply to rFactor, Automobilista or GSCE but since this is a triple screens setup guide it's worth mentioning.

And going back very quickly to the right triangles, we already know that "A = invTan(a/b)" and that we need to double "A" in order to get the entire monitor angle and to halve the width of said monitor in order to get to "a". All of that gives us the formula: MonitorAngle = 2 x {invTan x [MonitorWidth ÷ (2 x ViewingDistance)]}.

So... You can simply calculate the total horizontal FOV by multiplying A by 6 instead of only by 2. As in 3 monitors times 2. That happens because there are three monitors but we are only calculating half of the viewing angle.

How to calculate the proper horizontal FOV:




4. ADDITIONAL TIPS AND ADJUSTMENTS

It goes without saying but in case you're in doubt, yes, the screen bezels' width must be corrected within the NVIDIA or AMD control panels regardless of the other calculations or adjustments in order to achieve a seamless transition between the screens.

Raise or lower your screens and/or seat in order to align your eye line with the middle of the screens that way you won't be constantly looking up or down in search for the horizon but facing forward in natural line as you should and as you do in real life. Ideally your eye line must align to the middle of the screen up to 20% above of that (or between 50% to 60% up from the bottom of the viewable area) but no more.

Always try to get as big of a screen as possible and sit as close to it as you can since the closer your eyes will be to the image the lower the FOV you'll be able to use and the best visual experience you will get.

Turn off things like "virtual arms" and "virtual steering wheels", since you already have you real ones...

Level the horizon for the cockpit view of your favorite cars in your vehicle .CAM files:



Remove all the artificial cockpit vibrations in your PLR files.



This is not at all essential but I'd recommended you to customize and to attach a hood and skirts to your monitors as it will improve your experience by blocking potential distractions and by eliminating or reducing reflections (and will make your rig look even cooler). I cut MINE out of simple styrofoam sheets and then wrapped it in "carbon fiber" film, but you can use a whole bunch of other different materials to achieve similar or even better results.

And that's it for now. Later on I'll be adding more information on what to look for when choosing the right TV for sim racing as well as how to improve the overall eye candy factor for the various sims.

Mathematical perfection for practical application at its best!

Enjoy! ;)[/QUOTE]
 
Last edited:
Very nice write up, thanks! However i have two questions. First i cant find "INV" on any calculator. I cant remember my math, lol. Tested some scientific ones from windows 10 to online ones and not a single one has "inv". Ive seen "in" on some of them but not in Win10's version. Not sure if "in" is the right one?

Thank you!
 
Last edited:
This guide was a little confusing. I see the in-game FOV setting. Was that the one you're talking about? Is there some file I have to edit for anything?

I'm using NVIDIA, surround, bezel-corrected triples with AMS multi-view and it's pretty clear the game isn't taking the bezels into account. How could it? I didn't tell it the width.

I have this working in iRacing. How do I get it working in AMS?

I have a feeling we're talking about different things when we say "bezel-corrected". I used the NVIDIA Surround tool to deal with bezels but they only make sure everything aligns - they don't do what iRacing does with the width you tell it for the bezels (ie. hiding the image behind the bezel so it's not overly stretched).
 

Latest News

Shifting method

  • I use whatever the car has in real life*

  • I always use paddleshift

  • I always use sequential

  • I always use H-shifter

  • Something else, please explain


Results are only viewable after voting.
Back
Top