Peripheral quality is reduced to save compute
Aliases: gaze-contingent rendering · eccentricity LOD · foveal island
What it is
Foveated rendering paints full resolution only near the current fixation and lowers shading rate, shading quality, or geometric detail with eccentricity. It exploits the fall of contrast sensitivity away from the fovea, so a headset can keep sharpness where the fovea is inside a limited GPU budget. It is a rendering policy, not a way of measuring “what the user attends to,” and not a selection technique.
Why it happens
Cone density and cortical magnification both concentrate on the fovea. The same spatial frequency is far less resolvable at 10° eccentricity than in the center. Painting an entire binocular 4K×4K image to foveal standard hits fill-rate and power limits before perceptual return. Stratifying shading samples by eccentricity (sometimes with contrast-aware downsampling) removes most pixels from the pixel shader while leaving foveal sharpness intact.
How much is saved depends on island radius, transition width, and the peripheral floor. An island that is too small lets one bad gaze estimate show blur; one that is too large erases the savings. Degradation has to sit under the contrast-sensitivity curve, not as a uniform discount by pixel distance—a uniform discount is spotted immediately just outside the fovea.
Studying it
Guenter and colleagues, and later VR foveation work, expose a tunable eccentricity–quality function, ask whether peripheral degradation is visible, and record GPU time. Independent variables: island radius, transition, peripheral LOD floor, presence of contrast preservation. Dependent measures: detectability (yes/no or ratings), task scores (reading, search), frame time. Drive it from the headset’s own eye tracker; a desktop “simulated gaze point” undercounts head motion and lens distortion. Separate detection from work: finishing a search does not mean artifacts were invisible.
Where it stops holding
Low vision or foveal damage already changes the sensitivity map; an island cut for a standard observer will be cut in the wrong place. Uncalibrated or imprecise tracking parks the full-resolution island off-center, and the user sees blur in the middle and sharpness beside it—worse than no foveation. On a 2D desktop where people leave the screen often, the compute saved rarely justifies tracking-failure risk. Cinematic peripheral detail (moving objects in the dark) can still be caught parafoveally; “anything goes in the periphery” is false.
Applying it
- Fit the quality function to that headset, those lenses, and that population’s contrast sensitivity; do not copy another product’s island radius.
- Inside the GPU budget, protect foveal sharpness and the transition first, then decide how far the periphery can fall; do not pick a savings percentage and back into quality.
- Verify with reading and free viewing, collecting verbal reports of when blur or flicker is seen, plus frame time and whether the island keeps up with gaze.