Octane Kernels and Sampling in Cinema 4D: Path Tracing, Photon Tracing and Fireflies
OTOY’s kernel guide follows one order: kernel, depths and clamp, then sampling. The short version:
- Path Tracing: the default for realistic renders without important caustics
- Photon Tracing: when caustics matter; test it on multi-GPU and network renders
- Max Samples: start at 64–256 and let adaptive sampling and the denoiser do the rest
- GI clamp: lower it only after fixing lights; it removes energy as well as fireflies
- Animation: keep Coherent Ratio at 0 and avoid PMC for sequences
Most slow or noisy Octane renders in Cinema 4D come from kernel settings, not from the GPU. A scene can render for twenty minutes at 16,000 max samples when 256 samples, adaptive sampling and a denoiser would give the same picture in a fraction of the time. On a render farm the cost of a bad setting multiplies by every frame.
This guide follows the order OTOY recommends in its kernel guide: choose the kernel, set depths and GI clamp, then tune sampling. Every value below is from OTOY’s documentation; treat them as starting points to test on your own frames.
Checked against the OctaneRender for Cinema 4D manual (Kernels, Path Tracing, Photon Tracing) and OTOY’s Help Center kernel guide, November 2026.
1. Which Octane kernel should you use?
Octane has four main render kernels: Direct Light, Path Tracing, PMC and Photon Tracing. OTOY’s guide places them by what the shot needs. Direct Light is the fast option for simple scenes without caustics or heavy scattering. Path Tracing is the general choice for realistic images when caustics are not a key feature. Photon Tracing is built for caustics: OTOY’s C4D manual says it renders caustics much faster and with less noise than PMC, using GPU photon mapping and path guiding. PMC handles very complex lighting and refraction but is much slower and less predictable from frame to frame.
Two notes matter for farm rendering. OTOY’s guide warns that Photon Tracing adds overhead and can cause problems in multi-GPU or network rendering, so test it on the actual multi-GPU machine before committing a sequence. And because PMC can change from frame to frame, OTOY calls it a poor fit for animation; use it for stills.
For caustics with Photon Tracing, OTOY notes that you also enable caustics in the IOR channel of the reflective and refractive materials that should create them. Our guide on Spectron lights and photon tracing caustics covers that setup.
2. Depths, GI clamp and the settings that cost the most time
Depth values set how many times a ray may bounce. OTOY’s guide notes that the Path Tracing defaults of 16 diffuse and 16 specular bounces are a good start, while Direct Light’s default glossy depth of 2 is usually too low. Lower depths step by step until the image starts to change, then go back one step.
Octane kernel settings that change render time the most
Starting points from OTOY’s kernel guide; tune per scene.
| Setting | Starting value | What it trades |
|---|---|---|
| Max Samples | 64–256 for Path or Photon Tracing; 16–64 for Direct Light | Noise against render time; keep low and let the denoiser finish |
| Diffuse / Specular depth | 16 for Path Tracing (default); 5–8 glossy for Direct Light | Bounces of light; lower until the look changes |
| GI clamp | 1,000,000 (default) to start | Fireflies against light energy |
| Parallel Samples | 32; 16 on older cards or heavy scenes | Speed against VRAM use |
| Coherent Ratio | 0 for animation | Speed against blotchy, flickering dark areas |
| Adaptive Sampling | on; noise threshold 0.03 default, 0.02 cleaner | Time spent on clean pixels |
Parallel Samples affects both speed and memory. OTOY suggests starting at 32 and dropping to 16 on older cards or memory-heavy scenes, and checking VRAM in the Live Viewer readout. On a 32 GB card there is usually room for the higher value; on a scene close to the VRAM limit, the lower value can be the difference between rendering in-core and running out of memory.
GI clamp and fireflies
Fireflies are single bright pixels from rare light paths that carry a lot of energy, often through glass or small bright lights. GI clamp caps the contribution of each path. OTOY’s Path Tracing page explains the trade: reducing the clamp removes fireflies by removing energy, so the image can get darker and lose some indirect light.
OTOY’s guide therefore keeps the clamp high (1,000,000) at the start and lowers it only after lights and caustics are fixed in other ways. Simple scenes can use values of 100 or 10. If caustics cause the fireflies and you need them, Photon Tracing is the better fix than a low clamp.
3. Adaptive sampling: stop spending samples on clean pixels
With adaptive sampling on, Octane stops sampling pixels that are already clean and keeps working on noisy ones. OTOY’s guide recommends keeping it on. The noise threshold sets what counts as clean: 0.02 is clean, 0.03 is the default and a little faster, and 0.04 or higher is faster but noisier. Minimum samples defaults to 256, so every pixel gets at least that many before adaptive sampling decides.
Expected exposure tells adaptive sampling how bright the final image will be, so it judges noise in dark areas correctly. OTOY’s guide says it starts at 0 and should match your Imager exposure if you changed it. Pixel grouping defaults to 2×2.
Adaptive sampling changes where time goes, not the maximum. Areas such as glass and caustics can still run to Max Samples, so keep Max Samples reasonable rather than at 16,000.
4. Settings for animation and multi-GPU renders
A still image can tolerate settings that break an animation. OTOY’s guide lists three to watch for sequences:
- Coherent Ratio: speeds up rendering but causes blotchy or noisy dark areas; keep it at 0 for animations.
- Denoiser: keep it off during look development and turn it on near the end, then lower Max Samples step by step. Test a few frames or a render region before the full sequence; see our guide to denoising Octane animations without boiling.
- PMC: avoid it for sequences because results vary from frame to frame.
Kernel settings are identical on one GPU or eight: more GPUs render the same samples faster. That means you can tune samples on your workstation and expect the same picture on a multi-GPU machine, with Photon Tracing as the one kernel worth a separate test, as noted above.
5. Compare two settings on the same frames, in the background
Tuning by eye in the Live Viewer works for one frame. For a sequence, the fair test is the same short range rendered twice, once with each version of the settings, then compared side by side for noise, flicker and time. Save the scene twice (for example shot_A.c4d with your current samples and shot_B.c4d with the change), turn on Stamp Info so every frame records its samples and render time, and let the Commandline renderer do the rest while you keep working:
- Maxon’s
-frametakes a start, an end and a step:140 144 1renders five consecutive frames, enough to see boiling between frames; g_logfilewrites each run’s console output to its own text file;- OTOY’s example adds
g_modulePathso the Octane plugin loads in a background render.
Give the two scenes different output paths so the runs do not overwrite each other, then flip between the two sets of frames. Keep the change that removes the noise you can see at the lowest time on the stamp. OTOY notes that background rendering needs a valid command line license.
Sources: Maxon: Cinema 4D and the Command Line, OTOY: Command Line Rendering.
6. SaaS or IaaS render farm for tuning Octane samples?
Which farm type fits an Octane sampling workflow
Both render the same kernel; the difference is whether you can adjust it on the machine.
| Situation | Usually a better fit | Why |
|---|---|---|
| Samples and denoiser already tested on frames | SaaS (managed farm) | Submit and render |
| Still tuning Max Samples or GI clamp | IaaS (remote workstation) | Change settings in the Live Viewer and re-render a frame |
| Photon Tracing on several GPUs | IaaS | Test the kernel on the same multi-GPU machine first |
| Very long sequence at final quality | Either, after a test batch | Measure time per frame before the full run |
| Short one-off still | SaaS | No setup time |
Rule of thumb: tune kernel and samples where you can see the Live Viewer. Once the settings are fixed and tested on a few frames, any farm type will render them the same way.
Tuning Octane samples on an iRender server
On iRender you rent a whole Windows workstation with Cinema 4D and OctaneRender installed and sign in with your own OTOY account, so you tune in the Live Viewer exactly as at home:
- Upload the project through iRender Drive and start a 2x, 4x or 8x RTX 5090 server.
- Open the Live Viewer and render the hardest frame with your kernel, depths and clamp.
- Turn on adaptive sampling and the denoiser, then lower Max Samples until noise appears and go back one step.
- Render three to five frames in a row and check for flicker before the full range.
- Write down the time per frame and multiply by the frame count to estimate the job.
Octane kernel checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Which Octane kernel is fastest?
Direct Light is the fastest, but it is meant for simple scenes without caustics or heavy scattering. Path Tracing is the usual choice for realistic renders, and Photon Tracing is faster than PMC for caustics.
2. What is the difference between Path Tracing and Photon Tracing in Octane?
Path Tracing is the general kernel for realistic lighting. Photon Tracing adds GPU photon mapping and path guiding so caustics render faster and with less noise. OTOY notes it adds overhead and can cause problems in multi-GPU or network rendering.
3. How do I get rid of fireflies in Octane?
Fix the cause first: very small bright lights, glass and caustics. Then lower GI clamp step by step. A lower clamp removes energy as well as fireflies, so the image can get darker.
4. What noise threshold should I use for adaptive sampling?
OTOY’s guide gives 0.02 as clean, 0.03 as the default and slightly faster, and 0.04 or higher as faster but noisier. Minimum samples defaults to 256.
5. How many max samples does Octane need?
OTOY’s guide starts Path Tracing and Photon Tracing at 64–256 samples and Direct Light at 16–64. With adaptive sampling and the denoiser, most scenes do not need the 16,000 default.
6. Is PMC good for animation?
OTOY calls it a poor fit: it is much slower and less predictable from frame to frame. Use it for stills with complex refraction and use Path or Photon Tracing for sequences.
7. Do Octane kernel settings change on a multi-GPU machine?
No. The same settings give the same image; more GPUs render the samples faster. Test Photon Tracing on the target machine because OTOY warns it can cause problems in multi-GPU or network renders.
Render your Cinema 4D + Octane scenes on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 or RTX 5090 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. Cinema 4D and OctaneRender are installed; sign in with your own OTOY account (OTOY’s Studio+ plan has no GPU limit for multi-GPU servers). Your server image is saved between sessions.
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, so they keep their boost clocks. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start Cinema 4D and Octane on an iRender server:
On a 4x RTX 5090 server, a 300-frame Cinema 4D + Octane animation rendered in 1 hour 18 minutes. The second clip runs the same kind of scene on 4x RTX 5090 and 4x RTX 4090:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Octane render farm page, download the iRender GPU app, or read the Octane AI Denoiser for animation.
Sources: OTOY Help Center: kernel guide, OTOY: Kernels tab (C4D), OTOY: Path Tracing (C4D), OTOY: Photon Tracing (C4D), OTOY: Path Tracing kernel, GI clamp, OTOY: adaptive sampling parameters. Checked November 2026.




