November 16, 2026 Kath Nguyen

XGen and Yeti Hair with Redshift for Maya: Batch Patches, Caches and Min Pixel Width

Hair & furMaya hair that renders the same in every batch
From Autodesk, Maxon and Peregrine Labs documentation

Hair that looks right in the Render View can still disappear in a batch render. Check these before a hair shot:

  • XGen batch: export patches with Export Patches for Batch Render and keep them in the project
  • Materials: Redshift uses the patch material, or the description’s if the patch has none
  • Yeti: write a .fur cache for the shot range with pgYetiCommand -writeCache
  • Thin hair: Hair Min Pixel Width reduces shimmer; the automatic threshold is recommended
  • Smoothness: Hair Tessellation smooths curves without more VRAM, at a time cost

Hair is the most common reason a Maya render looks right on the workstation and wrong on a render machine. The groom is evaluated live in the interface, but a batch render reads hair from exported patch or cache files. If those files were never written, or were left behind, the frames come back with a bald character.

This guide covers XGen and Yeti hair with Redshift for Maya: how batch rendering reads hair, how to export and cache it step by step, how Redshift shades XGen, and how Hair Min Pixel Width and hair tessellation affect quality and render time. Our Redshift hair and instancing guide covers grooming plugins more broadly.

Checked against Autodesk’s XGen rendering page, Maxon’s Redshift for Maya XGen Rendering and Hair Min Pixel Width pages, and Peregrine Labs’ Yeti cache documentation, November 2026.

1. Why does XGen hair disappear in batch renders?

XGen hair in a batch render comes from patch files, not from the live groom. Autodesk’s steps for rendering XGen primitives set the Render Mode to Batch Render and then export the patches with File › Export Patches for Batch Render in the XGen window (Autodesk: Render XGen primitives). Maxon’s Redshift for Maya XGen page covers the same export (Maxon: XGen Rendering).

iRender
Why XGen Hair Renders in the Render View but Not in a Batch
Schematic
Interactive (Render View on your workstation)XGen descriptiongroom in the sceneMaya evaluatessplines on the flyHair renderslooks rightBatch (Render.exe on any machine)XGen descriptionsame sceneExported patchesExport Patches for Batch RenderHair renderspatch files foundPatches not exportedor not copiedBald characterbatch frames miss hair
XGen in the sceneexported patchesmissing step
Schematic · based on Autodesk XGen and Maxon XGen Rendering docs

The figure shows the two paths. In the interactive path Maya evaluates the description and the hair renders. In the batch path the renderer looks for the exported patches; if they are missing, out of date or outside the project, the batch frames have no hair even though every test in the Render View looked fine. Re-export after any change to the groom or the animation it follows.

2. How to set up XGen hair for Redshift batch renders (step by step)

Settings checklist (copy or follow line by line):

Settings checklist
XGen window › File
Export Patches for Batch Render → run after the final groom / animation change
Patch files → inside the project, copied to the render machine
XGen › Preview/Output › Output Settings
Renderer / Operation → Redshift / Render
Render Mode → Batch Render
Primitive Bound → 1 or more; higher for long hair
Shading
Material → on the patch, or on the description as fallback
Redshift Render Settings › Globals › Hair
Min Pixel Width → On for thin hair; automatic threshold
Hair Tessellation → smoother curves; no extra VRAM, more time
Check → a batch frame with the closest hair, then a few frames in motion

Step 1: Set the output settings

In the XGen Preview/Output tab, set the renderer and operation, set Render Mode to Batch Render, and set Primitive Bound to 1 or more; Autodesk notes to raise it for long primitives (Autodesk: Render XGen primitives).

Step 2: Export the patches

Use File › Export Patches for Batch Render and keep the exported files inside the project so they travel with the scene.

Step 3: Assign materials

Redshift uses the material assigned to the XGen patch; if the patch has none, it uses the material of the parent description (Maxon: XGen Rendering).

Step 4: Turn on Min Pixel Width for thin hair

Enable Hair Min Pixel Width in the Redshift render settings and keep the automatic threshold, which Maxon recommends (Maxon: Hair Min Pixel Width).

Step 5: Test a batch frame

Render the frame with the closest hair through Render.exe, not only in the Render View, so you test the same path the final frames use.

3. Yeti caches for consistent batch frames

Yeti grooms can render live, but a cache makes every machine read the same fur. Peregrine Labs documents caching a graph with pgYetiCommand -writeCache, using C-style frame padding such as %04d and an optional <NAME> token for the node name (Peregrine Labs: Working with caches).

iRender
Write a Yeti cache for the shot range
mel
1// MEL: cache a Yeti groom for frames 1-120 into the project's cache folder
2// <NAME> adds the Yeti node name, %04d the 4-digit frame number
3pgYetiCommand -writeCache "D:/proj/cache/yeti/hero_<NAME>.%04d.fur" -range 1 120;
Point the Yeti node to the cache files before batch renderingPeregrine Labs: Working with caches

After caching, point the Yeti node at the cache files and keep them in the project. Yeti also has to be installed on the render machine with its renderer extension configured; Peregrine Labs lists the environment settings per renderer (Peregrine Labs: Renderer extension configuration). Install the same Yeti version the groom was made with.

4. Hair quality, memory and render time in Redshift

Thin hair aliases because it is easily missed by camera rays, which shows as moiré or noise-like artifacts (Maxon: Hair Min Pixel Width). Min Pixel Width widens strands that are thinner than a pixel and makes them semi-transparent, so more samples hit them.

