November 11, 2026 Linh Nguyen

Blender Cycles Displacement and Adaptive Subdivision (2026): Dicing Rate, Memory and Animation

Quick answerDisplacement and adaptive subdivision in Cycles
Checked Nov 2026

In Blender 5.0, adaptive subdivision is no longer experimental and is always available in the Subdivision Surface modifier. Cycles then subdivides each object at render time based on its size on screen, controlled by Dicing Rate, Offscreen Scale and Max Subdivisions in Render › Subdivision. For animation with a moving camera, set a Dicing Camera so detail does not crawl.

  • Enable: material Displacement method + Adaptive Subdivision on the modifier.
  • Detail: Dicing Rate Render: lower is finer and uses more memory.
  • Memory: raise Offscreen Scale and set Max Subdivisions.
  • Animation: Dicing Camera stops crawling artifacts.

Displacement turns a texture into real geometry, and adaptive subdivision makes that practical by adding detail only where the camera can see it. Both can also fill a GPU quickly if the dicing is too fine.

This guide covers what changed in Blender 5.0, the settings that control displacement detail and memory, and how to keep displaced surfaces stable across an animation rendered on several GPUs.

Checked against the Blender 5.0 Cycles release notes and the Blender Manual (Subdivision, Adaptive Subdivision, Material Settings), November 2026.

1. What changed in Blender 5.0

The Blender 5.0 release notes state that adaptive subdivision is no longer an experimental feature and is always available in the Subdivision Surface modifier; 5.0 also added an Object space option to specify edge length in object space rather than pixel size (Blender 5.0: Cycles). With displacement, the Normal Map node now uses the undisplaced normal and tangent, matching EEVEE. Files that relied on the Experimental feature set no longer need it.

2. Turning on true displacement

Two settings are needed. In the material, set the displacement method under Settings to Displacement Only or Displacement and Bump; with Bump Only, the Displacement output shades the surface but does not move geometry (Blender Manual: Material Settings). Then add a Subdivision Surface modifier and enable Adaptive Subdivision, so Cycles subdivides the mesh at render time (Blender Manual: Adaptive Subdivision).

iRender
Bump vs true displacement
Schematic
Bump Onlynormals tilted, surface stays flatDisplacementgeometry moves: real silhouette and shadowsBump changes shading only; displacement changes the shape, which is why it needs subdivisionBlender Manual: Material Settings (Displacement method)
bump: shading onlydisplacement: geometrytilted normals
Schematic, not to scale

Bump only changes how light hits the surface, so edges and shadows stay flat. True displacement moves vertices, and moving vertices needs enough of them, which is the job of adaptive subdivision shown next.

iRender
Adaptive subdivision: detail follows the camera
Schematic
Cameranear: fine dicingmid: coarserfar: coarseoutside the view:Offscreen ScaleDicing Rate sets micropolygon size relative to the camera; Max Subdivisions caps the levelAdaptive subdivision dices finely near the camera and coarsely far away or off screenBlender Manual: Subdivision; Blender 5.0 release notes
nearmidfaroff screen
Source: Blender Manual, Subdivision; Blender 5.0 release notes

3. Dicing rate, offscreen scale and memory

In Render › Subdivision, Dicing Rate is a multiplier for the size of micropolygons in the final and viewport render. Offscreen Scale increases the dicing rate gradually for geometry outside the camera view; the Manual notes lower values give better reflections and shadows of off-screen objects, while higher values use less memory. Max Subdivisions stops subdividing at that level even if the dicing rate would produce finer tessellation (Blender Manual: Subdivision).

Displaced geometry is held on every GPU, so a dicing rate that is too fine is a common reason for out-of-memory errors on large terrains. Test the heaviest frame and raise Dicing Rate or Offscreen Scale before lowering texture quality; see Cycles GPU memory.

iRender
Dicing Rate: micropolygon size on screen
Schematic
Dicing Rate 1about one micropolygon per pixelDicing Rate 4coarser: fewer triangles, less memoryDashed: 4 × 4 pixelsLower rate = finer detailand more memoryMax Subdivisions capsthe level whatever the rateOffscreen Scale coarsensgeometry out of viewDicing Rate is a multiplier for micropolygon size: raise it first when displacement runs out of memoryBlender Manual: Subdivision (render settings)
fine dicingcoarse dicingpixel grid
Schematic, not to scale

A rate of 4 instead of 1 means each micropolygon covers several pixels, so far fewer triangles are stored on every GPU. The table below lists where each of these settings lives.

SettingsBlender 5.x + Cycles

Where displacement and subdivision are set

