TL;DR
This page is a public-facing capability snapshot for Drivurs Racing.
It summarizes what the product model supports today:
- session start from a selected Garage vehicle,
- automatic and manual session behavior,
- run validity labels,
- run viewer graphs and metrics,
- saved sessions and uploaded leaderboard flows,
- and RaceBox-oriented setup guidance.
Garage to session handoff
Racing starts from a selected vehicle.
That matters because session history and leaderboard context should resolve back to the same Garage identity, not a detached one-off run card.
Session modes
Drivurs Racing supports:
- Auto Track for more automatic session handling
- Manual mode for broader session control when you do not want the app to finish the run automatically
See: Auto Track vs manual sessions
Run state and validity
Recorded runs can appear as:
- valid
- valid with warnings
- invalid
- incomplete
These labels exist so run history, best-time summaries, and leaderboards do not treat every captured attempt as equally trustworthy.
Run viewer
The run viewer supports the recorded-attempt layer:
- metric tiles
- graph views
- run-quality interpretation
- attached vehicle identity
The goal is to make the run explainable, not just rankable.
Saved sessions and uploads
Runs and sessions can be saved and later uploaded for leaderboard ranking.
That means the product model is:
- record the session,
- inspect the run,
- save or upload it,
- view its leaderboard context.
Device context
The current public guidance and setup documentation is RaceBox-oriented.
Relevant setup/reference pages: