November 14, 2026 Maddie Quach

Karma XPU Volume Rendering in Houdini: Pyro, VDB, Step Rate and Memory

VolumesRender Pyro and VDB volumes on Karma XPU
From SideFX documentation

Karma XPU renders volumes fast, but only with specific shaders and settings. Check these before a long Pyro render:

  • Shaders: XPU Pyro Preview, Karma Volume or Karma Whitewater VOP only
  • Step Rate: default 0.25; higher values cost render time quickly
  • Motion blur: volume blur on XPU only in Lookup Offset mode
  • Memory: each GPU holds the whole scene; trim fields and resolution
  • Houdini 22: volume lights in the light tree, equiangular MIS, iso-surface VDBs as uniform volumes

Smoke, fire, clouds and spray are where Karma XPU saves the most time over CPU rendering, and also where scenes most often fail on another machine: a volume renders grey or vanishes because its shader is not supported on XPU, motion blur looks different, or the VDB caches do not fit in GPU memory.

This guide covers which volume shaders and features Karma XPU supports, how Volume Step Rate trades noise for time, how to keep volume memory under control on 32 GB cards, and what Houdini 22 changes for volume rendering. Simulation memory is a separate topic, covered in our guide to Pyro simulations running out of memory.

Checked against the SideFX Houdini 22 documentation (Karma XPU, Karma Render Settings, What’s new in Karma for Houdini 21 and 22), November 2026.

Which volume shaders render on Karma XPU

The Karma XPU page is explicit: only the XPU Pyro Preview, Karma Volume and Karma Whitewater VOPs work as volume shaders. A Pyro scene set up with another shader for Karma CPU can therefore render grey, look different or disappear when you switch to XPU. Assign one of the three before you compare renders.

iRender
What Karma XPU Does With a Pyro Shader
Schematic
Pyro cacheVolume shaderon Karma XPU?one of the 3any otherrenders with fire and smokeXPU Pyro Preview, Karma Volume,Karma Whitewater VOPgrey, different or missingshader not supported on XPUAssign one of the three VOPs before comparing a CPU and an XPU render of the same Pyro cache.
supported shaderother shader
Schematic based on SideFX Karma XPU docs

A few volume features are limited on XPU: volume filter and width parameters are not supported, uniform volumes work only on mesh and point prims with constant primvars, and volume lights do not support Active Radius or Shadow Distance. Volume motion blur works only in Lookup Offset mode, so check blurred fire on XPU before the full sequence.

Sources: Karma XPU, What’s new in Houdini 21: Karma.

Volume Step Rate: noise against render time

Volume Step Rate sets how finely Karma samples a volume as a ray travels through it. The default of 0.25 means one sample every four voxels; 1 samples every voxel and 2 samples every voxel twice. SideFX describes it as behaving like pixel samples: a multiplier on the total number of samples for volumes.

iRender
What Volume Step Rate Changes
Schematic
one camera ray crossing 16 voxelsStep Rate 0.25default · 1 per 4 voxels4 samplesStep Rate 1every voxel16 samplesStep Rate 2every voxel twice32 samplesVolume Step Rate multiplies volume samples, like pixel samples multiply camera rays.Raise it only for visible volume noise: render time grows with it.
default1 sample per voxel2 per voxel
Schematic based on SideFX Karma render settings help

SideFX warns that raising the step rate can dramatically increase render times and should only be adjusted when necessary, and the Karma Render Settings help notes that values beyond 1 rarely change the result much. Raise pixel samples or use denoising for general noise first, and raise the step rate only when the volume itself shows grain or banding.

ReferenceVolume settings

Karma settings that change volume quality and cost

From the Houdini 22 Karma Render Settings and Karma XPU pages.

SettingWhat it doesPractical use
Volume Step RateHow finely or coarsely a volume is sampled as a ray travels through it; default 0.25 = one sample per 4 voxelsRaise only for visible volume noise; it acts like a multiplier on volume samples
Volume LimitThe number of times a volumetric ray can propagate through the scene (0–65535 on XPU)Thick clouds with multiple scattering need more; thin smoke needs few
Volume Velocity Blur ScaleVelocity multiplier that reduces or exaggerates motion blur on volumesOn XPU, volumes blur only in Lookup Offset mode
Pixel samples and denoiserOverall image noiseTry these before touching the volume step rate
Rule: fix noise with pixel samples and denoising first; change the step rate only where the volume itself is noisy.

