Confirm action

AI LEARNS TO DRIVE

Training lab

Build a driver, train it, inspect the result.

Help & tutorial ↗
About & feedback

Simulator by Zorro909; interface and hosting by TiGa. Inspired by the game by ActivationFunction. Built-in tracks are reconstructed replicas. For supported conditions, the lab checks the run’s final fitness policy (or frozen input) with a bounded fresh replay. It predicts conditions only and does not award or accumulate original-game stars; opponent races and other unsupported conditions remain unchecked.

Uploaded files are used for the requested run. Results are held briefly in application memory and deleted after verified download or expiry. Browser recipes contain settings only. Read the data policy.

Cars are simulated behind the scenes. The map shows track layout, not moving cars.

Report a problem · Opens an editable draft for you to review.

Build: connecting…

New here? Start a first run Four steps, whenever you need them
  1. Choose a track

    Pick a built-in replica or upload your own track.

  2. Create a driver

    Choose a car and create a small starter network, or upload a network you already have.

  3. Review the settings

    The starter settings are ready for a short first experiment. You can save them as a recipe later.

  4. Run and inspect

    Start training, then download the result to inspect your drivers. A first run may not finish a lap.

Simulation

Creates a small network in this page only. It does not start a run or change saved recipes.

Training uses the selected recipe. Frozen evaluation runs the selected policy in a fresh car without changing its weights.

After each run, supported star challenges are checked with unchanged weights. Results are predictions, not game awards. How checks work.

Select or create a network below to enable training. Review Training & recipes before running.

Supports Formula, Rally, Snowmobile and Truck networks. Control outputs follow the original vehicle editor rules. Network shape and supported sensors are bounded by the original game contract.

Checking available backends…

CPU needs no sign-in. Checking optional GPU account connection…

Account help & troubleshooting

CPU works without an account. HF sign-in identifies GPU requests; it does not guarantee available allowance. Sign in before choosing files: sign-in reloads this page and clears selected files and unsaved edits. Saved recipes remain.

Your account token stays in page memory. Refreshing or closing this page disconnects the app. Disconnecting here does not sign you out of the HF website or delete job data.

Checks which account the GPU submission service sees. Runs automatically before GPU training; it does not check your remaining allowance.

Loading built-in replica tracks…

Choose an uploaded file or use a network from the browser editor.

Uploads are processed for this run. By default, the server copy is deleted after the browser verifies the download.

Optional repeat download

This is optional and resets after each run. When bucket auto-save is on, verified receipt must delete the server copy first, so repeat download is disabled. All results expire after five minutes. Data policy

Selected track & terrain

Loading selected track…

Asphalt Dirt Ice Start

Run & results

The browser keeps the received result in memory until discarded, replaced by a new run, or this page is closed. It is not saved to browser storage.

READY — no run started




Optional, read-only check for supported built-in tracks. It sends the track ID and best lap to this app server; Steam receives only a public leaderboard read. No score is submitted. The result is an estimate, not an official rank.

Reports use only server-reported run and generation fields. The engine does not report per-reward contribution, so reward weights are shown as configured values only.

Portable bucket bundle

Build, export, or restore one validated bundle. Bucket storage is optional. When connected, automatic save is on by default; turn it off here to keep saves manual. Disconnected runs never call bucket storage.

No bucket action has been requested.

Connect to an existing private bucket

Bucket storage is optional. Authorizing storage also identifies your account for GPU requests; ordinary GPU sign-in remains available with the basic identity permission. Then enter your existing private bucket ID. Connected runs automatically save by default; uncheck this option to keep run saves manual. No personal token is requested or stored.

HF describes the requested write-repos permission as read/write access to your personal repositories. That grant is broader than one selected bucket and is not a bucket-only permission; the app limits its own operations to the bucket you enter. The minimum current scope for bucket read/write has not been confirmed by HF.

Checking optional HF bucket authorization…

Not connected. Bucket storage is optional.

Ready. Inputs remain on this device until you run the test.

Effective training settings
Generation results
About star challenge checks

After a run, supported conditions are checked against its named policy with a bounded fresh replay. Results appear in the Star challenge check panel when available. These are predictions for the reconstructed replica track, not original-game awards; opponent races and unsupported conditions are left unchecked.