Too far lowers readability and pointing precision

What it is

Push the same settings panel four or five metres out and the letters are still there, the buttons are still there, yet reading needs a squint and a ray jitters between neighbouring items. Too far hits two capacities at once: each glyph gets fewer pixels on the retina, so readability falls; hand angular jitter is multiplied by distance, so pointing error grows in metres. It is the other end of the same distance axis as “too near hurts,” and it is not explained by type size alone — even when the letters still look acceptable, far pointing still drifts.

Why it happens

A headset has a finite pixel budget per degree. With physical size held constant, pushing the panel out shrinks the visual angle of each letter as the reciprocal of distance, so strokes land on fewer pixels. Serifs go first, then the counters of e, a, and 口. Stereo disparity also falls as 1/distance, so a far panel is almost a painting stuck to the sky, with little depth to grab onto as “I am aiming at this board.” People plant the ray in the empty air in front of or behind it.

Pointing travels on an angular-error channel. Controller or hand tremor is angular; linear miss ≈ angular jitter × distance. A 3 cm button that is hittable at two metres needs about twice the angular precision at four metres, and an unsupported hand does not get steadier. Far aiming also tends to raise the elbow, and fatigue then grows the jitter. Readability and precision fail together when the panel is too far; fixing one does not automatically fix the other.

Studying it

Hold the panel’s physical size and button size fixed and change only depth (for example 1.5 m, 3 m, 5 m). Run a reading-aloud task and a ray-selection task. Reading yields accuracy and rate; selection yields Fitts throughput or miss rate, plus the scatter of hits about the target centre.

Independent variables: panel distance, target physical size (held constant), input (ray / direct touch — far away, only the ray remains). Dependent variables: reading errors, completion time, selection misses, hit-point standard deviation, the subjective “can’t reach / can’t read.”

If the experiment grows the buttons with distance, the study is no longer about being too far; it is about distance with angular size compensated. To expose too-far, physical size has to be locked.

Where it stops holding

In a small room people never get to “too far” — four metres is often already a wall. Telescope-style viewing of a huge far screen can buy readability back by growing physical size, but ray precision still worsens with distance unless the input becomes gaze or something more stable. Optical see-through loses contrast at range, so too-far shows up as “melting into the background” before it shows up as “not enough pixels.” A device without positional tracking cannot even keep “the panel is N metres away” stable. A brief far landmark (an arrow, a place name) can spend detail; this leaf is about surfaces that must be read and hit.

Applying it

• Pull panels that need reading and precise selection back from the far wall into roughly the one-to-two-metre band, rather than making people walk up to them.
• Leave the far field for landmarks, status dots, and objects several people in the room must see together. Keep settings lists and text buttons closer.
• Grow the hittable region of a far ray target with distance, not only the visual size — hit rate drops before the look does.
• How to check: thirty selections of the same physically sized buttons at 1.5 m and at 4 m. A clear rise in misses at range, or letters starting to be misread, means the panel is too far. Do not only ask “can you see it.”

Related

• Same group: N3.02.1 Too near causes vergence conflict and a sense of pressure · N3.02.3 Type size must scale with distance
• Nearby: N3.09 Interface Distance and Comfort Viewing Distance · N1.04 Vergence–Accommodation Conflict
• Search terms: excessive interface distance · far-field pointing · angular error