Redshift Displacement in Cinema 4D: Tessellation, Maximum Displacement and Memory
Displacement adds real geometry at render time, so the tessellation settings decide both the look and the memory. The main points from Maxon's documentation:
- Settings live on the Redshift Object tag: Geometry tab, Override on: Subdivision Rule, Screen Space Adaptive, Minimum Edge Length, Maximum Subdivisions and the displacement settings.
- Memory is set by tessellation: Maxon's example: 1,000 quads with edge length 0 and 8 subdivisions can become 65 million quads. Screen Space Adaptive and a larger Minimum Edge Length keep this under control.
- Flat or cut-off displacement: Maximum Displacement must cover the full displacement, including stacked shaders and the object Displacement Scale; if it is too low, the peaks are clamped.
- Fine detail without more polygons: Auto Bump Mapping turns detail that tessellation cannot reach into bump. Heightfield and vector displacement, in object or tangent space, are both supported.
- Rendering heavy displacement: Large tessellated terrains need GPU memory; iRender servers with RTX 5090 (32 GB per GPU) or RTX 4090 (24 GB) let you check the tessellated scene in the RenderView before the batch render.
Displacement turns a texture into real geometry at render time, which is why it looks so much better than bump on close-ups, and why it can fill GPU memory in seconds. This guide explains the Redshift tessellation and displacement settings in Cinema 4D, why displacement comes out flat or too heavy, and how to keep detail without exploding the polygon count.
Checked against the Cinema 4D and Redshift documentation, November 2026.
1. How does displacement work in Redshift?
Redshift first tessellates the mesh, splitting polygons into smaller ones at render time, and then the displacement shader moves the new vertices. Both are controlled on the Redshift Object tag in its Geometry tab with Override enabled (Maxon: Tessellation and Displacement). The figure shows the two settings that cause most problems.
On the left, Screen Space Adaptive tessellation keeps splitting polygons until their edges are about the Minimum Edge Length in pixels, so the ground near the camera gets dense geometry and the far ground stays light. On the right, Maximum Displacement is lower than the height the shader asks for, so every peak is cut flat at that limit.
Tessellation and displacement settings in Redshift
Settings on the Redshift Object tag, as described in Maxon's Tessellation and Displacement documentation.
| Setting | What it does | Practical use |
|---|---|---|
| Subdivision Rule | Catmull-Clark for quads with Loop for triangles, or Catmull-Clark only. | Use CC Only when the result must match software without Loop subdivision. |
| Screen Space Adaptive | On: Minimum Edge Length is measured in pixels, so distant objects get fewer polygons. Off: measured in scene units (world space), tessellating the same everywhere. | Leave on for most shots; it saves GPU memory on distant and off-screen geometry. |
| Minimum Edge Length | Polygons keep splitting while their edges are longer than this. Smaller values mean more tessellation. | Raise it first when memory or preparation time is too high. |
| Maximum Subdivisions | Upper limit on subdivision levels. | Maxon's example: 1,000 quads with edge length 0 and 8 subdivisions can become a 65 million quad mesh. |
| Out-of-Frustum Tessellation | Factor and optional limit for geometry outside the camera view. | Limit it when off-screen terrain only needs to cast shadows and reflections. |
| Maximum Displacement | The largest distance the displacement can move vertices. Too low clamps the peaks. | Set it to the sum of all displacement that can stack, times the object scale. |
| Auto Bump Mapping | Adds the detail tessellation cannot reach as bump, as if tessellated to sub-pixel level. | Keep on so you can use fewer subdivisions without losing fine detail. |
2. How to set up displacement in Redshift (step by step)
Settings checklist (copy or follow line by line):
Object › Tags › Render Tags › Redshift Object › Geometry Override .............. On (also applies to child objects) Screen Space Adaptive . On Minimum Edge Length ... moderate start value Maximum Subdivisions .. match how close the camera gets Maximum Displacement .. largest total displacement (e.g. scale 3 → 3) Displacement Scale .... multiplies the shader scale Auto Bump Mapping ..... On Material ................ height/vector map › Displacement node › displacement output
Step 1: Add a Redshift Object tag
Right-click the object, add the Redshift Object tag from Render Tags, open the Geometry tab and enable Override. The settings also apply to child objects.
Step 2: Set tessellation
Keep Screen Space Adaptive on, start with a moderate Minimum Edge Length and a Maximum Subdivisions value that matches how close the camera gets.
Step 3: Connect the displacement
In the material, connect your height or vector map through a Displacement node to the material’s displacement output.
Step 4: Set Maximum Displacement and scale
Set Maximum Displacement to the largest distance all displacement can add up to. The object Displacement Scale multiplies the shader scale, so a value of 3 with a shader scale of 1 needs Maximum Displacement of 3.
Step 5: Enable Auto Bump Mapping and check
Keep Auto Bump Mapping on, render a close and a wide frame in the RenderView, and watch GPU memory before rendering the full sequence.
Quick check: if the silhouette is cut off flat at the top of bumps, Maximum Displacement is too low; if close-ups look faceted, raise Maximum Subdivisions or lower Minimum Edge Length and watch GPU memory.
3. Why does Redshift displacement use so much memory?
Because each subdivision level multiplies the number of polygons. Maxon’s documentation gives the example of a mesh with only 1,000 quads that becomes about 65 million quads with a Minimum Edge Length of 0 and 8 Maximum Subdivisions. Ways to keep it under control:
- Screen Space Adaptive: distant objects get fewer polygons; in world space mode every object is tessellated the same, on screen or not.
- Minimum Edge Length: a larger value stops subdivision earlier. In screen space there is an internal minimum of 0.5 pixels.
- Out-of-frustum limits: limit tessellation for geometry outside the camera view.
- Auto Bump Mapping: fine detail is kept as bump, so fewer real subdivisions are needed.
- Instancing: adaptive tessellation cannot be used on instanced objects; instances and proxies use fixed tessellation.
4. Why is my displacement flat, stretched or showing seams?
- Flat tops: Maximum Displacement is too low and the peaks are clamped.
- Too weak or too strong: the object Displacement Scale and the shader scale multiply each other.
- Seams on hard edges: split normals at sharp edges open gaps; Maxon shows rounding the edges or adjusting the phong angle and edge handling.
- Texture displacement artifacts: texture displacement relies on a good UV unwrap; overlapping UVs, like those of a default cube, cause severe problems.
5. How to use vector displacement maps (VDM) in Redshift
Redshift supports both heightfield displacement, which moves vertices along the normal, and vector displacement, which moves them in any direction and can create overhangs. Vector maps can be in object or tangent space; use the space the map was exported in from ZBrush, Mudbox or Blender, and keep Maximum Displacement large enough for the longest vector.
6. Where should you render heavy displacement: SaaS or IaaS farm?
Displacement is calculated on the render machine, so the GPU memory of that machine decides how far you can push tessellation. A SaaS render farm suits scenes whose memory use you have already measured. An IaaS render farm such as iRender suits scenes you still need to tune: you open the scene on the same GPUs that will render it, watch memory in the RenderView, and adjust Minimum Edge Length before the batch render.
These videos show Cinema 4D and Redshift jobs on iRender multi-GPU servers.
On iRender you rent a whole server with 2x, 4x or 8x RTX 5090 or RTX 4090 GPUs, with Cinema 4D and Redshift pre-installed; Prime members get activated Cinema 4D and Redshift licenses. Related: GPU memory per card compared. Real render times are in our Redshift benchmark, and plans are on the Cinema 4D Redshift render farm page.
7. Redshift Displacement FAQ
How do I enable displacement in Redshift for Cinema 4D?
Add a Redshift Object tag to the object, open its Geometry tab and enable Override to access tessellation and displacement settings. Then connect a displacement texture to the material’s displacement output through a Displacement node and set Maximum Displacement and the displacement scale.
Why is my Redshift displacement flat on top?
Maximum Displacement is set lower than the displacement your shaders produce, so Redshift clamps the peaks. Set it to the largest total distance, for example 2 if two textures can each push vertices by 1 unit, and account for the object Displacement Scale.
Why does displacement use so much memory?
Every subdivision level multiplies the polygon count. Maxon gives the example of 1,000 quads becoming 65 million with a minimum edge length of 0 and 8 maximum subdivisions. Use Screen Space Adaptive, raise Minimum Edge Length and limit out-of-frustum tessellation.
What does Auto Bump Mapping do in Redshift?
It adds the displacement detail that the current tessellation cannot represent as bump mapping, as if the geometry had been tessellated to sub-pixel level. It lets you keep fewer subdivisions while preserving fine surface detail.
Does Redshift support vector displacement maps?
Yes. Redshift supports heightfield displacement along the vertex normal and vector displacement maps in object or tangent space. Make sure the map’s space matches how it was exported from the sculpting application.
Can I use adaptive tessellation on instanced objects?
No. Maxon notes that adaptive tessellation cannot be used when instancing in Redshift; instanced objects and proxies use fixed tessellation.
