Revive a shelved Earth-scale planet engine into a seamless space flight demo

A Redditor handed Claude Code a 2012 Unity prototype and, in four weeks, grew it into a 21,000-line C++ and HLSL engine with full-size planets, three landable moons and a city.

Done withClaude CodeCodex· Nov 19, 2026

What they did

The poster had parked a space game in 2012 after building a Unity prototype of an Earth-sized planet whose geometry is rebuilt every frame, so a ship can fly anywhere at any speed with no loading. Four weeks ago they gave that old code to Claude Code running Opus 5.5, with some work done in Codex. The agents wrote most of a roughly 21,000-line engine in C++ and HLSL, while the poster decided what to build and checked the results. Every feature started as a written spec, and the docs folder now holds more than 40 live specs. A single rules file is updated whenever the agent makes a mistake, and each experiment gets a git tag so a dead end can be rolled back. For each fix Claude writes a flight route of viewpoints across the planet, which the poster flies to check it. Claude also wrote the shot list for the demo video and drove the engine's cinematic mode frame by frame.

How it went

The old prototype ran again within a few prompts. The engine now has plate tectonics building mountains and islands, rivers carved on the GPU, wind-driven climate placing forests, deserts, snow and clouds, three moons you can land on and a small city with a spaceport. The poster has flown more than 70 check routes and made seven versions of the video in two days, reviewing each and sending notes. It is not a game yet: you can fly, land and walk around at full scale. It runs only on Windows and you build it yourself with Visual Studio 2022. Commenters praised the look but said the trip from orbit to ground felt too fast for a sense of gravity or atmosphere.

Worth knowing

The poster says the time goes into checking, not prompting, and that a single screenshot is not enough to judge a fix. Ship and building models start as generated 3D and are cleaned up by hand in Blender, then reviewed on close-up sheets because an automated check once wrongly called one clean. The code is source available on GitHub, not open source, as the poster clarified in the comments.

Try it

With Claude Code· 6 parts to fill in

I have an old prototype of [describe the project, e.g. a planet renderer] in [language/engine] at [path]. Get it building and running again first, then report what works. From now on, for every new feature, write a short spec in [docs folder] and wait for my approval before coding. Keep a single rules file at [path]: when I point out a mistake, update the rule, not just the one case. Tag each experiment in git so we can roll back. For every fix, give me a list of [viewpoints or test routes] to check it by hand, and stop after each feature until I confirm it looks right.

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

Where they said it

Related