Lumen GI and Reflections feedback thread

[Krzysztof.N]

@BananableOffense

It’s only visible in screen traces and seemingly only in the direction of the reflective surface’s normal.

Maybe something with r.Lumen.Reflections.SampleSceneColorNormalTreshold, which is designed to prevent to sample wrong side of the mesh.

@BananableOffense

I’m probably missing something but I can’t see any difference besides light transmission. That said I’m currently quite pleased with the state of lighting on foliage. Reflections on the other hand can be problematic.

This hit skip is only active for GI and can be toggled with r.Lumen.ScreenProbeGather.ScreenTraces.HZBTraversal.SkipFoliageHits. If a hit is skipped then it will be continued using world space traces. The idea here is that two sided DF are dithered to they should leak light and make foliage occlude less.

@BananableOffense

Is it possible to have a per mesh or better yet material option to skip screen tracing lighting and/or reflections (preferably independently)? I’m often quite happy with them, but there’s usually a few problem meshes and materials and it feels like the only solution is to disable traces entirely which is a bummer.

Anything set per mesh or material would require to add a bit to GBuffer and GBuffer space is at premium, so unlikely to happen unless it’s undoubtedly a critical and must have feature to ship.

We could do some kind of skips based on data which is already there, like shading model. For this we need just need to figure out a common need, so that we add something that is useful for most people.