Octane Displacement in Cinema 4D: Texture vs Vertex, Mid Level and Memory
Octane has two displacement systems that behave very differently. The main points from OTOY's documentation:
- Texture Displacement: Image maps with UVs; detail set by Level of Detail without heavy tessellation. Higher LoD raises VRAM and render time.
- Vertex Displacement: Moves real vertices; works with procedurals, OSL, height and vector maps; needs a dense mesh or a Subdivision Level.
- Mid Level 0.5: For maps where 50% grey is the base surface, set Mid Level to 0.5 so edges line up.
- Motion blur: A deformed object with texture displacement does not blur properly; use vertex displacement instead, as OTOY advises.
- Heavy displacement: Octane does not pool VRAM across GPUs; iRender RTX 5090 servers with 32 GB per GPU give more room for high Level of Detail and dense subdivided meshes.
Displacement is where Octane scenes most often go wrong: floating surfaces, missing polygons, blocky detail or a GPU running out of memory. Most of these come from choosing the wrong node or a wrong Mid Level. This guide follows OTOY’s documentation and troubleshooting guide.
Checked against the Cinema 4D and OctaneRender documentation, November 2026.
Symptoms this guide fixes: polygons vanish or clip as the camera moves, the displaced surface floats above or sinks below where it should, or the detail looks blocky and faceted.
1. How does Octane turn a height map into displacement?
The height map is read relative to the Mid Level, and Height sets the strength (OTOY: Displacement). The figure shows what Mid Level 0.5 means and how the two node types get their detail.
With Mid Level at 0.5, 50% grey stays on the original surface, white pushes outward and black pushes inward. Texture displacement creates fine detail on few polygons through its Level of Detail. Vertex displacement moves the mesh’s real vertices, so detail depends on how dense the mesh is.
Which Octane displacement node to use
From OTOY documentation for Octane in Cinema 4D and other hosts.
| Point | Texture Displacement | Vertex Displacement |
|---|---|---|
| Inputs | Image textures with UV coordinates; procedurals must be baked first | All textures: images, procedurals, OSL; height and vector maps |
| Detail comes from | Level of Detail (internal map resolution); does not need heavy tessellation | Mesh density and the Subdivision Level setting |
| Memory and time | Higher Level of Detail raises VRAM use and render time | Higher subdivision raises render and pre-processing time |
| Known limits | Can show missing or clipped polygons; motion blur on deformed, texture-displaced meshes does not render properly | Slower, more robust; mix several with the Vertex Displacement Mixer |
2. How to set up displacement in Octane (step by step)
Settings checklist (copy or follow line by line):
Displacement node choice Texture Displacement .. image maps with UVs; detail from Level of Detail Vertex Displacement ... procedurals, OSL, vector maps, deforming / motion blur Displacement node Texture ............... flat image file, linear Mid Level ............. 0.5 (50% grey = no displacement) Height ................ start small, raise while watching the silhouette Level of Detail ....... (texture) raise until shadows look clean Subdivision Level ..... (vertex) or render-time subdivision in the Octane Object tag Map type .............. Height for b&w maps, Vector for vector maps
Step 1: Choose the node
Use Texture Displacement for image maps on static or rigid objects; Vertex Displacement for procedurals, vector maps, deforming objects and shots with motion blur.
Step 2: Load the map correctly
Use a flat image file in linear color space. Set Mid Level to 0.5 if 50% grey is the base surface.
Step 3: Set Height in scene units
Start with a small Height and increase it while watching the silhouette in the Live Viewer.
Step 4: Set resolution
Texture: raise Level of Detail until shadows on the surface look clean. Vertex: raise Subdivision Level, or subdivide in the Octane Object tag at render time (OTOY: subdivision and polygons).
Step 5: Check memory
Watch VRAM use in the Live Viewer as you raise detail, and stop at the lowest setting that looks right at final resolution.
Quick check: if edges of a tiling texture do not line up or the surface floats, check Mid Level 0.5 and that the map is linear; if polygons vanish, raise Level of Detail and base mesh density.
3. Why does Octane displacement look wrong?
OTOY’s troubleshooting guide covers the common cases (OTOY: Displacement troubleshooting).
Common displacement problems and fixes
From OTOY's "Displacement in Octane for Cinema 4D" troubleshooting guide.
| Symptom | Likely cause | Fix |
|---|---|---|
| Nothing displaces | Texture not loading (e.g. PSD with effects or vector layers) | Test the texture in the albedo channel; save as a flat image |
| Missing or clipped polygons | Texture displacement filtering and resolution | Adjust the filter, raise base mesh density, texture resolution and Level of Detail |
| Blocky or faceted result | Map or mesh too low resolution | Texture: raise map and LoD. Vertex: raise map and polygon count |
| Edges do not line up, surface floats | Wrong Mid Level or color space | Linear map with Mid Level 0.5; adjust gamma in the Image Texture node for vertex displacement |
| Vector map looks wrong | Map type mismatch | Height for black and white maps, Vector for vector maps |
For animation, note the motion blur limitation: OTOY staff confirmed that a deformed object with texture displacement does not render motion blur properly, and recommended vertex displacement (OTOY forum).
Watch VRAM as you raise detail. A higher Level of Detail (texture displacement) or Subdivision Level (vertex displacement) increases memory use and render time, and Octane does not pool VRAM across GPUs, so every GPU must hold the displaced scene.
4. Where should you render displacement-heavy scenes: SaaS or IaaS farm?
A SaaS render farm renders the scene with the displacement settings you uploaded, which suits a finished, tested file. An IaaS render farm such as iRender gives you the full Cinema 4D and Octane session, so you can check VRAM use and adjust Level of Detail or subdivision on the same GPU that renders the final frames.
These videos show Cinema 4D and Octane 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 OctaneRender pre-installed. You sign in with your own OTOY account; for multi-GPU servers OTOY’s Studio+ plan has no GPU limit. Related: displacement in Redshift. Plans and real render times are on the Octane render farm page.
5. Octane displacement FAQ
What is the difference between texture and vertex displacement in Octane?
Texture displacement uses an image map and UVs and builds detail from its Level of Detail setting, without dense geometry. Vertex displacement moves the mesh’s actual vertices, works with any texture including procedurals, and needs a dense mesh or a subdivision level.
What Mid Level should I use for Octane displacement?
Use 0.5 when 50% grey in the map means no displacement, which is the case for most ZBrush exports and linear height maps. Then grey stays on the original surface, white goes out and black goes in.
Why are polygons missing in my Octane texture displacement?
OTOY notes this is almost always seen with texture displacement. Adjust the filter value, increase base mesh polygons and texture resolution, and raise the Level of Detail.
Can I use procedural noise for displacement in Octane?
Yes, with the Vertex Displacement node, which supports procedural and OSL textures. Texture displacement needs image textures, so procedurals must be baked first.
Does displacement work with motion blur in Octane?
Vertex displacement does. OTOY staff explain that a deformed object with texture displacement will not render motion blur properly, and recommend vertex displacement for that case.
Why does Octane displacement use so much VRAM?
A high Level of Detail in texture displacement and a high subdivision level in vertex displacement both increase memory and render time. Use the lowest setting that holds up at your final resolution and camera distance.
