Compositor Glare

examples/compositor-glare/

Bloom where it actually lives — a compositor Glare (Fog Glow) node fed by Render Layers, wired via scene.compositing_node_group on 5.x and scene.node_tree on 4.x, with the Glare node's legacy properties vs 5.x menu sockets.

Rendered headless by the example itself. Select it to enlarge.

witnesses scene.node_tree is gone in 5.x and EEVEE has no use_bloom on either side: the halo beyond the ring silhouette falls off strictly with the compositor on and is exactly zero with it off.

tags compositor rendering

runs on 4.5 LTS · 5.1 · 5.2 LTS

blender --background --python examples/compositor-glare/compositor_glare.py --

falsify it Breaks the contract on purpose and must exit 4

blender --background --python examples/compositor-glare/compositor_glare.py -- --threshold-high

A runnable example that puts bloom where it actually lives: the compositor. Three emissive rings are rendered, then a Glare (Fog Glow) node fed by Render Layers grows the halo — wired through scene.compositing_node_group on Blender 5.x and through scene.node_tree on 4.x, because the 5.0 compositor rewrite removed the scene-level tree entirely (scene.node_tree now raises AttributeError; scene.use_nodes survives only as a deprecated flag, removal in 6.0).

The Glare node changed shape with it: on 4.x it takes legacy enum properties (glare_type='FOG_GLOW', quality='HIGH', size=6), while on 5.x the same choices are menu/float input sockets (inputs['Type'].default_value = 'Fog Glow'). The 4.x threshold property is a dead shim — the real threshold is the Threshold input socket on both versions. And EEVEE has no use_bloom toggle on either version (removed in 4.2): bloom is a compositor node, period.

What it witnesses: the halo is the compositor's output, proven with pixels. The check renders the scene twice at 96×54 (single-sample Cycles, noise-free) — once with use_compositing on, once off — and samples a column of pixels above the middle ring's silhouette via world_to_camera_view. With the compositor on, the halo luminance just outside the silhouette is far above zero and falls off strictly with distance (the Fog Glow kernel signature); with it off, those same pixels are exactly zero. The structural check pins the wiring (Render Layers → Glare → output), the version-correct tree plumbing, and the absence of any EEVEE bloom toggle.

Run#

# Cheap correctness check (two tiny renders) — the CI check:
blender --background --python compositor_glare.py --

# Falsifier: Threshold=1000.0, above the brightest ring (18). Must exit non-zero (no halo pixels, exit 4).
blender --background --python compositor_glare.py -- --threshold-high

# Also render a still (EEVEE on a GPU host; use --engine cycles on GPU-less hosts):
blender --background --python compositor_glare.py -- --output rings.png
blender --background --python compositor_glare.py -- --output rings.png --engine cycles

Exit codes#

Per-script sequential checks. 9 is a valid check code; there is no rule against it.

CodeMeaning
0Success
1Uncaught exception (FATAL wrapper)
2argparse / usage
3Compositor tree / Glare / link-chain contract
4Check render missing, tube dark, no halo, or halo does not fall off (--threshold-high lands here)
5Halo present with compositing off
6--output produced no file
10Gallery framing violation (render path; checked before the beauty render)

The blender-smoke workflow runs the check on Blender 5.2 LTS and 4.5 LTS (5.1 on the weekly cron, the needs-5.1 PR label, or manual dispatch). Smoke does not pass --output. Its catalog falsifier is --threshold-high (expects exit 4).

Source

examples/compositor-glare/compositor_glare.py View the script on GitHub →
Three glowing neon rings, violet, cyan and warm white, with fog-glow bloom and reflections on the floor.