Whiplash / Fatal Racing

Stunt tracks with a field of rivals

Fatal Racing, also released as Whiplash, builds its racing around loops, corkscrews and jumps as well as competition with other cars. The original game's presentation emphasizes contact, aggressive rivals and tracks whose changes in height make the next section part of the challenge. Choosing a car involves a balance between handling and acceleration, rather than simply selecting the highest top speed.

That describes the original game's appeal. The browser demo and an imported retail copy are different amounts of that game; the original marketing's complete track collection should not be mistaken for the contents of the demo.

Fatal Racing · original game presentation archive · ROLLER · project and demo documentation

Try the demo or bring a retail disc

ROLLER reconstructs the 1995 game for modern systems and provides a browser build. You can start with the bundled freeware demo or import data from your own retail disc. This gives the project two useful entry points: try the game before preparing files, or use a copy you already own to go beyond the demo.

The import accepts disc-image workflows, including a CUE with its associated BIN and audio files. Keep the related files together; selecting only the small CUE descriptor is not equivalent to supplying the disc data it references. Follow the launcher's supported selection flow for an ISO or a multi-file disc image.

ROLLER · project and demo documentation · ROLLER · web import, input and persistence implementation

Touch and tilt are separate choices

The web shell provides touch input and a motion-control option. Tilt controls depend on the browser granting motion permission; if permission is denied, the shell returns to touch input. On a phone, use landscape orientation so the game and driving controls have room. A rejected motion request is therefore a reason to choose the touch layout, not to repeatedly force the same permission prompt.

ROLLER · web import, input and persistence implementation

Keep settings and replays with the browser

The browser shell uses persistent local storage for game configuration, replays and custom tracks. Those records are separate from selecting the retail game data. Staying in the same browser profile preserves that local context; deleting site data can remove it. Treat a browser-data cleanup as a deliberate reset, rather than a routine step for switching from the demo to your own disc.

ROLLER · web import, input and persistence implementation