Unreal Engine 5, [UE5 Developer Availability 2022-04-05]

[Scott_Arm]

Maybe they cone trace the size of a pixel and that’s how the select vertices. If the model is stored as a hierarchy you stop at the level where the polygon vertices are slightly larger than a pixel.

 

[j^aws]

Nanite is using REYES, and its general pipeline (from Wiiki) for reference:

1. 1) Bound. Calculate the bounding volume of each geometric primitive.
2. 2) Split. Split large primitives into smaller, diceable primitives.
3. 3) Dice. Convert the primitive into a grid of micropolygons, each approximately the size of a pixel.
4. 4) Shade. Calculate lighting and shading at each vertex of the micropolygon grid.
5. 5) Bust the grid into individual micropolygons, each of which is bounded and checked for visibility.
6. 6) Hide. Sample the micropolygons, producing the final 2D image.

Epic have essentially turned the GPU into a glorified software renderer. About time! I recall posting a bunch of speculative threads on these forums around 15 years ago with the Cell architecture doing REYES with PS3. Obviously that didn't come to fruition, but it's great to see the status quo being shaken in the industry. I can see both Sony and Epic collaborating with a similar vision for realtime rendering progressing.

 

[manux]

The plot thickens

https://twitter.com/x/status/1261099569426751488

 

[Strange]

Whats up with this? There seems to be some issue with a dynamic object casting shadows due to a dynamic light source.

Isn't that the shadow cast by the hand being below the light source?

 

[tinokun]

I recall posting a bunch of speculative threads on these forums around 15 years ago with the Cell architecture doing REYES with PS3.

I remember this happening:

Please... i don't want to see the R word... Ever. Again.


Whoever you are, you know who you are, you know what i'm talking about.

With "the R word" London-boy meant REYES, of course. And then:

Hmmm...

HOS and HDR on RSX to get a 'football' looking like a real football similar to that image.

Perhaps some CELL post processing to get motion blur like on the feet of that footballer too...

Also, maybe physics aware tesallation to get some nice football/cloth simuations with CELL + RSX. Would be neat...maybe they'll include a geometry shader?

That was funny as hell.

 

[Entropy]

How will this affect a games total size of assets?
The upcoming consoles have quite limited storage space and multi-TB expansion is not going to come cheap for the foreseeable future.

 

[Shifty Geezer]

How will this affect a games total size of assets?

They'll adjust assets to fit.

 

[AlNom]

They’ll maybe want to be doing instancing a fair bit to make the most (re)use of assets. For example, breaking down the statues to be built from smaller components would allow for some variation.

 

[Karamazov]

warning devs, if a see two identical stones in a same level, i want my money back !

 

[Ike Turner]

So Lumen is essentially what Sebbi did in Claybook (Ray tracing SDF via compute among other things like VT etc). Wonder how he feels about it now (as Epic & Brian Karris desperately wanted to hire him).

 

[Ike Turner]

They’ll maybe want to be doing instancing a fair bit to make the most (re)use of assets. For example, breaking down the statues to be built from smaller components would allow for some variation.

The whole demo is literally made with what looks like less than 15 assets all instanced and mixed & re-meshed together.

 

[AlNom]

Quite.

 

[chris1515]

The whole demo is literally made with what looks like less than 15 assets all instanced and mixed & re-meshed together.

https://quixel.com/megascans/collec...nt&category=natural&category=limestone-quarry

This is all the rocks assets they used for the demo

 

[Ike Turner]

https://quixel.com/megascans/collec...nt&category=natural&category=limestone-quarry

This is all the rocks assets they used for the demo

From the looks of it only a small portion of those are used in the demo (in conjuction with other scans from their other libraries). Which is how things have been done for years anyways. they are just using the high poly ones instead.

 

[PSman1700]

Epic have essentially turned the GPU into a glorified software renderer. About time!

That's what some members have been saying yes, moores law isn't dead yet regarding GPU's.

 

[Dictator]

Isn't that the shadow cast by the hand being below the light source?

Yeah it is shadow maps so it is just a bit overly sharp, (hand close to a bulb Light would produce a large diffuse shadow).

 

[Shifty Geezer]

So Lumen is essentially what Sebbi did in Claybook (Ray tracing SDF via compute among other things like VT etc). Wonder how he feels about it now (as Epic & Brian Karris desperately wanted to hire him).

Vindicated, as he adds it to Unity?

Actually, I feel a little vindicated. We talked about alternative GI solutions in the RTRT discussion, and it clearly is a workable solution for next-gen.

 

[function]

The idea of going heavy on software rasterization makes me consider Sony and MS's respective approaches this time round.

In the Road to PS5 presentation, Mark Cerny talked about how "fast and narrow" was "the tide that raises all boats". But with compute based rasterization, wouldn't that leave fewer boats to raise? The hardware rasteriser, RBs, tessellation unit and to some extent the L1 (unlike the L0 and L2 it's described repeatedly as a "Graphics L1" in the RDNA whitepaper) would surely be of relatively lesser importance for this approach....?

We don't know how PS5 and XSX stack up in terms of ACEs and Command Processor sauce whatnots, but we do know XSX has both more compute and more bandwidth / Flop to feed it (terrible metric but it seems to get used a lot!) ... so perhaps, ironically, this demo would have been most at home on XSX.

... in which case Sony would have made a really canny move by signing this multiplatform engine demo (not even a game demo!) as a Sony promotional exclusive. Bravo! *tips fedora*

 

[Karamazov]

or in the case of that demo it might be more important to have the double of SSD speed than 20% more GPU power.
who knows. UE5 devs know. We'll have answers soon.

 

[Deleted member 86764]

The idea of going heavy on software rasterization makes me consider Sony and MS's respective approaches this time round.

In the Road to PS5 presentation, Mark Cerny talked about how "fast and narrow" was "the tide that raises all boats". But with compute based rasterization, wouldn't that leave fewer boats to raise? The hardware rasteriser, RBs, tessellation unit and to some extent the L1 (unlike the L0 and L2 it's described repeatedly as a "Graphics L1" in the RDNA whitepaper) would surely be of relatively lesser importance for this approach....?

We don't know how PS5 and XSX stack up in terms of ACEs and Command Processor sauce whatnots, but we do know XSX has both more compute and more bandwidth / Flop to feed it (terrible metric but it seems to get used a lot!) ... so perhaps, ironically, this demo would have been most at home on XSX.

... in which case Sony would have made a really canny move by signing this multiplatform engine demo (not even a game demo!) as a Sony promotional exclusive. Bravo! *tips fedora*

Depends on how much of it pushes the SSD. If that demo uses the SSD at near peak-IO, then it's feasible that it could *only* be done on PS5.