Radiance Cascades
Radiance cascades is a ray-traced diffuse global illumination (GI) technique. It adds bounce light, colour bleeding and sky occlusion. It does not shoot random rays from every probe and denoise the result. Instead, it splits what each probe sees into distance bands. Close to a surface it samples few directions at many points. Further away it samples many directions at few points. The bands are stitched together, so the cost per frame is fixed and predictable, and a still camera settles on a stable image without random noise.
The renderer has three diffuse GI techniques, selected with Rendering.GI.Diffuse.Technique or a post process volume. Global Illumination compares them and covers the requirements and settings they share:
| Value | Technique | Notes |
|---|---|---|
| 0 | Screen probes (screen-probe RTGI) | The default. Random rays per probe, denoised over time. |
| 1 | Path traced | Full real-time path tracing. Replaces the analytic lighting and all other GI, and needs a path tracing pass in the render pipeline. |
| 2 | Radiance cascades | This page. |
Radiance cascades uses the same ray tracing backends as screen-probe RTGI. It uses hardware ray queries on GPUs with ray tracing, and the software BVH everywhere else.
Use radiance cascades
- Select a Post Process Volume that covers the area (or a global one), enable Override GI and set GI Diffuse Mode to Radiance Cascades. Without a volume, set
Rendering.GI.Diffuse.Techniqueto2. In the editor you can also pick it in the Quality Settings panel, under Global illumination › Diffuse mode. - Make sure a ray tracing backend is available:
- Hardware ray tracing needs
Rendering.RT.Enableand a GPU that supports it. - To trace in software, set
Rendering.GI.TraceBackendto2before the scene loads, because meshes build their software BVH when they load. The volume's GI Trace Backend property sets the same value while the volume applies. WithRendering.GI.TraceBackendat0(Auto), GPUs without hardware ray tracing use the software backend only ifRendering.RT.Software.Enableis on.
- Hardware ray tracing needs
- Switch the viewport to Render Mode › GI › Diffuse to check the indirect light on its own. In a game build without the render mode menu,
App.ViewRenderMode 24shows the same view.
GI as a whole must be on (Rendering.GI.Enabled), and Rendering.GI.RTGI.Enabled applies to both screen probes and radiance cascades.
How it works
Cascades. Cascade 0 places a probe on the visible surfaces every ProbeSpacing pixels (8 by default, 16 on the software backend). Each probe looks in 16 directions over a short distance. Every following cascade halves the probe density per axis, doubles the directions per axis and looks four times further. Five cascades reach from a few centimetres to MaxRayDistance (100 m). Rays that get that far take the sky.
Shared rays. By default (SharedRays 1), only cascade 0 traces. It casts one full-length ray per direction, and each ray is split across the cascades by how far it travelled before it hit something. Every direction of every cascade therefore gets a ray each frame, from a single trace. With SharedRays 0, every cascade traces its own distance band from its own probes. On the software backend a ray costs about the same whatever its length, so shared rays cut the trace cost by about the number of cascades.
Merging. A direction whose short ray finds nothing continues with what the next cascade's probes see in the same direction. The next cascade is only used where its probes stand on the same surface. Where they do not (at silhouettes, steps and thin objects), the ray's own result is used instead, so light never comes from a surface that the probe cannot see.
Stability. Probe positions and ray directions move through a fixed 16-frame pattern (Jitter). Each probe is averaged with its neighbours on the same surface and with its own earlier frames, and the diffuse stabilizer that is shared with screen-probe RTGI averages the frames. With Jitter off, the result is exactly the same every frame, but the probe grid shows as blotches and steps.
Multi-bounce and off-screen light
With MultiBounce on (the default), a ray that hits a surface that was visible last frame also brings back that surface's indirect light from last frame. Light gains one bounce per frame and settles within a few frames at unlimited bounces. Each bounce is damped by Rendering.GI.RTGI.ScreenFeedbackScale (0.8). With MultiBounce off, every pixel gets exactly one bounce. That is cheaper to reason about and slightly darker in deep interiors.
Screen feedback only knows surfaces that were on screen. Two options change what a ray hit gets when its surface was off screen or hidden last frame:
- Radiance cache (
Rendering.GI.RadianceCascades.RadianceCache, off by default, shared rays only). Ray hits take their later bounces from the world-space radiance cache, which the cascade rays train, instead of from last frame's image. A hit is then lit the same whether its surface is on screen or not, so the GI no longer brightens towards the screen edges. Spaces that are lit only through off-screen bounces come out as dark as the path tracer renders them, and ray-traced reflection hits take their bounce light from the cache too. The cache is tuned with theRendering.GI.RTGI.RadianceCache.*CVars. - Hit sky visibility (
Rendering.GI.RTGI.HitSkyVisibility, off by default, also used by screen-probe RTGI). Without the cache, a hit that screen feedback cannot light receives the whole sky above it, so enclosed spaces get sky light they cannot see wherever their walls are off screen. With this option on, such hits trace one visibility ray towards the sky instead. This removes the leak, but those hits then get no bounce light at all, so interiors that are lit mostly from off screen can come out too dark. Use it together with the radiance cache.
Radiance cache changes in 0.12
The world-space radiance cache is shared with screen-probe RTGI (Rendering.GI.RTGI.RadianceCache). In 0.12, cells that have not been trained yet no longer read as black, training weights rays and restarts only on well-sampled changes, and queries blend in the sky fill until a cell is trusted (Rendering.GI.RTGI.RadianceCache.TrustSamples, 1). Ray-traced reflections that read the cache stop flickering as a result.
Cost and backends
The cascades trace many short rays, which hardware ray traversal handles cheaply. On the software backend the ray count sets the cost. That is why SoftwareProbeSpacing defaults to 16, which traces a quarter of the rays of spacing 8 with slightly coarser bounce light. Halving either spacing quadruples the cost.
Stats under Renderer/GI/RadianceCascades/ report whether the technique is enabled, the backend, the cascade count, directions per frame, whether shared rays and multi-bounce are active, and the reason for a fallback when there is one.
Limitations
- Mono views only. Stereo (XR) views fall back to screen-probe RTGI, and the stat
Renderer/GI/RadianceCascades/StereoFallbackreports it. - Probes stand on visible surfaces, so the near field is resolved per probe (every 8 pixels, or 16 on the software backend), not per pixel. Thin features between probes take the light of the most similar nearby probes.
- The Vulkan backend shares the shaders, but radiance cascades has only been tested on DX12.
CVars
The settings marked Quality panel also appear in the editor's Quality Settings panel under Diffuse: radiance cascades.
| CVar | Default | Description |
|---|---|---|
Rendering.GI.Diffuse.Technique | 0 | 2 selects radiance cascades. |
Rendering.GI.RadianceCascades.Cascades | 5 | Number of cascades, 1–6. Quality panel. |
Rendering.GI.RadianceCascades.Directions | 4 | Cascade-0 directions per octahedral axis, 2–8 (4 = 16 directions). Quality panel. |
Rendering.GI.RadianceCascades.ProbeSpacing | 8 | Cascade-0 probe spacing in pixels on the hardware backend, 2–32. Quality panel. |
Rendering.GI.RadianceCascades.SoftwareProbeSpacing | 16 | Cascade-0 probe spacing in pixels on the software backend, 2–32. Quality panel. |
Rendering.GI.RadianceCascades.SharedRays | 1 | Hardware backend. 0 = every cascade traces its own band. 1–4 = only cascade 0 traces, with this many full-length rays per direction. |
Rendering.GI.RadianceCascades.SoftwareSharedRays | 1 | The same for the software backend. |
Rendering.GI.RadianceCascades.YoungProbeRays | 0 | With shared rays: rays per direction for probes that just came into view (at most twice the shared rays). 0 = no extra rays. |
Rendering.GI.RadianceCascades.YoungProbeFrames | 4 | Probes with less history than this many frames count as young. |
Rendering.GI.RadianceCascades.MultiBounce | true | Unlimited bounces through last frame's GI. Off = one bounce. Quality panel. |
Rendering.GI.RadianceCascades.RadianceCache | false | With shared rays: later bounces come from the world-space radiance cache instead of screen feedback. |
Rendering.GI.RTGI.HitSkyVisibility | false | Off-screen hits take the sky through one visibility ray instead of the whole sky. Shared with screen-probe RTGI. |
Rendering.GI.RadianceCascades.MaxRayDistance | 100 | Where the last band ends and the sky begins, in metres. Quality panel. |
Rendering.GI.RadianceCascades.NormalDetail | 0.5 | How much of the normal map the bounce light follows, 0–1. At 1, fine normal maps can show moiré at grazing angles. Quality panel. |
Rendering.GI.RadianceCascades.IntervalScale | 4 | Length of the cascade-0 band in multiples of the probe spacing at the probe's distance. |
Rendering.GI.RadianceCascades.MinInterval / MaxInterval | 0.1 / 2 | Clamp of the cascade-0 band length in world units. |
Rendering.GI.RadianceCascades.IntervalOverlap | 0.1 | Margin by which each band reaches into the next. |
Rendering.GI.RadianceCascades.NormalBias | 0.04 | Ray start offset from the surface. |
Rendering.GI.RadianceCascades.MergePlaneTolerance | 0.5 | How far a next-cascade probe may sit off a probe's surface plane before it stops continuing its rays. Lower = less leaking across depth edges. |
Rendering.GI.RadianceCascades.GatherPlaneTolerance | 0.03 | How far a probe may sit off a pixel's surface plane, as a fraction of view depth. |
Rendering.GI.RadianceCascades.GatherNormalPower | 4 | How strictly a pixel's normal must match a probe's. |
Rendering.GI.RadianceCascades.LightSampling | 0 | Light selection at ray hits: 0 = the strongest lights (no noise), 1 = weighted reservoirs. |
Rendering.GI.RadianceCascades.Jitter | true | 16-frame stratified probe and direction pattern. |
Rendering.GI.RadianceCascades.ProbeJitter | 0.75 | Share of its screen cell a jittered probe moves through. Lower keeps probes off silhouettes. |
Rendering.GI.RadianceCascades.HistoryWeight | 0.97 | History weight of the diffuse stabilizer for this technique. |
Rendering.GI.RadianceCascades.DebugView | 0 | 1 = probe coverage (green on the surface, yellow blended fallback, red none). 2 = in red, where the next cascade could not continue a direction. |
Rendering.GI.RadianceCascades.DebugCascade | 0 | Gathers a higher cascade instead of cascade 0. |
Rendering.GI.RadianceCascades.Merge | true | Diagnostic. Off shows only what each band sees on its own. |
Settings shared with screen-probe RTGI also apply: light at ray hits (lights with shadow rays, emissive surfaces, the sky), Rendering.GI.RTGI.ScreenFeedbackScale, Rendering.GI.RTGI.Resolution and the stabilizer settings.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| No indirect light at all | No ray tracing backend. Enable Rendering.RT.Enable on a supporting GPU, or set Rendering.GI.TraceBackend to 2 and reload the scene. Check the Renderer/GI/RadianceCascades/Fallback stat. |
| GI brightens towards the screen edges | Off-screen hits receive unoccluded sky. Turn on Rendering.GI.RadianceCascades.RadianceCache, then Rendering.GI.RTGI.HitSkyVisibility. |
| Light leaks around silhouettes and steps | Lower MergePlaneTolerance or ProbeJitter. DebugView 2 shows where the next cascade could not continue. |
| Blotchy or stepped bounce light | Jitter is off, or the probe spacing is too coarse for the view. Lower ProbeSpacing (at four times the cost per halving). |
| An XR view looks different from the desktop view | Stereo views use screen-probe RTGI. |