Redshift GI Engines in Cinema 4D: Brute Force, Irradiance Cache and Point Cloud for Animation
Redshift splits global illumination into a primary and a secondary engine. Check these before an animation:
- Recommended: Maxon recommends Brute Force primary, Irradiance Point Cloud secondary and 2 or 3 bounces
- Brute Force: slowest, but very accurate and does not flicker; too few rays show as grain
- Irradiance Cache: often several times faster, but too few rays show as splotches and flicker
- Point Cloud: secondary only; helps with many bounces, many lights or hard lighting
- Flicker fix: Irradiance Cache prepass, then Load with Number of frames to blend
Global illumination is the light that bounces off walls, floors and objects onto everything else. It is what makes an interior look lit rather than spot-lit, and in Redshift it is also one of the settings most likely to cause trouble in animation: the wrong engine choice shows up as splotches that crawl from frame to frame.
This guide explains how Redshift’s primary and secondary GI engines work, what each engine is good and bad at, the settings Maxon recommends, how to get flicker-free results if you use the Irradiance Cache, and what that means when a sequence is split across several machines.
Checked against the Maxon documentation for Redshift GI Engines, the Irradiance Cache GI engine and the Irradiance Point Cloud GI engine, November 2026.
1. How do primary and secondary GI engines work?
When a camera ray hits a surface, Redshift uses the primary GI engine to gather the bounced light there. Any further bounces use the secondary engine. Maxon’s reasoning is simple: the primary result is directly visible, so it needs high quality; the secondary result is usually a smaller part of the lighting, so it can be cheaper (Maxon: GI Engines).
In the figure, the light reaching point A from the floor at B is primary GI; the light that reached B from the ceiling at C is secondary. Redshift handles caustics separately from diffuse GI, and caustics need photon mapping (see our Redshift caustics guide). More bounces make the image brighter but slower and can wash it out; in Maxon’s example the biggest visible change was from zero to one bounce.
2. Which GI engine should you use?
The table summarizes Maxon’s pros and cons for the four techniques.
Redshift GI engines at a glance
Strengths and limits as Maxon lists them
| Engine | Strengths | Limits |
|---|---|---|
| Brute Force | Very accurate; one main setting (Num Rays); no flicker in animation; no storage | Slowest; grainy with too few rays |
| Irradiance Cache (primary only) | Often several times faster; smooth; results can be saved per frame | Too few rays give splotches and flicker; separate pass, so no interactive feedback; heavy in very detailed scenes |
| Irradiance Point Cloud (secondary only) | Speeds up and cleans Brute Force and Irradiance Cache; small storage | Helps mainly with multiple bounces, many lights or difficult lighting |
| Photon Mapping | Fast for reasonable photon counts; needed for caustics | Photons stored in GPU memory; needs tuning; described by Maxon as outdated for diffuse GI |
Maxon’s recommended starting point is Brute Force for the primary engine, Irradiance Point Cloud for the secondary engine and 2 or 3 bounces (Maxon: GI Engines). For animation this is the safe choice: noise from too few Brute Force rays looks like grain, while too few Irradiance Cache rays show up as splotches and flicker, which Maxon calls more distracting than grain (Maxon: Irradiance Cache).
3. How to set up GI for an animation (step by step)
Settings checklist (copy or follow line by line):
Step 1: Set the engines
In the Redshift render settings, open the GI tab, enable GI, set the primary engine to Brute Force and the secondary to Irradiance Point Cloud.
Step 2: Set the bounces
Start with 2 or 3 bounces, as Maxon recommends. Raise them only if an interior still looks too dark in the corners.
Step 3: Clean the grain
Render a test frame and raise Brute Force Num Rays until the GI grain is gone, and check how your Redshift version’s sampling mode handles per-effect samples in our Redshift sampling guide.
Step 4: Test a range, not a frame
Render 12 to 24 consecutive frames at final settings and play them back at speed. GI problems in animation only show between frames.
4. Irradiance Cache without flicker: prepass and Load
If a scene is too slow with Brute Force, the Irradiance Cache can still work for animation with Maxon’s two-pass method (Maxon: Irradiance Cache):
- Set
ModetoRebuild (prepass only)and choose a filename. If an Irradiance Point Cloud is used, set it to Rebuild. - Render the animation. A cache file is written for each frame and the final pass is skipped.
- Set
ModetoLoadand setNumber of frames to blend. - Render the animation again. Each frame blends its neighbors’ cache files, which reduces or removes flicker.
A blend value of 2 uses the two previous and two next frames plus the current one. Maxon suggests 2 to 4 with well-tuned settings, and warns that too many frames can cause ghosting on fast-moving content. Flythrough Mode, which builds each frame’s points from the previous frame, suits only shots where the camera alone moves; moving objects or lights cause artifacts.
This has a practical consequence on any farm: the Load pass reads the cache files of neighboring frames, so the prepass must have written them first. If you split a sequence across several machines or GPU groups, run the prepass for the whole range, keep the cache files in one shared folder, then start the Load pass.
5. Irradiance Cache splotches and memory errors
When Irradiance Cache results look wrong
Fixes from Maxon Irradiance Cache documentation
| Symptom | What to change |
|---|---|
| Splotches or flicker around thin details | Min Radius to 0, then raise Max Rate (-1 to 0, or 0 to 1) |
| Splotches that crawl in animation | Raise Num Rays if under 1000; if already 2000–3000, lower Adaptive Error Threshold, then Adaptive Amount |
| Too blurry compared with Brute Force | Disable smoothing passes; reduce Radius Factor if above 2.0; lower Color Threshold carefully |
| Frame aborts: points do not fit in VRAM | Raise Irradiance cache working tree reserved memory (Memory tab, default 64 MB); raise Min Detail; lower Max Rate |
| Dense foliage or very detailed objects | Use the per-object force-brute-force option for those objects |
Maxon also suggests, when Irradiance Cache flickers, rendering a few frames with reflections and refractions disabled globally to see whether they are the source (Maxon: Irradiance Cache). For a full list of what to check before any Redshift render, see our Cinema 4D and Redshift pre-flight checklist.
6. SaaS or IaaS render farm for GI-heavy animation?
Which farm type fits a GI-heavy animation
Both farm types render Redshift GI; the difference shows with two-pass caches and long tests.
| Situation | Usually a better fit | Why |
|---|---|---|
| Brute Force GI, settings final | SaaS | Each frame renders on its own, so a submit-and-collect farm splits it easily |
| Irradiance Cache prepass + Load | IaaS | You run both passes on one machine or a shared folder and control the cache files |
| GI rays and bounces still being tuned | IaaS | You test ranges on the render machine and change settings between runs |
| Studio pipeline with its own submit tools | Either | Pick the farm that supports your submit workflow |
Rule of thumb: Brute Force animation splits cleanly on any farm; two-pass Irradiance Cache work is easier where you control the machine and its folders.
Rendering a GI animation on an iRender server
On iRender you work on the render machine by remote desktop, so GI tests and both cache passes run on the same machine:
- 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 12 to 24 consecutive frames at final GI settings and play them back; if you use the Irradiance Cache, run the prepass for the full range first.
- Render the full range (or the Load pass) 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 GI animation checklist
Tick each item before you send the full range to any machine.
Frequently asked questions
1. Which GI engine does Maxon recommend for Redshift?
Brute Force for the primary engine, Irradiance Point Cloud for the secondary engine, and 2 or 3 GI bounces. Caustics are handled separately with photon mapping.
2. Why does my Redshift animation flicker with Irradiance Cache?
Too few rays in the Irradiance Cache show up as splotches that change between frames. Raise Num Rays, or use Brute Force, which Maxon lists as flicker-free.
3. Is Brute Force too slow for production?
It is the slowest engine, but Maxon describes it as practical given Redshift’s speed, and it needs no storage and does not flicker. Pairing it with the Irradiance Point Cloud secondary engine makes it faster and cleaner.
4. How do I remove Irradiance Cache flicker without switching engines?
Render the range once with Mode set to Rebuild (prepass only), then render again with Mode set to Load and Number of frames to blend at 2 to 4. Each frame then averages its neighbors’ caches.
5. Can I split an Irradiance Cache animation across several machines?
Yes, but the Load pass reads neighboring frames’ cache files. Run the prepass for the whole range first, keep the files in one shared folder, then start the Load pass.
6. How many GI bounces should I use?
Maxon recommends 2 or 3. More bounces make the image brighter but slower and can wash it out; the biggest visible change is usually from zero to one bounce.
7. Why does my frame abort with an Irradiance Cache memory error?
The cache points do not fit in GPU memory. Maxon suggests raising the Irradiance cache working tree reserved memory in the Memory tab (default 64 MB), or raising Min Detail and lowering Max Rate.
8. Can I render GI-heavy Redshift animation 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 run range tests and both Irradiance Cache passes on the same machine.
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: GI Engines · Maxon: The Irradiance Cache GI Engine · Maxon: Irradiance Cache (Redshift docs) · Maxon: The Irradiance Point Cloud GI Engine · Maxon: Irradiance Cache flicker notes. Checked November 2026.