The settings to check when displacement looks wrong or memory runs out.

SettingWhereWhat it does
Displacement methodMaterial › Settings › SurfaceBump Only, Displacement Only, or Displacement and Bump; true displacement needs one of the last two
Adaptive SubdivisionSubdivision Surface modifierSubdivides at render time based on distance to the camera; no longer experimental in 5.0
Dicing Rate RenderRender › SubdivisionMultiplier for micropolygon size in the final render; lower is finer and uses more memory
Offscreen ScaleRender › SubdivisionCoarser dicing outside the camera view; higher uses less memory
Max SubdivisionsRender › SubdivisionStops subdividing at this level even if the dicing rate asks for more
Dicing CameraRender › SubdivisionFixed reference camera to avoid crawling detail when the render camera moves
MemoryDisplacement memory comes from the dicing: raise Dicing Rate or Offscreen Scale before buying a bigger GPU.

4. Animation: crawling detail and the Dicing Camera

Because dicing follows the camera, a moving camera re-dices surfaces every frame, which can make fine displacement shimmer or crawl. The Manual describes Dicing Camera as a reference camera for subdivision that avoids crawling artifacts when the scene camera moves. Set it, render a short range of frames and play them back before the full sequence. When frames are split across GPUs, every instance must use the same file and settings, as in our guide to multi-GPU rendering in Cycles.

iRender
Dicing Camera stops crawling displacement
Schematic
Render camera moving, no Dicing Camera: dicing changes every frame (crawl)frame 1frame 2frame 3Dicing Camera set: the same dicing every frame (stable)frame 1frame 2frame 3Set Render › Subdivision › Dicing Camera for shots where the camera moves over displaced surfacesBlender Manual: Subdivision (Dicing Camera)
re-diced each framefixed dicing
Schematic, not to scale

With a Dicing Camera, the subdivision is computed from one fixed viewpoint, so the triangles on a surface stay the same from frame to frame even while the render camera moves.

A displacement checklist before a long render

  1. Material: Displacement Only or Displacement and Bump set
  2. Modifier: Adaptive Subdivision enabled on the Subdivision Surface modifier
  3. Detail: Dicing Rate Render tested on the closest shot
  4. Memory: Offscreen Scale and Max Subdivisions set; peak memory checked
  5. Animation: Dicing Camera set for moving-camera shots; short range played back
  6. Normal maps: checked after upgrading to 5.0, since the Normal Map node now uses undisplaced normals

For paths, caches and other scene checks, see our 10-point Blender Cycles pre-flight checklist.

Both farm models can render displacement. On an IaaS server you can adjust dicing on the same GPUs that render the sequence, watch memory on the heaviest frame and play back a short range before committing.

Rendering displacement on an iRender server

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.c4d · .blend · .hip1 GPUYour iRender serverscene.c4d · .blend · .hipup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found
  1. Upload the project folder to iRender Drive before you start the server; uploading is free and does not use rental time.
  2. Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs and connect by remote desktop.
  3. Render the heaviest frame, check memory and adjust Dicing Rate.
  4. Render the sequence one Blender per GPU, then shut down; multi-GPU servers are billed per minute.

Frequently asked questions

1. Is adaptive subdivision still experimental in Blender?

No. Since Blender 5.0 it is no longer experimental and is always available in the Subdivision Surface modifier.

2. Why does my displacement only look like bump?

The material displacement method is probably Bump Only. Set it to Displacement Only or Displacement and Bump.

3. How do I reduce displacement memory in Cycles?

Raise Dicing Rate Render, raise Offscreen Scale, and set Max Subdivisions.

4. Why does displacement crawl in my animation?

Dicing follows the moving camera. Set a Dicing Camera in Render › Subdivision.

5. Did normal maps change with displacement in 5.0?

Yes. The Normal Map node now uses the undisplaced normal and tangent, matching EEVEE.

Render your Blender 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. You install Blender once; your server image is saved between sessions, so Blender and your add-ons stay installed.

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 Blender on it:

Two Blender runs we recorded on our servers: 120 frames at 1080p on 4x RTX 5090 at 72 seconds per frame, and the same 4K scene on 4x RTX 5090 and 4x RTX 4090 at 87 and 108 seconds per frame per GPU:

New users get a 100% bonus on the first top-up (minimum $50). See plans on the Blender render farm page or download the iRender GPU app.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, ,

Linh Nguyen

Linh Nguyen works in customer support at iRender, helping artists render Blender and Houdini projects on multi-GPU servers. She has written more than 300 articles for the iRender blog, covering Blender, Houdini and practical GPU rendering.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →