Skip to the notes

Input-lag test equipment: what a reproducible report needs

A checklist for documenting press detection, response detection, timing and the full test chain.

Dana RehnTechnical editor

Filed Revised Nov 14, 20261 min read

Quick answer. An input-lag report needs a defined start event, a defined end event and a timing method. A list of gaming hardware alone does not establish measurement accuracy.

Define the signal being timed

Record how the button press is detected and how the screen response is detected. State whether both events use the same clock. If separate clocks are involved, explain synchronization and its uncertainty.

RTINGS' input-lag method describes a display-specific measurement method. That is useful context, but a display-only result is not a complete controller-to-screen measurement.

Record the chain

Part Information to retain
Controller Model, firmware and connection
Device under test Firmware, slot and script or fixture version
Console or PC System version, game build and scene
Display Model, refresh rate, mode and response location
Instrument Sensors, clock, sampling rate and calibration
Trials Conditions, sample count, order and exclusion rules

Resolution is not the whole uncertainty

A 1000 Hz sample stream has 1 ms between samples. Sensor thresholds, display scanning, clock alignment and event detection can introduce additional uncertainty. A large number of trials does not automatically eliminate systematic error.

Publication scope

This is a measurement checklist, not a claim that Zen Lab owns or has validated a particular rig. The earlier hardware inventory and photo references were removed where they could not be confirmed. See the method for how the site distinguishes sourced explanation from original results.

A figure looks wrong? Report an error

Further notes