Description

Certain Lumen Hardware Ray Tracing CVars, when disabled in isolation, will not fall back to tracing the Global Distance Field, because the Global Distance Field is still disabled.

The function "Lumen::UseGlobalSDFObjectGrid(...)" from Lumen.cpp is missing entries for these settings, namely:

  • Lumen::UseHardwareRayTracedDirectLighting(...)
  • Lumen::UseHardwareRayTracedRadiosity(...)
  • Lumen::UseHardwareRayTracedShortRangeAO(...)
Steps to Reproduce

1. Download the Licensee's test project and open (see addl info URL)
2. Execute the console command "r.Lumen.Visualize 14" to visualize the Indirect Lighting
3. Observe that the indirect lighting is propagating the scene.
4. Execute the console command "r.GlobalDistanceField.Debug.ShowStats 1"
5. Observe that no stats appear - the Global Distance Field is not being updated.
6. Execute the console command "r.LumenScene.Radiosity.HardwareRayTracing 0"
7. Observe that the Indirect Lighting is no longer propagating in the scene (bug).
8. Observe that the Global Distance Field is still disabled (bug).
9. Execute the console command "r.Lumen.Reflections.HardwareRayTracing 0"
10. Observe that the Indirect Lighting is now propagating the scene.
11. Observe that the Global Distance Field is now enabled.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-265798 in the post.

0
Login to Vote

Unresolved
ComponentUE - Graphics Features - Lumen
Affects Versions5.5.4
CreatedApr 4, 2025
UpdatedApr 4, 2025
View Jira Issue