ATV 2PC & browser port

Setup and play

The game is built on your own computer from your own disc, and played in this site's game page from the files the builder made. This site never has the game: it sends only its own page code; your files go from your disk into your browser's own storage.

What you need

  • Your own copy of ATV Quad Power Racing 2 for the original Xbox, USA retail release, legally owned, with its files copied to a folder on your computer (the folder with default.xbe in it).
  • The builder (coming): a small package of this project's own code that turns those files into the game for your computer.
  • Edge or Chrome on a desktop computer, with WebGPU.
  • A gamepad is optional: the keyboard works, and any standard-layout pad drives player 1.
  • About 1 GB of free disk space for the build, and the same again in the browser's storage for the game files.

This browser

Checking…

The game page also needs cross-origin isolation (for shared memory between its threads). This site turns it on for its pages (and the PC launcher for its own); nothing to set by hand.

How it goes

  1. Copy your disc's files to a folder. The folder should hold default.xbe and the game's data files and folders next to it.
  2. Get the builder coming. It will be linked here when it is ready. It contains only this project's code and the open-source recompiler; no game code.
  3. Run it and pick the game folder. The builder checks default.xbe (its size and SHA-256 must match the USA retail release; other releases and modified copies are refused).
  4. It compiles locally. The recompiler translates the game's program to C and compiles it to WebAssembly (atv2.wasm) on your computer. Nothing is downloaded from this site, and the result stays on your computer.
  5. It writes your play folder, atv2-play (by default in %LOCALAPPDATA%\atv2-builder; the builder prints where): your game files (as links, so no extra space on the same drive), atv2.wasm and atv2-build.json (the builder version and the build's SHA-256).
  6. Play here. On the Home page, Play → Select local game files and choose that folder (you can paste its path into the folder window's address bar). The page checks default.xbe, and checks that atv2.wasm is exactly the build this site's game page was made for; then it copies the files into your browser's private storage (about 0.7 GB, less without the movies). After that, Play starts straight away, with no folder to pick.
  7. Settings: what you set on the Configs page is what the game here uses.
  8. Or play from the PC launcher: the builder also starts a local server at http://127.0.0.1:8460 and opens it (it answers only this computer); the Configs page's launch link opens it with your settings.

"atv2.wasm does not match this site": the site's game page and your build must come from the same builder version. Run the builder version the message names (it rebuilds in a few minutes) and select its folder again. "No atv2.wasm": you picked the game folder itself; pick the builder's atv2-play folder instead.

Default keys

  • Enter Start, Backspace Back
  • Z A (accelerate), X B (brake)
  • WASD left stick (steer and lean)
  • Arrow keys: d-pad (menus)
  • F1 or Esc: the game page's own menu

Change them

If something is wrong

  • "WebGPU is not available": update Edge or Chrome, and check that hardware acceleration is on in the browser's settings.
  • No sound: click the page or press a key once; browsers start sound only after that.
  • The pad does nothing: press a button on it while the game page has focus.
  • The folder is refused: only the USA retail release is supported, and the folder must be the builder's atv2-play (game files and atv2.wasm).
  • Start over: Home → Play → Forget game files removes the copy from this browser; your saves stay.
  • Saves: kept in this browser for this site (the PC launcher's are separate, for 127.0.0.1:8460). Back them up from the game page's Saves tab; the zip also opens on the Stats page.

Windows build

The same recompiled game also runs as a Windows program, with Direct3D 11. Its saves use the same folder layout as the browser's save backups, so they move between the two.