Refresh rate jointly determines flicker visibility and motion continuity

What it is

How many times a second the panel lights is refresh rate. It governs two different things. Brightness has to be dense enough in time for flicker to fuse — critical flicker fusion (CFF). And the displacement of head and objects between two frames has to be small enough for motion to read as continuous, not stepped. One number, two axes: “do I still see it flashing”, and “does motion break into ticks”.

It does not explain why a pixel paints a smear on the retina, nor where brightness goes when refresh is raised.

Why it happens

CFF moves with luminance, waveform, and where in the field you look. Brighter, spikier pulses, and more peripheral, more visible flicker. A headset spreads bright pixels into a large periphery; 60 Hz that just passes on a desk monitor can flash at the visor’s edge. PWM dimming stacks another pulse train on top of refresh and lifts the fusion threshold again.

Motion continuity is a second ledger. The head turns by θ, the world must jump θ between frames; lower refresh, larger jump, thinner temporal sampling. Even with flicker fully fused, a slow refresh still turns a nod into discrete samples. “Not flashing” is not “smooth enough to turn in” — CFF can already be cleared while the sampling rate motion needs is not.

The two thresholds do not coincide. Hertz to kill peripheral flicker, and hertz to kill discretisation on a whip-turn, are often higher on the second. Taking “I cannot see flicker” as a refresh pass drops the motion axis.

Studying it

Flicker: classical CFF, vary frequency or modulation depth to the just-not-visible point; on a headset split centre and periphery, and control mean luminance. Motion: a forced choice of continuous versus stepped under controlled yaw, or pursuit of a target sampled at the refresh.

Independent variables: refresh rate, mean luminance, modulation waveform (steady versus PWM), centre versus periphery, head speed. Dependent variables: CFF threshold, motion-continuity judgements, pursuit error.

Report the two thresholds apart. A single “minimum acceptable refresh” that does not say whether it was for flicker or for motion will flip the next time luminance changes.

Where it stops holding

Dark scenes, small fields, central fixation: CFF drops and 60 Hz can be flash-free; the same panel showing a bright sky and peripheral UI will flash again. Age and fatigue move CFF; taking young-participant thresholds as a population refresh spec will be tight or loose depending on direction. LCD pixel response paints extra temporal blur on top of refresh, so measured “incoherence” is not sampling rate alone. Footage shot at 24 or 30 does not become denser because the display is 90; in-between frames are invented.

Applying it

• Write the refresh target as two sentences: no flicker on a bright periphery, and motion not stepped at the expected head speed. Meeting one is not a pass.
• Do not ship desktop 60 Hz experience onto a bright, wide-field, PWM-backlit visor.
• Accept in two probes: a static bright field at the edge, then a head turn.
• How to check: at the same luminance, first report flicker on a bright region at the field edge, then pursue a thin world-locked line at a product-typical whip-turn. If the line no longer flashes but still ticks, raise refresh on the motion axis; do not keep twisting brightness.

Related

• Same group: N1.12.2 Low persistence trades shorter illumination for less smear · N1.12.3 When the eye pursues a moving object, smear is paint on the retina · N1.12.4 Raising refresh rate lowers available brightness
• Nearby: N1.05 Motion-to-Photon Latency · N1.11 Render Latency and Motion-to-Photon Time
• Search terms: critical flicker fusion · refresh rate · temporal sampling