Hair and Fur on Karma XPU: Curves, Procedural Hair and GPU Memory
Hair is where Karma XPU is strongest and where GPU memory runs out first. Key points:
- Curves: Karma XPU renders rounded tubes only; ribbons need Karma CPU
- Topology: wrong vertex counts for the curve basis make curves disappear
- Sampling: SideFX: hair resolves better with Path Traced convergence on XPU
- Procedural: Houdini Procedural: Hair builds curves at render time and saves disk
- Memory: every rendered curve sits on every GPU; KARMA_XPU_OPTIX_CURVE_OPT_LEVEL trades memory for speed
Creatures, characters and grass mean millions of thin curves. Karma XPU handles them well, and SideFX itself notes that scenes with lots of hair tend to resolve better with Karma XPU. They are also among the heaviest data in a scene: every rendered curve has to fit in each GPU, and cached hair can run to large files per frame that have to reach the render machine.
This guide covers how Karma renders curves, the topology rules that make curves vanish, the render-time Hair Procedural, sampling for fur, and how to keep curve memory under control on 32 GB cards.
Checked against the SideFX Houdini 22 documentation (Karma User Guide: Geometry, Karma XPU, Houdini Procedural: Hair), November 2026.
How Karma renders curves
Karma renders curves as rounded tubes by default and can also render ribbons and oriented ribbons, with the curve basis overridable at render time. On Karma XPU only rounded curves are supported, and the XPU page adds that disabling backface culling on curves is not supported. If a groom was set up as ribbons for Karma CPU, expect it to render as tubes on XPU.
Topology matters. USD BasisCurves are either linear or cubic, and SideFX warns that different curve types need different numbers of vertices for a strand to be valid; incorrect topologies can make curves disappear or look strange. The Karma guide recommends non-periodic linear curves for most cases and pinned cubic B-splines when you need smoother curves.
Sources: Karma User Guide: Geometry, Karma XPU.
Render-time hair with the Houdini Hair Procedural
Caching every render curve for every frame produces large files that take time to write, upload and load. The Houdini Procedural: Hair LOP, available since Houdini 19.5, provides a render-time hair solution that saves disk space. In Generate mode it creates new curves interpolated from existing guides; in Deform mode it deforms existing render curves using the guides. Its Animated Procedural option decides whether it is evaluated before each frame or only at the start of the render.
The procedural runs inside husk at render time, so test it on the render machine: Python run by husk can check out an Engine license, according to SideFX’s licensing FAQ. The saving is in disk and upload size; the generated curves still occupy GPU memory during the render.
Sources: Houdini Procedural: Hair LOP, SideFX FAQ: husk licenses.
Sampling noisy fur
Thin curves are hard to sample: each pixel sees many strands, so fur stays noisy longer than surfaces. SideFX’s Karma guide gives direct advice: scenes with lots of hair or fur tend to resolve better with Path Traced convergence and with Karma XPU, and relying heavily on secondary samples to clean up noisy fur gets very expensive. Raise pixel samples and use the denoiser before adding secondary samples.
Shading also changes the cost. Houdini 21 updated the fur shader, and Houdini 21 lets Karma displace curve vertices when a displacement shader is applied to curves. Keep displacement on curves for close-ups, where it is visible.
Sources: Karma User Guide: Geometry, What’s new in Houdini 21: Karma.
Keeping curve memory inside one GPU
Karma XPU memory is not pooled, so a 4x RTX 5090 server gives a groom 32 GB per card, not 128 GB. Curve count, segments per curve and per-vertex attributes (width, colour, UVs) all multiply. Ways to bring a heavy groom down:
- Reduce curve density for characters far from camera; generate full density only for close-ups.
- Drop per-vertex attributes the shader does not read.
- Use fewer segments on short fur.
- Try the curve optimisation level below.
SideFX documents KARMA_XPU_OPTIX_CURVE_OPT_LEVEL as a trade between curve memory and performance: 1 favours lower memory, 2 is the default, 3 favours performance. Houdini 21 also added data deduplication, which reduces memory when identical geometry or primvars appear. For budgets per card, see how much VRAM Houdini GPU rendering needs.
Sources: Karma XPU, What’s new in Houdini 21: Karma.
SaaS or IaaS render farm for hair and fur?
Which farm type fits a groom-heavy shot
Both render curves; they differ in how easily you can test memory and the procedural on the target GPU.
| Situation | Usually a better fit | Why |
|---|---|---|
| Cached hair that already fits comfortably in 32 GB | SaaS (managed farm) | Upload caches and submit |
| Hair Procedural evaluated at render time | IaaS (remote workstation) | Check the procedural and its license on the machine that renders |
| Groom close to the VRAM limit | IaaS with 32 GB cards | Compare curve optimisation levels on the heaviest frame |
| Very large hair caches | IaaS | Upload once and keep them between sessions |
| Short one-off render | SaaS | No setup time |
Rule of thumb: if the groom is cached and fits on one card, a managed farm is the least work. With render-time procedurals or tight memory, a machine you control lets you test on the spot.
Rendering hair 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 with guide or hair caches 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 frame with the most hair on screen and check per-GPU memory and the device list.
- Render the range with husk or the USD Render ROP.
Hair and fur checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Does Karma XPU render hair ribbons?
No. Karma XPU supports rounded curves only. Ribbons and oriented ribbons need Karma CPU.
2. Why do some hair curves disappear in Karma?
Each curve basis needs a minimum number of vertices per strand. Invalid topology can make curves disappear or render strangely.
3. What is the Houdini Hair Procedural?
A LOP that generates or deforms hair at render time from guides, so you store guides instead of every render curve.
4. How do I reduce noise in fur with Karma?
SideFX recommends Path Traced convergence with Karma XPU; relying on many secondary samples gets very expensive for fur.
5. How do I lower hair memory on Karma XPU?
Reduce curve density and attributes, and try KARMA_XPU_OPTIX_CURVE_OPT_LEVEL=1, which favours lower memory.
6. Do four GPUs share the memory of one groom?
No. Karma XPU memory is not pooled; every GPU holds all rendered curves.
7. Does Houdini 21 support displacement on curves in Karma?
Yes. When a displacement shader is applied to curves, Karma displaces the curve vertices, similar to point meshes.
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: Geometry, Karma XPU, Houdini Procedural: Hair LOP, What’s new in Houdini 21: Karma, husk licenses (SideFX FAQ). 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).


