Deep EXR with Octane in Cinema 4D: Deep Image Settings, Depth Samples and VRAM
Octane can write deep EXR files from Cinema 4D, but it needs two switches and enough samples. The points that decide whether a deep sequence works:
- Two switches: Deep Image in the kernel settings, plus Save Deep Image with a file path in the Octane render settings
- Enough samples: on the OTOY forum, a deep image could not be saved when Max Samples was too low
- Up to 32 per pixel: Max. Depth Samples caps the deep samples stored per pixel; Depth Tolerance merges close ones
- VRAM: OTOY warns deep rendering uses a lot of VRAM; the fix is fewer depth samples or a lower resolution
- Volumes: with too few bins, deep volumes are cut off at the back
Deep compositing solves edge problems that flat AOVs cannot: overlapping objects, depth of field, motion blur and live footage placed inside rendered smoke. Octane supports it, but the setup in Cinema 4D has a few traps, and deep frames are much heavier than flat ones.
This guide explains what Octane stores in a deep pixel, which settings turn deep output on in Cinema 4D, how Max. Depth Samples and Depth Tolerance shape the file, and how to plan for the VRAM and disk space a deep sequence needs.
Checked against the OTOY OctaneRender for Cinema 4D and Standalone manuals and the OTOY forum, November 2026.
1. What does an Octane deep image store?
A flat image keeps one RGBA value per pixel. A deep image keeps several, each with its own depth. OTOY describes two kinds of deep sample: point samples, which have only a front depth, for hard surfaces, and volume samples, which have a front and a back depth (Z and ZBack), for visible volumes (OTOY: Deep Image Rendering). From these, a compositing app can combine footage at any depth instead of only stacking image A over image B.
The cost is size: every extra sample per pixel is stored, so transparency, volumes, depth of field and motion blur all make deep files larger.
2. How do you turn on deep output in Cinema 4D?
Octane needs two things in Cinema 4D: the Deep Image option in the kernel settings, and Save Deep Image with a Deep Image File path in Render Settings › Octane Renderer › Main › Deep Image (OTOY: Octane Render Settings).
On the OTOY forum, a Cinema 4D 2025 user enabled Save Deep Image with a path and got no file. The fix was the separate Deep Image checkbox; an OTOY forum expert explained that it keeps Octane from processing deep data when it is not needed. The same thread found a second trap: if Max Samples is too low, the deep image cannot be saved (OTOY forum: Deep Image).
Deep image settings and what they control
From the OTOY Cinema 4D and Standalone manuals.
| Setting | Where | What it does |
|---|---|---|
| Deep Image | Kernel settings | Turns deep rendering on; Octane does not process deep data otherwise |
| Max. Depth Samples | Kernel settings | Upper limit of deep samples stored per pixel (32 at most) |
| Depth Tolerance | Kernel settings | Merges samples whose relative depth difference is within the tolerance |
| Deep Render AOVs | Kernel settings | Writes render AOVs into the deep channels; by default only beauty |
| Save Deep Image + Deep Image File | Render Settings › Octane Renderer › Main › Deep Image | Writes the deep EXR and sets its path |
By default only the beauty pass goes into the deep channels. Enable Deep Render AOVs to include your render AOVs, and expect more VRAM use, which OTOY warns about for large images (OTOY: Deep AOVs). OTOY’s manuals for other hosts list the Path Tracing and Direct Lighting kernels for deep rendering, and newer pages add Photon Tracing (OTOY: Deep Image Rendering, 3ds Max); check the option on the kernel you render with.
3. Max. Depth Samples, Depth Tolerance and why saving can fail
A GPU renders thousands of samples per pixel, far too many to store. OTOY’s Standalone manual explains how Octane chooses what to keep (OTOY: Enabling Deep Image Rendering):
- When rendering starts, Octane collects seed samples, a multiple of Max. Depth Samples.
- From them it builds a bin distribution for each pixel: up to 32 bins that do not overlap in depth. Every later sample is accumulated into a bin, so no sample is thrown away.
- Until that distribution exists, the result cannot be saved, and the deep option in the save menu stays disabled.
This fits the forum finding above: a render with very few samples may stop before the bins are ready. Depth Tolerance then merges samples whose relative depth difference is within the tolerance, which keeps files smaller at the cost of depth detail.
4. VRAM and volumes: the two limits to plan for
VRAM. After the bin distribution is built it is uploaded to the GPUs for the whole frame. OTOY warns that deep rendering uses a lot of VRAM even with tiled rendering, that devices may fail when the render starts, and that the log shows whether the buffers are too large. The only fixes it gives are a lower Max. Depth Samples or a lower resolution (OTOY).
Volumes. Bins are an approximation. If there are not enough of them, a deep volume with a large depth range is cut off at the back, which shows when you view the deep pixels as a point cloud in Nuke; the volume is still usable up to the cut. If surfaces disappear in some pixels, OTOY recommends rendering again with a higher Max. Depth Samples. Particle volumes built with the OpenVDB mesher are covered in X-Particles with Octane in Cinema 4D.
The two limits pull in opposite directions: more depth samples help volumes but cost VRAM. Test the heaviest frame at final resolution before you choose. For how VRAM behaves across several GPUs, see Octane multi-GPU rendering in Cinema 4D.
5. Check a deep frame before the full sequence
Render one representative frame, then confirm from the command line that the file really is deep and note its size. The OpenEXR tool exrinfo prints the header of an EXR file, including its type and channels (OpenEXR: exrinfo).
Then open the frame in your compositing app and check a pixel where volumes or transparent objects overlap. For more on the compositing side, see our guide to Octane AOV compositing in Cinema 4D.
Rendering deep EXR sequences on a render farm: SaaS or IaaS?
Choosing a farm type for deep sequences
Deep settings are saved in the scene; the difference is where you tune them and where the large files are written.
| Situation | Usually a better fit | Why |
|---|---|---|
| Deep settings tested; you need frames | Either type | The scene carries the deep settings |
| Still choosing depth samples or tolerance | IaaS (remote machine you control) | You can render test frames and read the log on the render machine |
| Large deep files to collect | Either, plan the transfer | Deep frames are much larger than flat ones |
| VRAM errors at render start | IaaS with larger cards | Each GPU must hold the deep buffers for the frame |
Rule of thumb: if your deep frames already render and save at home, either type works. If you still need to balance depth samples against VRAM, a machine you can open and test on saves failed submissions.
A test workflow 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:
- Upload the project through iRender Drive.
- Start a server with RTX 5090 cards (32 GB each) if your deep frames are heavy.
- Render the heaviest frame at final resolution with Deep Image and Save Deep Image both on.
- Check the log for buffer errors, then check the file with exrinfo and in your compositing app.
- Render the full range to the local 2 TB NVMe SSD, then move the frames through iRender Drive.
Octane deep EXR checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Why does Octane not write a deep EXR in Cinema 4D?
Check both switches: the Deep Image option in the kernel settings and Save Deep Image with a path in the Octane render settings. On the OTOY forum, a too-low Max Samples also stopped the deep image from saving.
2. How many deep samples can Octane store per pixel?
Up to 32. Max. Depth Samples sets the limit, and other samples are accumulated into the bins rather than thrown away.
3. What does Depth Tolerance do?
It merges deep samples whose relative depth difference is within the tolerance, which reduces file size at the cost of depth detail.
4. Why does my deep render fail when it starts?
Deep rendering uses a lot of VRAM. OTOY says the log shows whether the buffers are too large, and the fixes are a lower Max. Depth Samples or a lower resolution.
5. Why is my deep volume cut off?
There were not enough bins for the depth range of the volume. Render again with a higher Max. Depth Samples.
6. Are AOVs included in the deep file?
Only if Deep Render AOVs is enabled. By default only the beauty pass is written to the deep channels.
7. Does a deep EXR render need more VRAM on a multi-GPU machine?
More GPUs speed up the render, but VRAM does not add up across cards: the card with the least VRAM sets the limit (OTOY Devices tab). Deep output stores extra samples per pixel, so test the heaviest deep frame on the card size you will render with, and lower Max. Depth Samples if it does not fit.
Render your Cinema 4D and Octane 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 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 Octane AOV compositing in Cinema 4D.




