[alkonaut]

“Micropolygon” I assume means Reyes rendering, I.e that the polygons are created on demand from underlying geometry. Instead of various LODs you tessellate when rendering, specifically for the view so each pixel has ~1 vertex. Walk closer to the statue and it gets more triangles in tesselation.

[Miraste]

But how is it running so quickly? I've seen adaptive rendering implementations before, but they couldn't run in real time. If they are really using billions of polys they can't store them all in VRAM. Is the PS5 SSD fast enough to recalculate polys for every model in the scene every frame (Or even every few frames)?

[alkonaut]

No details yet, but hopefully that will follow soon.

I don’t think the SSD but rather the GPU would be doing the tesselation...

Here is a good presentation on micropolygon rendering (note: nothing says nanite works like this at all): https://www.cs.cmu.edu/afs/cs/academic/class/15418-s12/www/l...

[Miraste]

> I don’t think the SSD but rather the GPU would be doing the tesselation...

Ha, I phrased that badly. I meant that, if the high-poly models can't all be stored in VRAM at once, is the SSD fast enough to load them back onto the GPU every frame?

[alkonaut]

If the tesselation is performed on the GPU (surfaces uploaded to GPU in some non-triangle representation e.g image geometry/SDFs/patches) then I don’t think it’s ever viable to have the tesselated triangles loaded back from GPU memory even to RAM (never mind disk). This isn’t a lot of data. 2 triangles/1 vertex per pixel is just 8K triangles and 4K vertices every frame, that can be overwritten each frame. This is tiny. It’s <1MB!

[Miraste]

Ah, that makes sense. I was thinking the problem lay in loading the original meshes, but I didn't consider they could be using a smaller non-triangle format. I really hope they share more about how this works.