Karma Motion Blur in Houdini: Time Samples, Velocity Blur and Farm Checks
Karma blurs what the USD stage gives it. Most farm surprises come from missing time samples or the wrong blur type:
- Samples: Karma needs 2+ time samples on the stage; Motion Samples from Stage is on by default
- Deformation: point count must stay the same between samples
- Velocity: FLIP and particles: store velocities (SOP v); deformation blur is then ignored
- Memory: each extra geometry sample keeps another copy of the geometry in memory
- XPU: volumes blur only in Lookup Offset mode
Motion blur is one of the easiest things to get wrong when a Solaris scene moves to another machine. The interactive render looks blurred because Houdini cooks the frame on the fly; the farm render looks sharp because the USD file written for it only has one time sample per frame. Or the blur is there, but particles streak in the wrong direction because the wrong blur type is active.
This guide explains how Karma reads time samples, when to use transform, deformation, velocity and acceleration blur, what extra samples cost in memory on Karma XPU, and how to make sure the USD you render on a farm carries the samples the blur needs.
Checked against the SideFX Houdini 22 documentation (Karma User Guide: Motion Blur, Motion Blur LOP, Render Geometry Settings, Karma XPU), November 2026.
Karma blurs the time samples on the USD stage
SideFX’s Karma guide states the rule simply: once two or more time samples exist on geometry prims, Karma renders transform or geometry motion blur. The Karma render settings have Motion Samples from Stage on by default, so Karma uses all time samples that fall inside the shutter; adjusting Transform and Geometry Time Samples is usually unnecessary as long as the USD holds enough samples.
Two samples (shutter open and close) give one straight segment of blur. Fast arcs, spinning wheels and whip-pans need more: the transform and geometry time sample defaults are 2. If the samples on the stage do not line up with the camera’s shutter times, SideFX notes minor interpolation issues at the first and last segments, because the motion is truncated instead of interpolated.
Sources: Karma User Guide: Motion Blur.
Transform, deformation, velocity or acceleration blur
Karma supports four ways to blur an object, and they need different data:
- Transform blur comes from animated transforms and is cheap.
- Deformation (geometry) blur comes from points that change over time. It needs multiple time samples in USD, and the number of points cannot change between samples.
- Velocity blur uses a point attribute named
velocitiesin USD, which is the SOPvattribute. It is the right choice for FLIP fluids, particles and remeshed geometry whose point count changes every frame. When velocity blur is on, deformation blur is ignored. - Acceleration blur uses
accelerations(SOPaccel) to blur along curves; SideFX notes three or more samples are needed for the blur to be non-linear, and acceleration blur ignores Motion Samples from Stage.
Choose the blur type per object on the Render Geometry Settings LOP: No Velocity Blur, Velocity Blur or Acceleration Blur.
Sources: Karma User Guide: Motion Blur, Render Geometry Settings LOP.
Writing enough time samples into the USD for the farm
On your workstation, Houdini can cook subframes whenever Karma asks. A farm job renders a USD file, so the samples have to be in that file. SideFX calls the Motion Blur LOP the simplest way to author sufficient time samples: placed after the Karma Render Settings, it caches enough samples to blur across the shutter, using the render settings camera, and it can use the camera’s shutter settings to author only the samples it needs. Turning on Velocity Blur on that node also adds Karma’s velocity blur render property.
The Cache LOP caches time samples around the current frame or across the timeline and removes the Houdini time dependency. Volumes are a special case: USD does not store volumes directly, so to blur changing volumes you animate a different volume asset path at each time sample, or use velocity blur on the VDB.
Before the full range, render one fast-moving frame from the saved USD with husk, not from the interactive viewport, and compare the blur.
Sources: Motion Blur LOP, Karma User Guide: Motion Blur.
The quickest check is the one in the last step: render the saved USD with husk on any machine and compare the blur with your viewport.
What extra samples cost on Karma XPU
More samples are not free. SideFX notes that increasing Geometry Time Samples can affect how much memory Karma uses, because each extra sample keeps another copy of the geometry in memory while the shutter is sampled. On Karma XPU that copy is needed on every GPU, since memory is not pooled across cards.
Karma XPU supports motion blur with all associated settings (light, camera, transform, deformation and volume blur), with one limit: volume motion blur works only in Lookup Offset mode. Use the fewest samples that give a smooth result, raise them only on the objects that need arcs, and check per-GPU memory on the heaviest frame. For volume blur details, see our guide to Karma XPU volume rendering.
Sources: Karma User Guide: Motion Blur, Karma XPU.
SaaS or IaaS render farm for motion-blurred shots?
Which farm type fits a motion-blur-heavy shot
Both render blur; they differ in how easily you can check the saved USD first.
| Situation | Usually a better fit | Why |
|---|---|---|
| Time samples already baked into the USD and checked | SaaS (managed farm) | Upload the USD and submit |
| Blur only checked in the viewport so far | IaaS (remote workstation) | Render a frame from the saved USD with husk and fix samples on the spot |
| FLIP or particles with changing point count | IaaS | Check velocity blur direction and scale before the full run |
| Many geometry samples on heavy meshes | IaaS with 32 GB cards | Watch per-GPU memory on the heaviest frame |
| Short one-off render | SaaS | No setup time |
Rule of thumb: once the blur renders correctly from the saved USD, a managed farm is the least work. While you are still checking samples or blur types, a machine you control saves round trips.
Rendering motion blur on an iRender server
On iRender you rent a whole Windows workstation, install your own Houdini build and sign in with your own SideFX license, so the scene opens exactly as on your desk:
- Upload the project, including caches written with enough time samples, through iRender Drive.
- 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.
- Install your Houdini build. The Karma XPU kernels compile on the first render and the cache stays on your saved server image.
- Render the fastest-moving frame with husk from the saved USD and compare the blur with your interactive render.
- Render the range with husk or the USD Render ROP.
Motion blur checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Why is my Karma render sharp on the farm but blurred locally?
The saved USD probably has one time sample per frame. Author samples with the Motion Blur LOP or a Cache LOP before writing the USD.
2. How many motion samples does Karma need?
At least two. The transform and geometry defaults are 2; more samples follow arcs and spins better but use more memory.
3. How do I blur FLIP fluids or particles in Karma?
Use velocity blur with the velocities attribute (SOP v). It works when the point count changes between frames; deformation blur does not.
4. Does Karma XPU support motion blur?
Yes, including camera, transform, deformation and volume blur. Volume motion blur works only in Lookup Offset mode.
5. Do extra motion samples use more memory?
Yes. Each extra geometry sample keeps another copy of the geometry in memory, on every GPU with Karma XPU.
6. What does Motion Samples from Stage do?
It makes Karma use all time samples authored on the USD stage within the shutter. It is on by default.
7. Why does my velocity blur ignore deformation?
When velocity blur is on, Karma ignores deformation blur for that object; pick the blur type per object on the Render Geometry Settings LOP.
8. How do I blur a spinning object along an arc?
Use more transform samples, or acceleration blur with accelerations (SOP accel) and three or more samples for non-linear blur.
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.
Sources: Karma User Guide: Motion Blur, Motion Blur LOP, Render Geometry Settings LOP, Karma XPU. Checked November 2026.
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).


