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

It always seems like there's some sort of occlusion rejection error in UE5, as the reflections are hybrid screenspace/worldspace it makes sense that there could be errors even with RT all set up.
I don't know of any categoric algorithmic errors (things are compared to the reference PT fairly frequently), but unfortunately there are still content details and approximations that can affect the output a lot. Specifically the quality of the BVH, but also sometimes managing the Lumen surface cache, particularly with complex meshes or lighting setups.

It's really great to be able to free artists in terms of light placement and such, and perhaps more importantly to just start to move towards the assumption that every light is shadowed! Conversely it was also a bit unfortunate to have to go back to a lot of chasing people about LODs, instance counts and the exact composition of how things are made in the scene. There's some wiggle room in that the RT scene does not need to be as high detail as the primary view, but when you use it more for direct lighting rather than just GI it starts to push the edges harder. And unfortunately there's really nothing we can do on the current generation to make things like BVH refits or TLAS builds any faster... the constraints on that side are effectively fixed until new hardware/APIs can help.

Regardless, great demo! Really cool to see, looking forward to details on how on earth this even works. Restir? Shadowmaps? Hybrid?
I presume there might be some talks at some point but seeing as it's all in the public source code/engine release, some high level points from my perspective **as of today** (this is all still very WIP, and will almost certainly change rapidly!):

1) Stochastic light sampling, but not ReSTIR
2) Handles local lights currently, all types (point, spot, rect, textured rect, etc)
3) Unrelated to the previous "raytraced shadows" path from UE4.
3) Raytraced shadows preferred (and used exclusively for the local lights in the demo), but can also be used for VSM SMRT projection, or a mix of both (selected per light, not a hybrid for a specific light). This is expected to be useful to folks who still need to use some VSM lights in cases where the RT geometry is not detailed enough. Ex. soft area lights use RT, sharp point/spot lights on detailed geometry possibly still using VSMs.
4) Per above, the path can still be useful even if no RT is being used at all, as it can accelerate and denoise VSM local lights pretty effectively. In scenes that are fairly well cached, this can be a performant option as SMRT projection performance could dominate in the past.
5) Directional lights not currently supported but no reason they couldn't be. Just less likely to be useful since they tend to affect every pixel anyways, tend to be sharper shadows, and suffer more from BVH quality/distance issues.

I am assuming shadows for area lights are also ray traced hardware shadows?
Correct. Per above the directional light is the only VSM in the demo, and it's only really visible as the soft moonlight and fog shafts.
 
Last edited:
Raytraced shadows preferred (and used exclusively for the local lights in the demo), but can also be used for VSM SMRT projection, or a mix of both (selected per light, not a hybrid for a specific light). This is expected to be useful to folks who still need to use some VSM lights in cases where the RT geometry is not detailed enough. Ex. soft area lights use RT, sharp point/spot lights on detailed geometry possibly still using VSMs
Awesome news! Previously Epic stated that they will streamline the shadow systems in the engine to just VSMs and RT, they said they will expand the use of ray traced shadows along side VSMs and mix and match between the two, I am so glad they kept true to their word and applied both techniques in a visually pleasing way.

there's some sort of occlusion rejection error in UE5, as the reflections are hybrid screenspace/worldspace it makes sense that there could be errors even with RT all set up
For reflections there are currently 4 levels of doing them in UE5. You pick the one that suits your desired visual output/performance.

Software Lumen: basic RT with all the above errors.

Hardware Lumen: more accurate non screen space reflections (though aliased and poorly shaded with less detailed materials and shadows).

Hardware Lumen with Hit Lighting: more precise non aliased reflections and properly shaded, also use proper materials and shadows.

Path Tracing: reflections are pixel perfect.
 
megalights looks very cool.

UE 5.5 roadmap here. Haven't read through or watched the fest video yet.


@Dictator
Hardware Raytracing
Release 5.5 has made many improvements to the underpinning systems which all fall into the external-facing hardware raytracing category (HWRT). These lower level systems all impact the performance and capabilities of Lumen, Path tracing, and Light Baking. There are improvements to asynchronous evaluation of raytracing code, improvements to caching and better management of acceleration structures. The intent of these changes is to make it feasible to utilize HWRT at higher refresh rates on platforms for which there is hardware support.

That megalights demo is live on a ps5? Jesus.
 
Last edited:

I always forget some of this stuff is available a lot earlier in the experimental branches or something. Megalights looked pretty good a month ago. I'm sure people will find some compromises, but it's fast.

 
That Mega Lights demo looked awesome. I can't see how any game on PS5 could ever look like that though.

Since Megalights are 'experiemental' in 5.5, it begs the question of how quickly the feature makes it into productions? Is it a feature that can just be turned on mid or towards the end of development? Those dictate the timeline for shipping games using the feature?
 
Since Megalights are 'experiemental' in 5.5, it begs the question of how quickly the feature makes it into productions? Is it a feature that can just be turned on mid or towards the end of development? Those dictate the timeline for shipping games using the feature?

Some features stay experimental longer than others. They really showcased it so maybe sooner than later. Maybe 5.6 or something?
 
Triangle RT, "hardware". In Lumen (and most RT implementations) screen space rays are still used together with triangle traces as well since the RT scene lacks detail in scenes of any significant complexity.

Took a quick look and it looks like probably the sweep in that one drone shot it at least partially because of some limitations in how many lights can currently affect the distant Lumen scene. In the future I imagine the goal is for this to be more stochastic as well, but currently the megalights sampling supports direct illumination/shadowing.
Thanks. That's great news and great work with MegaLight, the demo is really impressive (particularly when running on a PS5).

Please do not go back to software RT reflections (no character reflections pn mirrors and such reflective surfaces). That's a big regression for me (and plenty others I assume) and breaks whatever great the rest of the effects are doing for image fidelity. Like in Fortnite for instance everytime I don't see the reflections of my character.
 
The many shadow-casting light sources look very good. A significant leap compared to before. In Robocop, the many missing shadows bothered me.

Fantastic stuff. Hopefully this becomes the norm on the next generation of consoles. UE5 is killing it.

I hope they do deep dive videos on mega lights like they did for nanite and lumen. Wonder how many rays they’re casting per light per pixel and if there’s any sort of sample reuse involved.
 
I remember an nvidia video about rtxdi in their ue5 branch talking about how it enables lots of lights with less performance hit, is megalights pretty much the same thing? Ill go see if I can find the video in question and add a link if I can.
 
Back
Top