N1.15.4visual performance decrementdesignresearch

Visual fatigue shows as a performance drop before subjective discomfort

Aliases: visual fatigue lag · CFF fatigue · delayed discomfort · task decrement

What it is

When the eyes start to tire, people still often say they are fine. What drops first is performance: slower search, missed words, worse stereoacuity thresholds, less accommodative facility. Spoken ache, dryness, headache catch up later. Putting “are you tired?” at the end of a session as the only meter writes a pass for someone whose performance has already been down for twenty minutes. Monitoring visual fatigue has to track the task curve. Subjective discomfort is a lagged confirmation, not the leading edge.

It does not explain how blinks or accommodation each tire; it says which of those changes arrives first in time.

Why it happens

Fatigue moves thresholds and speed before it moves awareness. Search does not yet feel costly when an extra regressive saccade has already replaced a useful fixation; reading accuracy has not collapsed when each line already costs a few hundred milliseconds more. Critical flicker fusion and accommodative facility — “how fast can I change gear / how fine a flicker can I still resolve” — shift down before ache. Subjective scales wait for symptoms to cross a reporting threshold, and that threshold is pushed up by task engagement, social expectation, and not wanting to break the experience.

So for one fatigue, the performance curve bends first and the discomfort curve later. Using the later bend to decide “should we rest” places rest after the bend has already happened. Games and demos make this easy: content holds people until nausea or frank eye pain, while misses and mis-aims are already in the log.

This is the same class of problem as sampling sickness during the experience, with a different stick: job scores and visual function here, not a sickness scale.

Studying it

Every fixed interval, drop in a short standard job: visual search, proofreading, stereoacuity or accommodative facility, plus a 0–10 ocular discomfort item. Plot both curves and find the time gap between the performance inflection and the discomfort inflection.

Independent variables: task load, session length, how intrusive the probe is. Dependent variables: job reaction time and error, CFF or accommodative facility, subjective ratings, the gap between inflections.

The probe must not become a new fatigue source: a thirty-second job is cleaner than doffing for a page of questionnaire every time. A control of equal-duration 2D near work is needed to split headset-specific lead time from ordinary near-work fatigue.

Where it stops holding

Very short experiences (a few minutes) bend neither curve; order cannot be seen. People who already have frank dry eye or uncorrected refractive error may have discomfort arrive with performance, or even earlier. Highly absorbing entertainment raises the subjective threshold so far that performance can be poor while people still report “fine” — that is not this claim failing, it is the lag stretching. If the job overlaps too little with the main skill (mental rotation as a stand-in for reading fatigue), the curve that bends is not the function being monitored. Lab payment makes people even less likely to report discomfort, artificially widening the gap.

Applying it

  • Do not set session caps from end-of-session satisfaction and discomfort items alone. Embed measurable short jobs on the critical task (search time, proof errors).
  • Trigger rest from the performance inflection: two consecutive slower or more errorful short jobs, interrupt. Do not wait for the wearer to say it aches.
  • In demos and dogfood, log “can they still hit / can they still read correctly” beside the spoken rating; when speech is optimistic, trust the job.
  • How to check: a forty-minute session, every five to eight minutes a thirty-second search plus one discomfort number. If search time rises first and discomfort later, this holds, and the rest mark belongs on the step where search time started up, not on the step where people started saying they were tired.

Related

  • Same group: N1.15.1 Blink rate drops during focused viewing and the ocular surface dries · N1.15.2 The brightness step at don and doff needs dark-adaptation time · N1.15.3 Staring at one depth for long accelerates accommodative fatigue
  • Nearby: N1.04 Vergence–Accommodation Conflict · N1.08 Headset Mass and Prolonged Wear
  • Search terms: visual fatigue · performance decrement · subjective discomfort

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/N1.15.4