photoreal-gamea procedure for playable, photographic 3D from code
Everything in this build followed the photoreal-game skill: product before look; one dominant light with an environment for fill; material variation in albedo, roughness and normal; multi-scale composition; a filmic image formation chain; and executable gates instead of opinion.
The skill's order mattered. The title, race loop, settings, pause, save, touch path and failure states existed before the city was lit. Each art round changed one lever, was captured from fixed cameras, and was kept only if no gate regressed.
Title, race, pause, settings, save, touch, win/lose and restart are built first. A beautiful frame without a loop is a failure.
One shadow-casting sun down the canyon, a PMREM sky environment, a sky-tinted hemisphere and a cool bounce from the camera side.
Procedural asphalt, paving, four facade styles, metal, concrete, wood, rubber, cloth and water — all with more than one varied channel.
Kart, barrier, sidewalk, street wall, landmark towers and a distant skyline. Three scales and three depth layers in the hero frame.
HDR scene target, ACES tone mapping, bloom, FXAA, chromatic aberration, grain, vignette and a deliberate desaturation.
Render, census, collision, lights, product, mobile, playtest and look. The stock walker gates were re-expressed for a barrier-lined circuit.
Feature gallery
Thirteen screens from a 1600 × 900 high-quality capture session. The touch shot is 390 × 844.














Feature contact sheet · 13 shots · 1600 × 900 (mobile 390 × 844) · captured at a fixed seed.
Six rounds
Every round was captured from a fixed camera and a fixed seed. The next change came from the lowest gate/metric, not from the most interesting idea.
First light

Correct the circuit, compose the grid

Materials and colour

The signature surface

Hero object, city density

Product shell and a real loop

Tone, evidence, final captures

Process note
During the shell round, a multi-file batch edit overwrote the main game module and the page went blank. The module was reconstructed from the build transcript, all 25 later patches were replayed, and every subsequent round was committed to a local checkpoint before the next edit. The record above is the real one, including that failure mode.
Iteration gallery
Every fixed-camera round, including the ones that were reverted. The contact sheet at the bottom is the whole build on one page.













Contact sheet · 16 frames · fixed seed 20261114 · every frame generated at runtime.
Gates
The final build was checked with the skill's executable contracts. The stock walker/cargo gates were re-expressed for a racing circuit.
| Gate | What was measured | Result |
|---|---|---|
| Product | Title, race, pause, settings, lost, won, persistence, touch, 4-step objective, roles/tools, HUD, audio, two cameras; 635 draw calls / 539,243 triangles / 4 lights | PASS |
| Mobile | 390 × 844; no horizontal overflow; title usable; touch UI present | PASS |
| Census | 435 meshes / 759 instances; 0 failures; no nearby prop without identity | PASS |
| Lights | 4 lights, every one anchored to a fixture (or sun/sky) | PASS |
| Playtest | 31 checks: title/race, pause/settings, save, accelerate, drift/turbo, full 4-lap finish, timer fail, wreck, restart, barrier push/stop, open road | 31 / 31 |
| Look (fallback) | No external reference by project constraint. Hero: clip 0.01/1.63%, midtones 67.0%, flat 0%. Close: clip 0.07/2.08%, midtones 64.8%, flat 7.0% | PASS |
| Collision (adapted) | 204 barrier AABBs; edge push stops at 5.10 m; road remains open forward; wall clamp while driving | PASS |
| Offline | No external image/font/script requests; Three.js r169 inlined; all textures generated by canvas | PASS |
What is still not photoreal
- The kart is a code-authored low-poly kit. At 2.6 m the wing, seat and arms still read as designed primitives, not a manufactured vehicle.
- The city is box massing with a facade atlas. From above it reads as a block diagram; from the street the facades carry the scene.
- The spectator set is intentionally minimal; the crowd is two instanced draws, not individually modelled people.
- No external reference imagery was permitted, so the look gate is tone + emptiness, not a similarity score.
- No mobile GPU profile was captured; the mobile preset defaults to MEDIUM and the quality selector exposes LOW–ULTRA.
What the player can do
- Race four laps from P6 to the podium; drift for nitro, release for mini-turbo, spend it on the straights.
- Hit six boost pads, dodge three cone zones, survive barriers and rival contact; repair at each lap.
- Win at P1–P3, lose to the 4:00 clock, a wrecked chassis, or a P4+ finish; restart in one action.
- Persist best lap and best finish; change sensitivity, volume, FOV, invert-Y, quality and mute.
- Play with keyboard + mouse or touch at 390 × 844; look around with a drag.
Privacy & data
No analytics, cookies, tracking, external requests or personal data. The game stores only the best lap, best position and settings in localStorage. The screenshots were captured headlessly at a fixed seed; the names in the game are fictional. The site is static: no server, no account, no comments.
Credits
Method
- photoreal-game — the procedure, the art-direction brief, the iteration loop and the acceptance gates.
- Rendering: Three.js r169 (MIT), inlined into the single HTML; no network loader.
- Assets: every city block, facade, road texture, kart, tree, spectator, sign, particle and sound is generated by code at load time.
- No reference imagery was used; no external assets are requested.
License
- Original game code and generated content: MIT. See LICENSE.
- Three.js r169: MIT; full notice in THIRD_PARTY_NOTICES.md.
- The site is a static folder; deploy it to any GitHub Pages branch or subfolder.