Review 01 640 matches logged Score 9.1
Server Notes emblem Server Notes Online games, measured at the wire
Review · Racing

Slipstream Nine Is The Only Game We Have Tested That Survives A Deliberately Terrible Connection

A hundred and twenty-eight ticks, rollback that tells you when it has corrected you, and six hundred and forty matches including a hundred and sixty on a throttled tether at a hundred and ninety milliseconds. It was still a driving game. We have no other example of that.

Score 9.1 · 640 matches logged · Tick rate 128 Hz

We keep a connection profile specifically designed to ruin online games. It is a mobile tether, deliberately throttled, with variable latency around a hundred and ninety milliseconds and occasional loss. Forty games have gone through it. Thirty-nine of them stopped being the game they are.

Slipstream Nine, on that connection, is a racing game where you can still trade paint through a chicane and know who was ahead.

Two sleek hover racers streaking through a neon-lit tunnel with teal and orange light trails reflected on a wet track surface
Contact at speed is where every other networked racer gives up. Here it resolves, and when it resolves against you the game says so.

The number first

A hundred and twenty-eight ticks, derived from packet timing and stable across every session we logged. The archive median is twenty-eight. This is a fourteen-person studio doing four and a half times what most publishers consider adequate, which is the answer to anybody who claims tick rate is a budget question.

It costs them, obviously. Lobbies are capped at eight cars where competitors run twenty-four, and there are five regions rather than eleven. Both are deliberate trades and both are correct: eight cars that agree with each other are worth more than twenty-four that do not.

Connection profileMedian RTTCorrections/matchTesters calling it playable
Fibre, near region14 ms0.1100%
Cable, near region31 ms0.398%
Congested shared line88 ms0.993%
Throttled tether187 ms2.486%
Throttled tether, far region261 ms4.161%

Rollback that admits what it is doing

The reason the throttled figures hold up is not that corrections stop happening. They happen more than four times as often as on fibre. The difference is that the game shows you a small marker at the edge of the screen at the exact moment the server overruled your client, and it never silently moves your car.

This sounds like a minor interface choice and it is the most important design decision in the game. A correction you can see is information. A correction you cannot see is the game cheating, and our testers describe it in exactly those terms in every other title where it happens invisibly — including Verge Squad, which is otherwise excellent.

Players do not need a perfect connection. They need to know which of the things that just happened were real.

What it refuses to simulate

Not everything is authoritative, and the honesty about which parts are not is the second thing that makes this work. Cosmetic debris, spectator camera positions and the trailing light effects are all local and disposable. Position, contact and lap timing are server-resolved and never negotiated.

The result is that when two cars touch, both players see the same collision within a frame or two, and the one who loses the position loses it for a reason. Our testers logged four hundred and eleven contact events on the throttled profile and disputed nineteen, which is a rate no other racer in the archive approaches on any connection.

Five regions and an honest queue

Five hosting locations, and a matchmaking screen that shows your estimated round-trip time to each one before you commit. If nothing under a hundred and twenty milliseconds is available it tells you that, gives you the numbers, and lets you decide.

Compare Frost Relay, which has one region and simply never mentions it, or Banner Fields, which will happily put you in a four-hundred-player battle at two hundred and forty milliseconds without comment. Telling the player the truth costs nothing and almost nobody does it.

MeasureSlipstream NineArchive median
Tick rate128 Hz28 Hz
Hosting regions54
Visible corrections per match0.43.6
Correction indicatorYesNone
Latency shown before matchingYesNo

What is actually wrong with it

Two things, neither of them about the connection. Eight cars is a thin grid and the game's own track design keeps implying a larger field, particularly on the two widest circuits. And the reconnection window is only forty-five seconds, which on the throttled profile cost us eleven abandoned races that a two-minute window would have saved. Spore Depths holds a slot for four minutes and it costs that game nothing.

The short version

  • A hundred and twenty-eight ticks from a fourteen-person studio.
  • Playable on a throttled tether at a hundred and eighty-seven milliseconds.
  • Visible correction marker; the car is never silently moved.
  • Nineteen disputed contacts out of four hundred and eleven on the worst profile.
  • Latency to each region shown before you queue.
  • Eight-car grids and a forty-five-second reconnection window are the real limits.

Verdict

Nine point one, the highest score we have given, and it goes to the game with the smallest team and the fewest cars on track. Everything this desk exists to argue is demonstrated by the fact that those facts are not in tension.