Studio · Method, rig and refusals No advertising, no sponsorship
Controller Down emblem Controller Down Reviews that start at your hands
The studio

A very small desk with a camera pointed at a monitor

Controller Down is an independent games review site built around one idea: that the feel of a game can be measured, and that measuring it produces better criticism than describing it. This page explains the rig, the process and the things we will not do.

Why input first

A game is the only art form you operate. Everything else it does — the writing, the score, the level design — reaches you through a layer of buttons and sticks, and if that layer is wrong the rest arrives distorted. We think reviews should establish the quality of that layer before they discuss anything that sits on top of it.

The practical reason is more mundane: input is the part of a game most often described in language that means nothing. "Responsive", "tight", "weighty" and "floaty" are all doing real work in a reader's head and none of them carry a value. Replacing four adjectives with a number and then explaining what the number means is simply more useful.

What the rig is

A fixed test machine that has not changed configuration in nineteen months, one 60 Hz reference monitor, a 480 frame-per-second camera on a small tripod, four controllers, two keyboards, one arcade stick and three racing wheels. Nothing exotic and nothing expensive. The important property is that it does not change between reviews.

Response is measured by filming the screen while a finger presses a button, then counting frames between the button bottoming out and the first pixel change. It is a crude method and it is honest: it captures the whole chain, including the parts a game cannot see.

A testing desk with four controllers in a row, a camera on a tripod aimed at a monitor, and a notebook of handwritten figures
Process

What happens between receiving a game and publishing a review

Step 01

Measure cold

Before playing properly, we take 100 response samples per device on a clean save. Doing this first prevents familiarity from colouring the figure.

Step 02

Play to the end

We finish everything we score. Deaths and failures are logged with a note on whether the cause was visible on screen when it happened.

Step 03

Re-measure

A second set of samples after completion, on the final patch. If the two sets disagree by more than five milliseconds, we investigate and say so.

Step 04

Write, then check

Every figure in the finished text is checked against the log before publication. Anything we cannot support with a recording is removed.

What we refuse to do

  • No advertising and no sponsorship. There is no commercial relationship of any kind between this site and any publisher, platform or hardware manufacturer.
  • No scores in marketing. Our numbers may not be reproduced in promotional material. A figure separated from the measurement that produced it is misinformation.
  • No pre-release scores. We do not publish a number for a build that the public cannot buy, because the build we measured would not be the one they get.
  • No partial verdicts. If we did not finish it, we do not score it. Several games are absent from the catalogue for exactly this reason.
  • No unverified figures. Where a game publishes its own frame data, we check it before repeating it, and we report the errors we find.

Who writes here

A small group of three people who have been arguing about controller response for longer than is healthy. We do not publish personal details, contact routes or biographies, because none of that improves a review and it invites correspondence we have no way to handle.

What matters about the people writing is disclosed where it is relevant: which device a reviewer used as their primary, how many hours they played, and whether they had played the previous game in a series. Those facts appear in the reviews themselves.

Corrections

When a figure turns out to be wrong we change it, mark the change on the page, and keep the original visible. Measurements get corrected; scores are only revised when a patch materially alters what we measured, and every revision is logged on the scale page.