Houdini 22 on a Render Farm: Versions, Drivers and Renderer Plugins
Houdini 22 changed the platform underneath: operating system, drivers, Python, OCIO. Match these on the render machine:
- OS: Houdini 22 requires Windows 11 on Windows
- Driver: SideFX recommends NVIDIA 580; avoid 590 and 595
- Build: same 22.0 build as your workstation
- Plugins: Redshift 2026.9+ or Octane 2026.5 for Houdini 22
- License: licence server (hserver/sesinetd) 20.0 or newer
Houdini 22 arrived in July 2026 with build 22.0.368 and moved to the VFX Reference Platform CY2026. For rendering that means more than new features: it changes the supported operating systems, the recommended NVIDIA driver, the OCIO library and the Python builds, and every third-party renderer needs a build made for it.
This guide lists what has to match on a render machine for a Houdini 22 project, which Redshift and Octane builds support Houdini 22, and the checks to run before the first full sequence.
Checked against the SideFX Houdini 22 system requirements, platform and licensing notes, Maxon Redshift release notes and Otoy Octane release posts, November 2026.
What changed under Houdini 22
SideFX states that Houdini 22.0 targets the CY2026 specification of the VFX Reference Platform. The platform notes list, among other changes, OpenColorIO 2.5.0, NumPy 2.3.2, Boost 1.88.0, separate Houdini Python 3.11 builds, and the end of Intel Mac builds. On Windows, Houdini 22 is supported on Windows 11; the Houdini 22 requirements list Windows 10 and earlier, and Windows Server, as not supported.
For NVIDIA GPUs, the requirements page recommends the 580 Production/Studio driver and says to avoid 590 and 595. Karma XPU itself needs driver 570 or later.
Sources: Houdini system requirements, Houdini 22 system requirements (Japanese edition), Houdini 22 platform notes, Karma XPU.
Each mismatch fails in its own way, and the colour one fails silently, so compare the two machines row by row before the first render.
The order to check things on a render machine
Work through the chain in order, because each step depends on the one before it. A missing Windows 11 or the wrong driver shows up as a crash at start-up; a plugin built for another Houdini build shows up as missing nodes; a different OCIO config shows up as different colours with no error at all. The licence server must be recent enough too: SideFX lists hserver/sesinetd 20.0 as the minimum for Houdini 22.
Sources: Houdini 22 licensing notes, Houdini system requirements.
Renderer plugins for Houdini 22
Third-party renderers are built against specific Houdini builds, and each release adds new builds and drops old ones.
Houdini 22 and the renderers that support it
From SideFX, Maxon and Otoy release notes; check the latest notes before installing.
| Component | Houdini 22 support | Note |
|---|---|---|
| Houdini 22.0 | 22.0.368 production build released July 2026 | VFX Reference Platform CY2026; OpenColorIO 2.5.0 |
| Karma XPU | Ships with Houdini | NVIDIA driver 570+ for XPU; SideFX recommends 580 for Houdini 22 |
| Redshift | 2026.9: 22.0.368 · 2027.0.1: 22.0.429 | Each release lists exact builds and drops older ones |
| Octane | 2026.5: 22.0.368 and 22.0.429 | Installed as a Houdini package |
| Python | Main builds per CY2026; separate Python 3.11 builds | Pick the variant your scripts and plugins need |
Maxon added Houdini 22.0.368 and Solaris 22.0.368 support in Redshift 2026.9, with a USD 26.05 build for Houdini 22’s USD Procedural workflow, and added 22.0.429 in Redshift 2027.0.1. Otoy’s OctaneRender 2026.5 for Houdini supports 22.0.368 and 22.0.429 on Windows and Linux. If your workstation runs one of these builds, install the same Houdini build on the render machine rather than the newest one. Details for each renderer are in our guides to Redshift for Houdini and Octane for Houdini.
Sources: Maxon: Redshift 2026.9 / 2027.0 release notes, Otoy: OctaneRender 2026.5 for Houdini.
Karma, colour and the first frame on Houdini 22
- Kernel cache: the Karma XPU kernel cache is stored per major Houdini release, so the first Houdini 22 render on a machine compiles kernels even if Houdini 21 was used there before. See why the first Karma XPU frame is slow.
- Colour: Houdini 22 ships OCIO config 3.0 for ACES and the OpenColorIO 2.5.0 library; ship your own config with the project if you use one. See OCIO and ACES in Houdini 22.
- New husk options: Houdini 22 adds
--enable-usd-errors,--error-summary,--karma-percent-of-samplesand--pass; a render machine on an older build will not recognise them. See our husk guide. - Memory: Karma XPU in Houdini 22 uses up to half the memory for subdivided and diced meshes, so a shot that did not fit on Houdini 21 may fit now.
Sources: Pre-compile Karma XPU render kernels, Color management in Houdini, What’s new in Houdini 22: Karma.
SaaS or IaaS render farm for Houdini 22 projects?
Which farm type fits a Houdini 22 project
Both can run Houdini 22; they differ in who picks the builds.
| Situation | Usually a better fit | Why |
|---|---|---|
| Farm already runs your Houdini 22 build and renderer build | SaaS (managed farm) | Submit and render |
| You need a specific 22.0 build or renderer release | IaaS (remote workstation) | Install exactly the builds you tested |
| Studio OCIO config or Python 3.11 variant | IaaS | You choose the variant and config on the machine |
| Mixed Karma, Redshift and Octane in one project | IaaS | All three installed side by side with matching builds |
| Short job on standard builds | SaaS | No setup time |
Rule of thumb: if a managed farm already runs your exact builds, it is the least work. Otherwise a machine you control lets you match every version yourself.
Running a Houdini 22 project on an iRender server
On iRender you rent a whole workstation and install the software yourself, so the versions are the ones you choose:
- Choose a Windows 11 server for Houdini 22 (iRender offers both Windows 10 and Windows 11) and check that the NVIDIA driver is the version you use.
- Install the same Houdini 22 build as your workstation and sign in with your own SideFX license.
- Install the renderer builds made for that Houdini build (Redshift 2026.9+, Octane 2026.5) and sign in with your own licenses.
- Copy your OCIO config with the project and check the working space in the OCIO Editor.
- Render one test frame per renderer, then render the range.
Houdini 22 render machine checklist
Use this as a final check before you start the full range on any machine.
Frequently asked questions
1. Does Houdini 22 run on Windows 10?
No. The Houdini 22 system requirements list Windows 11 as supported and Windows 10 and earlier as not supported.
2. Which NVIDIA driver should I use for Houdini 22?
SideFX recommends the 580 Production/Studio driver and says to avoid 590 and 595. Karma XPU needs 570 or later.
3. Which Redshift version supports Houdini 22?
Redshift 2026.9 added Houdini 22.0.368; Redshift 2027.0.1 added 22.0.429.
4. Does Octane support Houdini 22?
Yes. OctaneRender 2026.5 for Houdini supports 22.0.368 and 22.0.429.
5. Which Python does Houdini 22 use?
The main builds follow the VFX Reference Platform CY2026; SideFX also offers separate Python 3.11 builds.
6. Why does Karma XPU compile kernels again after upgrading to Houdini 22?
The kernel cache is stored per major Houdini release, so Houdini 22 builds its own cache on first use.
7. Do Houdini 21 kernel caches work in Houdini 22?
No. The Karma XPU kernel cache is stored per major Houdini release, so Houdini 22 builds its own on first use.
8. Which licence server version does Houdini 22 need?
SideFX lists hserver/sesinetd 20.0 as the minimum for Houdini 22.
Render your Houdini 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: Houdini system requirements, Houdini 22 system requirements (Japanese edition), Houdini 22 platform notes, Houdini 22 licensing notes, What’s new in Houdini 22: Karma, Redshift 2026.9 / 2027.0 release notes, OctaneRender 2026.5 for Houdini, CG Channel: SideFX releases Houdini 22. 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).


