3 ms·
Anyone who's watched that demo has noticed exactly what he said, that their demo is basically a 2D tilemap of a few repeated 3D objects, most likely to make the
by interrupt 15y ago
Anyone who's watched that demo has noticed exactly what he said, that their demo is basically a 2D tilemap of a few repeated 3D objects, most likely to make the memory requirements of storing voxels at that level of detail feasible.
- superfx 15y agoIf 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.
- cheald 15y agoProcedurally generated assets take very little storage. They still take just as much memory to actually put into the scene graph and render.
- wlievens 15y agoNot 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.
- skyfex 15y agoNot 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.