Subpixel rendering fails under binocular viewing and motion

What it is

On a desktop LCD, subpixel rendering (ClearType and its relatives) treats the red-green-blue stripes inside a pixel as triple the horizontal resolution for a glyph edge. In a headset the same trick reverses: the two eyes do not see the same stripe phase, a head movement changes that phase, and glyph edges pick up colour fringes that will not sit still. Stereo viewing and motion are not edge cases. They are the two axes on which the subpixel assumptions come apart.

Why it happens

Subpixel antialiasing leans on three assumptions: stripe layout known and identical for both eyes, a stationary observer, and the phase written at layout time being the phase each eye sees. Headsets often use two separate panels or a pentile arrangement, so left and right RGB geometry are not the same map. Even with matched panels, stereo puts a slightly different perspective on each eye: the same edge lands on a green stripe for the left eye and a red stripe for the right, and fusion turns the fringe into rivalrous colour flicker.

A head movement slides the edge across display pixels. The filter was computed for a static phase; once it slips, the filter points the wrong way relative to the real stripes, and the fringe sweeps. Low persistence or reprojection then recolours that fringe every frame. Greyscale antialiasing gives up the “triple” horizontal resolution for an edge that is stable for both eyes and in motion — and on a headset, stability is worth more than that extra sliver of sharpness.

Studying it

Compare subpixel and greyscale antialiasing on the same passage, in three regimes: monocular still, binocular still, binocular with rhythmic head motion. People report whether coloured fringes are visible, and reading errors are counted. Left- and right-eye captures of the same edge can show whether the chromatic fringe is out of phase.

Independent variables: antialiasing mode, mono / stereo, head motion on or off, panel layout (RGB stripe / pentile). Dependent variables: fringe report rate, rivalrous flicker, reading errors, subjective sharpness.

Judging ClearType on a desktop monitor with one eye closed will conclude “subpixel is still sharper” — because the third assumption still holds. Collect the result in a headset, both eyes on, with nodding allowed.

Where it stops holding

In strictly monocular, head-locked inspection (some industrial viewing), subpixel may still be slightly sharper; that is using the headset as a tiny monitor. If the panel is not a horizontal RGB stripe (many headsets are pentile or vertical), a filter written for desktop stripes mis-paints the edge more obviously. Video see-through stacks real-world pixels and virtual type on different sampling grids; there is no shared stripe to align. When type is already unreadable in greyscale because it is too small, subpixel will not buy the resolution back.

Applying it

• Default spatial body text to greyscale or signed-distance antialiasing. Do not ship the desktop ClearType toggle into XR.
• On device, with both eyes in and a slight nod, watch the glyph edge: a red-green fringe that will not sit still is the cue to turn subpixel off.
• Strip “optimised for LCD stripes” font rasterisation out of the XR path in the asset pipeline.
• How to check: capture the same line in each eye. If the chromatic fringe swaps sides or will not fuse, subpixel has already failed in stereo. Add a nodding clip; if the fringe recolours with the head, motion has failed too. A greyscale control should not show that fringe.

Related

• Same group: N3.04.1 Tilt sharply reduces readability · N3.04.2 Text must face the user · N3.04.3 Complex backgrounds need a backing plate · N3.04.4 Minimum readable size is jointly set by angular resolution and pixel density · N3.04.6 Line length and leading are set in angle, not physical length · N3.04.7 Text that jitters with head motion is harder to read than still text
• Nearby: N3.02 Interface Distance · N3.07 Content at the Edge of the Field of View
• Search terms: subpixel rendering · ClearType in VR · binocular chromatic aliasing