Build a procedural voxel flight sim for a tiny ESP32 OLED

A hobbyist had Claude write an endless voxel flight sim for an ESP32-C3 SuperMini and a 0.6 inch 64x64 OLED, in integer maths at 30 fps, and released it under MIT.

Done withClaude· Nov 18, 2026

What they did

The developer behind the voxel-flight repo wanted to see how far an ESP32-C3 SuperMini and a 0.6 inch 64x64 SSD1357 OLED could be pushed. They described what they wanted to Claude in conversation and gave feedback from watching the screen, while Claude wrote and tuned all of the code. The result is one Arduino sketch: a ray-marched voxel renderer over a streaming 256x256 map with five biomes, cities with lit windows, suspension bridges, clouds, a day and night cycle, an autopilot that follows valleys and does loops, and DMA display output, all in integer maths because the chip has no floating point unit. Claude also wrote USB capture tools to turn screen frames into GIFs.

How it went

The author reports a smooth 30 fps on the real screen and published GIFs captured from the device. The project runs from two modules and seven wires, with the board's BOOT button picking one of three planes. The SparkFun OLED library needed two local patches to build for the ESP32-C3, documented in the README. The repo was created on 18 November 2026 and is MIT licensed.

Worth knowing

This is a README, not a write-up of the process, so there is no count of sessions, prompts or failed attempts. Updating the SparkFun library undoes the two patches. The README names Claude but not the model or whether a coding tool was used.

Try it

With Claude· 5 parts to fill in

Help me build [a game or demo] for [my microcontroller] driving [my display, size and controller]. Ask me for the pin wiring and libraries first. Write it as a single sketch for [Arduino IDE or PlatformIO], within the chip's RAM and flash, and use integer or fixed-point maths if the chip has no FPU. Aim for [target frame rate]. After each version, tell me what to look for on the screen and wait for my feedback before changing anything else. Stop when I say it runs as I want, then write a README with wiring, build steps and any library patches.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related