Quick answer. An update can invalidate an older comparison, but a release date does not establish that latency changed. Check what changed, then decide which conditions need to be remeasured.
Source review versus a physical retest
A source review checks the current documentation and release notes. A physical retest collects new measurements under recorded conditions. The article must say which happened.
| Change | What to review |
|---|---|
| Device firmware | Input routing, compatibility and any timing claims |
| Controller or console update | Baseline behavior and connection settings |
| Game patch | The response scene and mechanics used in a test |
| Display or instrument change | Whether old and new measurements are comparable |
Preserve context
Keep the earlier version and source-check date visible when discussing an old result. Do not attach a newer update date to an old table and imply that it was retested.
Current scope
Zen Lab's current articles explain sources and test design. They do not claim that every firmware release has been physically benchmarked. An original result would need the setup, sample count and reproducible calculation described in the methodology.
A figure looks wrong? Report an error
Further notes
- Cronus Zen firmware latency: what release notes establish
How to separate firmware fixes from measured input-lag improvements. Release notes do not establish a fastest firmware.
- Input-lag test equipment: what a reproducible report needs
A checklist for documenting press detection, response detection, timing and the full test chain.
- How to measure an NBA 2K green window
A green window is a timing-response curve, not the same number as a script green percentage.