Hacker News Reader

If I recall in the demo, they kept on referring to procedural generation, and so perhaps they have a few tricks up their sleeve for generating content (trees being an obvious example) that would be varied yet take up little memory.

View on HN

Procedurally generated assets take very little storage. They still take just as much memory to actually put into the scene graph and render.

Not with ray casting of sparse voxel octrees, which is probably what they're doing. Depending on how the procedural generation work, you only need to generate that which you render.

Not if your assets are functional, such as a procedurally generated heightmap. Then they take up next to no memory.

But you can't do that efficiently for a tree, I think.

Reply on news.ycombinator.com