Moving a Solaris and Karma XPU Scene to a Render Server in 2026: Save Paths, Relative References, Flattening and husk
A Solaris scene renders on another machine when every layer, cache and texture it references can be found there. Give layers save paths under $HIP, let the USD ROP write relative references, keep everything in one project folder, then render with husk or the USD Render ROP.
- Save paths: set them as absolute paths with $HIP; the default output processor turns them into relative references.
- Textures: only attributes of type asset are converted; string paths stay absolute.
- Flattening: flatten layers, not the whole stage, or the file becomes enormous.
- husk: renders a saved USD file from the command line with frame range, settings and output options.
A Solaris scene is a set of USD layers that point to other layers, caches and textures by file path. It renders on another machine only when every one of those paths can be found there. The fix is a consistent layout: layers with save paths under $HIP, relative references written by the USD ROP, and one project folder that moves as a unit.
This guide covers how save paths and output processors work, which texture paths need care, when to flatten, and how to render the saved USD with husk. For moving large caches, see our guide to uploading Houdini caches to a render farm.
Checked against the SideFX documentation for Writing out USD and husk, and SideFX staff answers on the Solaris forum, November 2026.
1. Why does a Solaris scene break on another machine?
Because USD files reference other files by path. If a layer, payload or texture points to a folder that exists only on your workstation, the render server cannot find it, and geometry or textures go missing. Layers authored in LOPs without a save path are another cause: Houdini writes them as temporary files instead of files you control.
A SideFX forum user summed up the second problem when helping another artist: most of their own issues came from not setting save paths on the layers authored inside Solaris (forum topic 78476).
2. How do save paths and relative references work in Solaris?
The USD ROP’s Output file sets the top-level file, and every layer with a save path is written to its own file. SideFX recommends absolute save paths, often using $HIP. During the save, the default output processor turns them into relative references between the layer files, so you can move all of them together to another location.
SideFX staff add one rule that explains most broken paths: a relative path in a USD file is always relative to the folder containing the USD file that does the referencing (forum topic 76401). For textures, the USD ROP converts paths only when the attribute or primvar has the data type asset, not string (forum topic 84246).
What to check so a Solaris scene moves cleanly
Each kind of file the stage references, and how to keep its path working on another machine.
| Data | Where the path is set | How to keep it portable |
|---|---|---|
| Authored LOP layers | Configure Layer LOP, SOP Import, SOP Create | Set a save path under $HIP |
| Top-level USD | USD ROP Output file | Write it inside the project folder |
| References and sublayers | Reference and Sublayer LOPs | Let the output processor make them relative |
| Textures | Material and primvar attributes | Use asset-type attributes so the path is converted |
| Per-frame data | Files with $F in the name | Keep frame files beside the layer that uses them |
3. Should you flatten a Solaris scene before rendering it elsewhere?
Flatten layers, not the stage. A SideFX staff member explains that the USD Render ROP does the equivalent of flattening all layers, while flattening the whole stage pulls all referenced data into one file and makes it enormous (forum topic 74412). Keep large caches as separate referenced files, with relative paths, and upload them once.
Time-dependent data needs a decision too. With Flush Data After Each Frame on and $F in the file name, the USD ROP writes one file per frame; with it off, frames are combined in memory, which SideFX notes can use a lot of memory.
How to read the figure. The left side is the project on your workstation; the right side is the same folder on the server. As long as the structure is unchanged, every relative reference still resolves.
4. How do you render the saved USD with husk?
husk is SideFX’s command-line utility for rendering a USD file with Karma or another Hydra renderer. The basic form is husk [options] usd_file -o image_file. Use -f for the start frame, -n for the number of frames, -i for the increment, -s to pick a RenderSettings prim, and $F4 in the output name for four-digit frame numbers.
husk checklist (copy or follow line by line):
Step 1: Write the USD
On the USD ROP, set the Output file inside the project folder and keep the default relative-path output processor on. Check that every authored layer has a save path.
Step 2: Test the folder in a new location
Copy the project folder to a different path on your own machine and open the top-level USD there. Anything that breaks here will also break on the server.
Step 3: Upload and render one frame
Upload the whole folder with its structure, then render a single frame with husk. Check that geometry, textures and AOVs are all present.
Step 4: Render the range
Run husk with -f and -n for the full frame range and $F4 in the output name, or render from the USD Render ROP inside Houdini.
How to read the figure. The badges follow Steps 1 to 4 above. Badge 1 is the USD ROP output inside the project, with relative references. Badge 2 is the test copy of the project at a new path on your own machine. Badges 3 and 4 are the husk commands on the server: one frame first with -n 1, then the full range. Paths and frame numbers are examples.
How to read the figure. The figure shows the most common size mistake. Most problems come from a path that was absolute or pointed outside the project folder when the USD was written.
5. What changes when the render server is a whole machine you control?
On a machine you control, you can open the .hip file in Houdini, check the stage in Solaris and render from the USD Render ROP, exactly as on your workstation; husk becomes an option rather than the only route. The portability rules above still apply, because the files have moved to a new path.
A SaaS render farm renders submitted jobs with its own setup, which suits finished, self-contained scenes. An IaaS server is a whole machine you control: you install your Houdini build, use your own SideFX license, and fix a missing path yourself in the scene instead of resubmitting a job.
SaaS or IaaS render farm for a Solaris scene?
Both farm models can render a portable USD with husk. The difference is whether you can open the .hip or the top-level USD on the render machine and fix a broken reference there.
Rendering a Solaris and Karma XPU scene on a farm
How the two farm models fit depending on how portable the scene is.
| Your situation | SaaS render farm | IaaS render farm (iRender) |
|---|---|---|
| The USD uses relative paths and passed the copy test | A good fit: upload and the farm renders with husk | Works as well: upload the folder and render with husk |
| Some references may still point outside the project | Usually found in the job log after the render | Open the scene on the server and fix the path in place |
| You need your own Houdini build, packages or HDAs | Check that the farm supports each one | Install them yourself; they stay on your server between sessions |
A test workflow on an iRender server
How to read the figure. The left box is your own workstation and the right box is the iRender server: the same desktop, Houdini version, plugins, licenses and render settings. The only difference is the GPU count, from 1 to 8 RTX 5090 or RTX 4090, so the scene renders on the server the way it does at home.
- Upload the project folder, with its structure unchanged, to iRender Drive before you start the server; uploading is free and does not use rental time.
- Start a server with RTX 5090 (32 GB) GPUs; for Karma XPU we recommend 4x RTX 5090. Install your Houdini build and sign in with your own SideFX license.
- Open the scene or the top-level USD and render one frame with the USD Render ROP or husk; check geometry, textures and AOVs.
- Render the frame range, then shut down; billing is per minute.
Frequently asked questions
1. Why are my textures missing when I render a Solaris scene on another computer?
The texture path probably stayed absolute. The USD ROP converts paths to relative only when the attribute or primvar has the data type asset, not string. Check the attribute type and keep textures inside the project folder.
2. What does the USD ROP output processor do?
By default it turns the absolute save paths of your layers into relative references between the layer files, so you can move all the files together to another location.
3. Are relative paths in USD relative to the .hip file?
No. SideFX staff explain that a relative path in a USD file is always relative to the folder containing the USD file that does the referencing.
4. Should I flatten the stage before sending it to a render farm?
Usually not. Flattening the whole stage pulls all referenced data into one very large file. The USD Render ROP flattens layers instead, which keeps files smaller.
5. What is husk in Houdini?
husk is SideFX’s command-line utility for rendering a USD file with Karma or another Hydra renderer. It takes options for frame range, render settings and output path.
6. How do I render a frame range with husk?
Use -f for the start frame and -n for the number of frames, for example husk -f 1001 -n 120 -o render/shot.$F4.exr shot.usd. Add -i to render every second or third frame.
7. Can I render a Solaris scene on iRender?
Yes. Upload the project folder, rent a server with RTX 5090 GPUs, install your Houdini build with your own SideFX license, and render from the USD Render ROP or husk. Billing is per minute.
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.


