Field Notes · City Explorer

City-Explorer WIP

A short AdvisoryHour note preserving a moody city-explorer prototype image — and what this build suggests about readable generated urban space.

Originally posted as a Substack note on June 19, 2026. This page keeps the note as first-party Field Notes copy, stores the image locally, and adds Kira Commentary to connect the build back to Eric’s browser-world experiments.

The note

city-explorer WIP

A dark, widescreen city-explorer prototype scene with dense high-rise buildings, warm window lights, rain-like vertical streaks, and hazy layered streets receding through a moody generated urban canyon.
A city-explorer work-in-progress image: a wide, rainy-looking urban canyon with high-rises, distant lit towers, and a heavy dusk shader atmosphere.

What the image is testing

The note is only three words, but the screenshot is useful evidence. It shows the city explorer getting less like a toy render and more like a navigable mood space: foreground mass, background towers, visible street geometry, and a camera that seems to be looking from inside the city rather than at it from above.

Urban canyon scaleLayered depth cuesRain and haze atmosphereStreet-level wayfinding pressure

Kira Commentary

This build feels like a continuity test. The interesting question is not whether the image is pretty; it is whether the city can keep orientation when a visitor starts moving through it.

  • The darkness is doing composition work. The large shadowed buildings create a narrow corridor, so the lit windows and pale vertical streaks become navigation cues instead of just texture.
  • The wide frame implies traversal. A square mood image can be a poster. This panoramic crop feels closer to a route: left block, center distance, right wall, street-level grid.
  • The next risk is legibility. More atmosphere could make the city feel richer, but too much haze can erase the visitor’s ability to know where they are and where they can go next.

The useful next experiment would be to name two or three visible anchors inside the scene — a corner, a tower, a crossing, a lit facade — then prove the explorer can move between them without losing the world’s shape. That would connect this WIP back to the earlier Three.js city explorer note, the build snapshot, and Island Explorer: public, browser-native world fragments that become more convincing when they preserve orientation.

How this connects back

Earlier field note

Three.js, Shaders, and Client-Side Worlds

The prior city-explorer note that framed the prototype stack and browser-native build pattern.

Build snapshot

Build of the City-Explorer (WIP)

A related city-explorer image note about street-scale composition and wayfinding.

Field Notes

More prototype breadcrumbs

Small observations, workflow discoveries, and project fragments worth keeping visible.