iRender
Hair Min Pixel Width: Why Thin Hair Shimmers
Schematic
Min Pixel Width offa strand thinner than a pixelis missed by most camera samplesMin Pixel Width onstrand widened and madesemi-transparent: most samples hit itResult in motion:off: shimmer / moiré on thin hairon: smoother with fewer samplesCost: semi-transparency addswork; Maxon notes it can stillsave time overall· = camera sample
hair strandcamera sample
Schematic · based on Maxon Hair Min Pixel Width docs

Maxon notes the semi-transparency can increase render time, but because hair then renders smoothly with fewer unified samples, it can still save time overall (Maxon: Hair Min Pixel Width). Hair Tessellation, in the Globals tab, improves the smoothness of hair at render time without more VRAM but can increase render times (Maxon: Globals, Hair). Dense grooms still take memory: check the heaviest hair frame in the Redshift log, and see our out-of-core guide if it spills to system RAM.

TroubleshootSymptom to fix

When hair renders wrong in Maya + Redshift

Based on Autodesk, Maxon and Peregrine Labs docs

SymptomLikely causeFix
Bald character in batch framesXGen patches not exported, out of date or not copiedExport Patches for Batch Render again; keep files in the project
Hair renders grey or with the wrong materialNo material on the patch or descriptionAssign the material to the patch or the description
Fur missing on some machinesYeti not installed or cache not foundInstall the same Yeti version; cache with -writeCache and keep caches in the project
Shimmer or moiré on thin hairStrands thinner than a pixelEnable Hair Min Pixel Width with the automatic threshold
Hair looks faceted close upToo few curve segments at render timeEnable Hair Tessellation
Hair frames much slower than testsGroom pushes the scene out of coreCheck the log; reduce density or use 32 GB GPUs

Test a few consecutive frames in motion: shimmer and popping strands only show between frames.

5. SaaS or IaaS render farm for Maya hair shots?

CompareNeutral guide

Which farm type fits a hair shot

Both farm types can render XGen and Yeti with Redshift; the difference is control over plugins and caches.

SituationUsually a better fitWhy
XGen with exported patches, standard MayaSaaSPatches and scene upload together; the farm renders them
Yeti or Ornatrix with a specific plugin versionIaaSYou install the exact version and its renderer configuration yourself
Groom still being adjusted between rendersIaaSYou re-export or re-cache on the render machine and test right away
Studio pipeline with its own submit toolsEitherPick the farm that supports your submit workflow

Rule of thumb: hair shots depend on plugins and cache files more than on the GPU; use the setup where you can control both.

Rendering a Maya hair shot on an iRender server

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.mb1 GPUYour iRender serverscene.mbup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found

An iRender server is a full Windows machine, so XGen, Yeti and Redshift are set up as on your workstation:

  1. Upload the project with exported XGen patches or Yeti caches to iRender Drive before you start a server; uploading is free and does not use rental time.
  2. Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs, install your Maya version, the matching Redshift build and Yeti or Ornatrix if needed; they stay in your image.
  3. Render the closest hair frame through Render.exe and a few frames in motion.
  4. Render the full range, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.

Maya hair render checklist

Tick each item before you start the full range.

ChecklistMaya hair render checklist
0 / 10 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 XGen hair render in the Render View but not in a batch?

Batch renders read XGen hair from exported patches. Use File › Export Patches for Batch Render in the XGen window, set Render Mode to Batch Render, and keep the patch files in the project.

2. Which material does Redshift use for XGen hair?

The material assigned to the XGen patch. If the patch has no material, Redshift uses the material assigned to the parent description.

3. How do I cache Yeti fur for a render farm?

Use pgYetiCommand -writeCache with a file path, C-style frame padding such as %04d and the frame range, then point the Yeti node at the cache files.

4. Why does thin hair shimmer in animation?

Strands thinner than a pixel are missed by most camera rays. Enable Hair Min Pixel Width with the automatic threshold; it widens and softens thin strands so they render smoothly.

5. Does Min Pixel Width make renders slower?

It adds semi-transparency, which can increase render time, but Maxon notes it lets hair render smoothly with fewer samples, so it can save time overall.

6. Does Hair Tessellation use more GPU memory?

Maxon describes it as improving hair smoothness at render time without requiring more VRAM, but it can increase render times. When memory goes to repeated objects rather than hair, see MASH instancing and Redshift Proxies in Maya.

7. Do Yeti and Ornatrix need to be installed on the render machine?

Yes. Install the same plugin version the groom was made with, with its renderer configuration, and make sure the caches are in the project.

8. Can I render Maya hair shots on a multi-GPU iRender server?

Yes. iRender servers have 1, 2, 4 or 8 RTX 5090 or RTX 4090 GPUs with full administrator access, so you install Maya, Redshift and your hair plugins once and render as on your workstation.

Render your Maya and Redshift projects on iRender

iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or 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. Your server image is saved between sessions, so your plugins and settings stay installed. Maya is not pre-installed: you install the Maya version your scene uses with your own Autodesk license, and it stays in your image. Prime accounts get Redshift licenses pre-activated on every server.

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 and 8-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 quick start shows how to start a server and connect to it:

A full Maya and Redshift session we recorded on an 8x RTX 4090 server:

New users get a 100% bonus on the first top-up (minimum $50). See plans on the Maya render farm for Redshift page or download the iRender GPU app.

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

Kath Nguyen

Kath Nguyen works in customer support at iRender, helping artists move Blender and Cinema 4D projects to multi-GPU servers. She has written more than 140 articles for the iRender blog.
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
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →