2LA is a full-scale Las Vegas → Los Angeles point-to-point racing game built on real-world road geometry — roughly 250 miles of Interstate 15, generated from OpenStreetMap and USGS elevation data. This is our development roadmap: a phased path from the finished technology proof-of-concept to the first playable game modes. The order is deliberate — each phase unlocks the next.

Route: Las Vegas → Los Angeles · I-15 · ~250 mi. The full-route tech leads into Cannonball Run; the arcade Checkpoint Race stages follow.

Legend: ✅ Done  ·  🟩 To do  ·  🏁 Game mode  ·  ⚑ Biggest gap


✅ Mile 0 — Technology Proof-of-Concept

Status: ✅ Done. Complete and verified on a real ~21-mile slice of I-15 through Baker, CA. A drivable world — not yet a game. Everything below turns it into one.

  • ✅ Offline route pipeline — OpenStreetMap + USGS elevation baked to a compact track file.
  • ✅ Runtime world generation — drivable road, graded off-road terrain, invisible containment walls, and scenic context roads (opposing carriageway + ramps).
  • ✅ Setpiece base levels — building massing, landmark markers, and sign anchors baked in as editable blockout for artists.
  • ✅ Project renamed to 2LA — under version control, with a reviewed code baseline.

1️⃣ Phase 1 — Finish the Core Tech

Build order 1. Take world generation from one 21-mile slice to the full, presentable Vegas-to-LA route. Prerequisite for Cannonball Run.

  • 🟩 Theming pass — make it look like the Mojave: terrain materials, desert scatter, real signage from the sign anchors, guardrails, distant-mountain backdrop.
  • 🟩 Streaming subsystem — load the route a chunk at a time so the full ~250 mi is physically possible, not just one slice; upgrade to higher-resolution elevation data.
  • 🟩 Set-piece blending — stitch hand-built landmarks (Baker’s thermometer, etc.) seamlessly into the procedural route.

2️⃣ Phase 2 — Gameplay Foundation

Build order 2. The shared systems every mode needs, before either mode is written.

  • 🟩 Checkpoint system  ⚑ Biggest gap — a real checkpoint query API plus an interval crossing test so markers can’t be skipped at speed.
  • 🟩 Fast position lookup — an optimized “where am I on the route” query that scales to many vehicles at once.
  • 🟩 Lane placement — a lane-center query used for the player, for traffic lanes, and for wrong-way logic.
  • 🟩 Traffic AI foundation — oncoming and same-direction traffic, behavior varying by vehicle type (slow/predictable vs. aggressive).
  • 🟩 Vehicle — move from the placeholder template car toward the genre-classic pick.

🏁 Two destinations, built in order

Cannonball Run comes first — the direct payoff of the full-track tech: the whole real Vegas→LA route as one long-form timed dash. Checkpoint Race follows — 8 short, high-difficulty arcade stages on fictional layouts, once the shared gameplay systems exist.

3️⃣ Phase 3 — Cannonball Run 🏁

Build order 3 · Game Mode 1. The full continuous Vegas-to-LA drive as a playable, scored mode — the checkpoint-racer loop at real-route scale.

  • 🟩 Timed run, end to end — checkpoints extend the clock.
  • 🟩 Scoring & high-score list — persistent results for the long-form dash.
  • 🟩 Live traffic across the whole route — the Phase 2 traffic AI running end to end.
  • 🟩 Cross-country narrative framing — wrap the drive in its story.

4️⃣ Phase 4 — Checkpoint Race 🏁

Build order 4 · Game Mode 2. The arcade heart of the game — 8 short, sharp, high-difficulty stages. The mode that most resembles OutRun, Rad Racer, and Cruis’n USA.

  • 🟩 8 hand-authored stages — each 3–5 min, based on a distinct real section but a fictional layout tuned for challenge.
  • 🟩 Per-stage checkpoint / timer loop — escalating difficulty across the eight.
  • 🟩 Bonus stages between courses — time attack, police chase, a gas-fill minigame as pacing breaks.

∞ Later — Beyond the first release

  • 🟩 Additional vehicles & handling variety.
  • 🟩 Music / changeable radio.
  • 🟩 Further polish & replay incentives.

Leave a Reply

Trending