Setting names are from the Karma Render Settings LOP.

Sources: Karma Render Settings, Karma LOP, Karma XPU.

Keeping volume memory under control

Karma XPU does not pool memory across GPUs: each card holds its own copy of the scene, so a 4-GPU server has 32 GB per card available on the RTX 5090, not 128 GB. If a GPU runs out of memory, that device drops out and the others, including the CPU, finish the frame more slowly. Textures load on demand in tiles and can be evicted when memory fills, but SideFX notes the GPU slows down significantly in that eviction state.

Volume memory is mostly decided before rendering, in SOPs:

  • Write only the fields the shader reads. A Pyro shader typically needs density, temperature and flame; velocity is needed only for motion blur. Extra fields in the cache cost memory and load time.
  • Match voxel size to the shot. A sim cached at a finer resolution than the camera resolves costs memory on every GPU without visible gain.
  • Use VDB caches rather than dense Houdini volumes, and keep them inside the project so another machine finds them.
  • Check per-GPU memory in the render stats before rendering the range.

Houdini 21 added data deduplication, which reduces memory when identical geometry or primvars appear in a scene, and Houdini 22 cut memory for subdivided meshes by up to half. For card sizes and budgets, see how much VRAM Houdini GPU rendering and volumes need.

Sources: Karma XPU, What’s new in Houdini 21: Karma, What’s new in Houdini 22: Karma.

iRender
Trimming a Pyro Cache Before It Reaches the GPU
Schematic
Pyro cache written for renderingdensityshader reads ittemperatureshader reads itflameshader reads itvelonly for motion blurscratch fieldsnot needed to renderGPU 0: everything cacheddensitytempflamevelscratchGPU 0: trimmed cachedensitytempflamevelEvery GPU holds the full cache: a field you drop is saved on each card. Drop vel too if the shot has no motion blur.
neededonly for blurnot needed
Schematic; field sizes illustrative

Trimming happens in SOPs before the cache is written, so it also shortens upload and load time on the render machine.

What Houdini 22 changes for volumes

Several Houdini 22 changes affect volume-heavy shots:

  • Volume lights join the light tree. SideFX expects significantly shorter render times, particularly with many volume lights such as explosions lit by their own fire.
  • Equiangular MIS on lights significantly reduces noise when a light is inside a volume or very close to it.
  • Iso-surface VDBs can render directly as uniform volumes on Karma XPU, without converting to a mesh first.
  • Uniform Volume Material now uses the Karma Volume VOP, so it no longer needs a density field, and the Whitewater material supports a specular layer over a uniform volume.

For simple atmosphere, the Karma Fog Box LOP creates a constant volume within a box without any VDB at all. Volume lights themselves came in Houdini 21 through the Geometry Light LOP and its VolumeLightAPI option.

Sources: What’s new in Houdini 22: Karma, What’s new in Houdini 21: Karma.

SaaS or IaaS render farm for Karma XPU volumes?

CompareNeutral guide

Which farm type fits a volume-heavy shot

Both render volumes; they differ in how much you can test on the target GPU first.

SituationUsually a better fitWhy
Pyro cache tested on XPU, fits comfortably in 32 GBSaaS (managed farm)Upload caches and submit
Cache close to the VRAM limitIaaS with 32 GB cardsYou watch per-GPU memory and trim fields before the full run
Shader or motion blur not yet checked on XPUIaaS (remote workstation)Render a frame, compare with CPU, fix in the same session
Very large caches (hundreds of GB)IaaSUpload once to storage on the machine and keep it between sessions
Short one-off renderSaaSNo setup time

Rule of thumb: if the volume already renders correctly on XPU and fits on one card, a managed farm is the least work. If you are still checking shaders, blur or memory, a machine you control lets you fix it on the spot.

Rendering volumes on an iRender server

