DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build a driving or racing level from a real road with Pixel Path

Use a real road from the map as the level for a driving, racing or endless-runner game.

  • Content
  • Advanced
  • 60 minutes
  • From the README
  • Claude Code

Who it is forAn indie game developer who wants a level based on a real place instead of a made-up track.

The problemHand-building a realistic road with buildings, hills and landmarks for a driving game takes far longer than the gameplay it supports.

The outcomeA real road baked from OpenStreetMap, with the pixel renderer and bake pipeline used as the base for a game built on the route.

What you need first

  • Claude Code
  • Node 18 or newer
  • Network access while baking (Nominatim, OSRM, Overpass, AWS Terrain Tiles, Wikidata)
  • Optional: a RetroDiffusion account with credit for real art, since placeholders cost nothing

Steps

  1. Clone the repo with git clone https://github.com/jonwheatley/pixel-path. (inferred, check the README)
  2. Read the commented pseudo-3D renderer in the repo, which the README describes as a renderer to read or build on.
  3. In Claude Code, ask the Pixel Path skill for a route between the two places your level should cover, and choose a level.
  4. Use the baked route folder as the level data, with its real buildings, ground and horizon.
  5. Add your own game logic on top of the renderer, such as speed, lanes or scoring.

Prompt for your agent

In the jonwheatley/pixel-path repo, read the commented pseudo-3D renderer and bake a route from <start place> to <end place> with the pixel-path skill. Expected output: a route folder and a short written summary of how the renderer draws the road. Verify that the route folder has index.html and that the summary names the renderer's main functions.

Caveat. The route has no traffic, no people and no weather, and driving routes only come from OSRM's car profile, so the game needs to supply any of those itself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page