Redshift Environment Fog and Volumetric Light in Cinema 4D: Scattering, Height Fog and Noise
The Redshift Environment object adds fog and light beams to the whole scene. Check these before a fog render:
- Create: add a Redshift Environment from the Create menu; it applies to the whole scene
- Scattering: sets how bright the beams are; lower it if the frame washes out white
- Viewing Distance: sets how thick the fog is; infinite lights such as the sun are not dimmed by it
- Height: 0 fills the scene; a value makes ground fog
- Lights: each light needs a Volume contribution above 0 to make beams
Light beams through a dusty warehouse, haze in a product shot or low morning fog over a landscape all come from the same idea: the air is not empty. Redshift renders that participating medium for the whole scene with the Redshift Environment object, without modeling a volume or loading a VDB.
This guide explains what each fog setting controls, how to set up scene-wide fog step by step, how anisotropy decides where the glow shows, how height fog works, and how to keep fog renders clean and affordable. For fog and smoke stored in VDB files, see our guide to Redshift volumes and OpenVDB in Cinema 4D.
Checked against the Maxon documentation for the Redshift Environment (Volume Scattering), Volumetric Scattering and Fog, and Common Redshift Light Parameters (Cinema 4D 2026), November 2026.
1. What does the Redshift Environment do?
The Redshift Environment object fills the scene with a global medium that scatters light. You create it from the Create menu and switch it on with the green check next to it in the Object Manager (Maxon: Volumetric Scattering and Fog). Lights that pass through it become visible as beams, and objects in their path cast dark shafts.
The figure maps the main settings to what you see. Maxon describes them this way (Maxon: Redshift Environment, Volume Scattering):
- Scattering (1/m): the strength of the volumetric lighting. Higher values are brighter; if the frame turns washed-out white, reduce it a lot.
- Viewing Distance (m): how thick the fog is and how much light dims as it passes through. It is especially useful with Emission to make ground fog visible.
- Anisotropy: from -1 to 1, the direction light prefers to scatter (section 3).
- Emission: makes the fog glow by itself, so it can have color instead of staying black; black by default.
- Tint: a global tint for volumetric lighting, which does not include the global fog.
One rule surprises people: Viewing Distance only dims non-infinite lights. Dome lights, the physical sun and infinite lights are not attenuated, because their infinite distance would otherwise be blocked completely.
2. How to set up scene-wide fog in Redshift (step by step)
Settings checklist (copy or follow line by line):
Step 1: Add the Redshift Environment
Create a Redshift Environment from the Create menu and make sure its green check is on.
Step 2: Start with very low Scattering
Raise Scattering slowly while you watch a light beam in the RenderView. If the whole frame goes white, the value is far too high.
Step 3: Set the thickness
Use Viewing Distance to make the fog thicker and to dim lights that travel through it. Add a dark Emission color if the fog should glow faintly on its own.
Step 4: Turn on volume light per light
Each Redshift light has a Volume Contribution Scale; it scales the light’s effect on volume materials and environment fog, and 0 disables it (Maxon: Common Redshift Light Parameters). Keep it above 0 only on the lights that should make beams.
Step 5: Check noise
Render the frame with the strongest beams at final samples. If the beams are grainy, raise the light’s Volume Samples, which Maxon notes reduces noise at a cost in performance (Maxon: Light Parameters, Volume Samples).
3. Anisotropy: why the glow shows from one side
Anisotropy controls the direction in which the medium scatters light. At 0 the scattering is even. Positive values scatter forward, so the glow is strongest when the camera looks toward the light; negative values scatter backward, so it is strongest when the light travels away from the camera. Seen from the side, the effect is weaker either way (Maxon: Redshift Environment).
That is why a shot can look right in one camera and flat in another. If a sun-through-the-window shot loses its beams when the camera turns, check the anisotropy before you raise Scattering, which brightens the whole frame instead of the beams.
4. Ground fog and horizon lines
A Height of 0 fills the scene with fog. Any other value limits the fog to that height, which gives low ground fog. In large scenes the height fog can meet the horizon in a hard line; Horizon Blur fades the fog there to soften it (Maxon: Redshift Environment).
By default the fog follows the Redshift Environment object (Use Transform). With it off, Ground Point and Ground Normal place the fog plane; setting the normal along X or Z turns the height fog sideways, which Maxon notes can create vertical fog. Ground fog stays dark without light passing through it, so Maxon suggests pairing Viewing Distance with Emission to make it read.
5. Keeping fog renders clean and affordable
Fog adds work to every ray that crosses the medium, so the settings that limit where it applies also limit the cost:
- GI contribution: the environment’s GI ray contribution is off by default; Maxon notes it can wash out the result, add noise (especially with strong anisotropy) and increase render cost.
- Lights: keep Volume Contribution Scale at 0 on lights that do not need beams.
- Samples: raise Volume Samples on the beam lights before raising global samples; see our Redshift sampling guide for the order.
- Compositing:
Replace Alphasets the environment alpha to 1 so the fog does not disappear where alpha is partial; turn it off only if you will composite the fog separately.
When the fog looks wrong
Based on Maxon Redshift Environment and light docs
| Symptom | Likely cause | Fix |
|---|---|---|
| Whole frame washed out white | Scattering far too high | Lower Scattering a lot, then raise slowly |
| No beams from a light | Light Volume Contribution Scale at 0 | Raise it on that light |
| Sun shows no fog dimming | Infinite lights are not attenuated by Viewing Distance | Expected; use Scattering, Emission or a local light for depth |
| Beams vanish when the camera turns | Anisotropy favors one viewing direction | Lower the absolute Anisotropy value |
| Grainy beams | Too few volume samples on the light | Raise that light’s Volume Samples |
| Hard line where ground fog meets the sky | Height fog in a large scene | Raise Horizon Blur |
| Fog missing in partly transparent areas of the alpha | Replace Alpha off | Turn Replace Alpha on unless the fog is composited separately |
Test on the frame where the beams are brightest and the camera looks into the light; that is where fog noise shows first.
6. SaaS or IaaS render farm for fog-heavy shots?
Which farm type fits a fog shot
Both farm types render Redshift environment fog; the difference is how you tune density and noise.
| Situation | Usually a better fit | Why |
|---|---|---|
| Fog settings final, frames only | SaaS | Upload and collect frames without managing a machine |
| Scattering, anisotropy and samples still being tuned | IaaS | You adjust and re-render the hero frame on the render machine itself |
| Heavy beams that need many volume samples | Either | Both benefit from more GPUs; check cost per frame on a test frame |
| Studio pipeline with its own submit tools | Either | Pick the farm that supports your submit workflow |
Rule of thumb: fog is easy to over- or under-tune, so settle density and samples on a machine you can open, then render the final range where it suits you.
Rendering a fog shot on an iRender server
On iRender you work on the render machine by remote desktop, so fog density and noise are judged on the same GPUs that render the frames:
- Upload the project to iRender Drive before you start a server; uploading is free and does not use rental time.
- Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs. Cinema 4D and Redshift are pre-installed.
- Render the frame with the strongest beams at final samples and adjust Scattering, Anisotropy and Volume Samples.
- Render the full range from the Picture Viewer or Render Queue, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.
Redshift environment fog checklist
Tick each item before you send the full range to any machine.
Frequently asked questions
1. How do I add fog to a whole scene in Redshift?
Create a Redshift Environment object from the Create menu and enable it. Raise Scattering slowly for visible light beams and use Viewing Distance for fog thickness.
2. Why is my render completely white after adding fog?
Scattering is too high. Maxon advises reducing it significantly if the frame becomes washed out; start with a very small value and raise it gradually.
3. Why does the sun not get dimmer through the fog?
Viewing Distance only attenuates non-infinite lights. Dome lights, the physical sun and infinite lights are not attenuated, because their infinite distance would otherwise be fully blocked.
4. Why do my light beams disappear when the camera moves?
Anisotropy makes the medium scatter mostly forward or backward, so the glow depends on the viewing angle. Lower the absolute Anisotropy value for a more even look from all sides.
5. How do I make low ground fog?
Set Height above 0 so the fog stops at that height, add Viewing Distance with a little Emission so it reads, and use Horizon Blur if a hard line appears at the horizon.
6. Why are my volumetric beams noisy?
Each light has its own Volume Samples. Raise them on the lights that make the beams; Maxon notes more samples reduce noise at a cost in performance.
7. Should fog affect GI?
The GI ray contribution of the Redshift Environment is off by default. Maxon notes enabling it can wash out results, add noise and increase render cost, so turn it on only when the shot needs it.
8. Can I render fog shots on a multi-GPU iRender server?
Yes. Cinema 4D and Redshift are pre-installed on iRender servers with 1, 2, 4 or 8 RTX 5090 or RTX 4090 GPUs, and you can tune fog density and samples on the same machine before rendering the range.
Render your Cinema 4D and Redshift projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. Your server image is saved between sessions, so your plugins and settings stay installed. Cinema 4D and Redshift are pre-installed on every server.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start a server and render Cinema 4D and Redshift on it:
Two Redshift runs we recorded on our servers: 150 frames at 1080p on 4x RTX 5090 at 40.84 seconds per frame (about 1h 42m), and a 301-frame cloth simulation at 1080p on 1x RTX 5090 at 21.3 seconds per frame:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Cinema 4D and Redshift render farm page or download the iRender GPU app.
Sources: Maxon: Redshift Environment, Volume Scattering · Maxon: Volumetric Scattering and Fog · Maxon: Common Redshift Light Parameters · Maxon: Light Parameters, Volume Samples. Checked November 2026.




