Methodology & editorial policy

Core formulas

• Horizontal FOV = 2 × atan( screen width ÷ (2 × eye distance) )
• Vertical FOV = 2 × atan( tan(hFOV ÷ 2) ÷ aspect )
• Screen width from diagonal = diagonal × aspect ÷ √(aspect² + 1)
• Triple total FOV = per-screen FOV + 2 × side screen angle
• Bezel-corrected FOV = 2 × atan( (3 × width + bezels) ÷ (2 × distance) )
• PPD = horizontal pixels ÷ horizontal FOV
• Fuel per lap (with margin) = practice consumption × (1 + margin%)
• Safe laps per tank = floor( tank ÷ fueled consumption )
• Stints = ceil( race laps ÷ safe laps per tank )

All tools implement exactly these equations; the test suite recomputes them against hand-verified values (for example: a 27" 16:9 screen at 60 cm subtends a horizontal FOV of about 52.6°, verified in both the calculator and the tests).

Sources & conventions

• Projection maths: standard perspective camera projection (the same model used in real-time graphics; see any computer graphics text on gluPerspective-style transforms).
• Triple screen geometry: planar arc model as used by sim racing rig guides; the seam-free condition is side angle = per-screen FOV, which matches the arrangement recommended across the community.
• Per-game FOV notes: based on the games' own settings documentation and community verification; we re-check each note when sims change their interfaces and log updates in the changelog.
• PPD reference bands: described as practical guidance, not measured thresholds.

Where a game hides its FOV behind an undocumented slider (some console titles), we say so on the tool page rather than inventing a mapping.

Known limits

• Curved screens subtend slightly less angle than the same width flat; treat the flat-screen number as an upper bound.
• Side screen angles in our total FOV use the simple planar model; extreme wraparound rigs (angle > 70°) distort, as do the images themselves.
• Fuel planning assumes stable consumption; wet races, traffic and saving change it, which is what the margin is for.

Testing & QA

1. Every formula has a hand-calculation test case that must pass before deploy.
2. Worked examples on pages are generated from the same functions the tools run.
3. Per-game notes change only with a changelog entry and a source.

AI use disclosure

Pages are drafted with tooling assistance and reviewed before publishing; every formula and claim is verified against the sources above. No invented statistics appear on this site, and anything unverifiable is labelled or excluded.

Corrections policy

Found an error? Report it with a source. Confirmed corrections ship within a week, are listed in the changelog, and credit is given where the reporter wants it.