iRender
How iRender works: your computer controls your own multi-GPU server
IaaS render farm
Your PC or MacNo powerful GPU neededRemote desktopLive screen1:1 like your PCYOUR OWN GPU SERVERbare-metal · not sharedGPUGPUGPUGPUGPUGPUGPUGPU1, 2, 4 or 8 × RTX 5090 (32 GB) or RTX 4090 (24 GB)Threadripper PRO · 256 GB ECC RAM · 2 TB NVMe SSDFull admin access · your setup is saved between sessions1Register, top upFirst $50+ top-up doubled2Upload your projectiRender Drive, free3Start and connectRemote desktop, any OS4Render, shut downBilling stops, per minute✓ Your workstation, just more GPUs: no queue to wait, no farm plugin, no job submission, no settings changed
Your mouse and keyboardServer screen streamed back
Schematic, not to scale

On iRender you rent a whole Windows workstation with your own Houdini, so the VDB caches and the scene behave exactly as on your desk:

  1. Upload the project and VDB caches through iRender Drive with relative paths.
  2. Start a 4x RTX 5090 server (32 GB per card), which we recommend for Karma XPU; 8x servers also render Karma XPU, but it does not get proportionally faster.
  3. Install your Houdini build. The Karma XPU kernels compile on the first render and the cache stays on your saved server image.
  4. Render the heaviest frame and check that all four GPUs stay in the device list and no card enters eviction.
  5. Render the range with husk or the USD Render ROP.

Volume checklist before the full render

Use this as a final check before you start the full range on any machine.

ChecklistVolume checklist before the full render
0 / 7 done
Tip: tick each item as you set up the job; the ticks reset when the page reloads.

Frequently asked questions

1. Why does my Pyro volume render grey or disappear on Karma XPU?

Karma XPU supports only the XPU Pyro Preview, Karma Volume and Karma Whitewater VOPs as volume shaders. Assign one of them.

2. What does Volume Step Rate do in Karma?

It sets how often a volume is sampled along a ray. The default 0.25 means one sample per four voxels; higher values reduce volume noise but increase render time sharply.

3. Does Karma XPU support volume motion blur?

Yes, but only in Lookup Offset mode.

4. Can four GPUs share the memory of one large VDB?

No. Karma XPU memory is not pooled; each GPU must hold the whole scene, including volumes.

5. What changed for volumes in Houdini 22?

Volume lights joined the light tree, equiangular MIS reduces noise near lights in volumes, iso-surface VDBs render as uniform volumes on XPU, and the Uniform Volume Material no longer needs a density field.

6. How do I add simple fog without a VDB?

Use the Karma Fog Box LOP, which creates a constant volume within a box.

7. Can a volume emit light in Karma XPU?

Yes, from Houdini 21: the Geometry Light LOP with the VolumeLightAPI option turns a volume into a light. Houdini 22 adds volume lights to the light tree.

8. Can Karma XPU render an iso-surface VDB without meshing it?

Yes, in Houdini 22: Karma XPU can render iso-surface VDBs directly as uniform volumes, without the detour through a mesh.

Render your Houdini Karma XPU scenes on iRender

iRender is an IaaS GPU render farm: you rent a bare-metal server with 4x NVIDIA 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 Houdini and use your own SideFX license; your server image is saved between sessions, so Houdini, your packages and the Karma XPU kernel cache stay installed. For Karma XPU we recommend the 4-GPU servers.

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 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 video walks through rendering a Houdini Karma XPU scene on an iRender server in five steps:

New users get a 100% bonus on the first top-up (minimum $50). See the Karma XPU render farm page for server options, or download the iRender GPU app.

If Karma XPU renders are slow on your machine, iRender’s Karma XPU render farm gives you a dedicated remote server where you install Houdini, bring your own license and render on multiple RTX 5090 GPUs (for Karma XPU, 4 GPUs is usually the most efficient setup).

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by 4x 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:
, ,

Maddie Quach

Maddie Quach, from iRender's customer support team, has written more than 100 articles for the iRender blog on Maya, Houdini, Arnold, Karma XPU and Redshift.
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
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →