Golaem Crowds with Redshift for Maya: Files, Procedurals and Render Machine Setup
A crowd renders only when the files, the plugin and the scene agree. Check these first:
- Procedural: Golaem builds crowd geometry at render time through a plugin per renderer
- Files: .gcha and .gcg for characters, .gscs and .gscf for the simulation, .gscl for layout
- Shaders: come from the Maya scene and must sit on non-hidden geometry
- Render machine: must load the Golaem Maya plugin and the Redshift procedural
- Check: CrowdRender › Check Render Settings, and fix any line that shows NO
Crowd shots look light in the viewport and heavy at render time. Golaem keeps thousands of characters out of the Maya scene and builds them only when Redshift asks for them, which is why a crowd can render perfectly on one machine and be missing entirely on another.
This guide explains how Golaem renders with Redshift in Maya, which files the render needs, how the Golaem module points Redshift to the right procedural, how to check a render machine before a batch, and how to fix missing crowds, grey characters and missing motion blur.
Checked against Autodesk Golaem for Maya documentation (Rendering Workflow, Rendering FAQ, Rendering Plugins Installation, Render Farm Deployment), November 2026.
1. How Golaem renders a crowd with Redshift
Golaem renders through procedural plugins, one per supported renderer, that load a simulation cache and generate the geometry on demand (Autodesk Golaem: Rendering FAQ). In Maya, a Crowd Render Proxy node reads files written by the Character Maker, Simulation Exporter and Simulation Layout: .gcha and .gcg for characters, one .gscs per simulation, one .gscf per frame, .gscl for layout edits and an .fbx or .gtg terrain. Shaders are read from the Maya scene, not from the geometry file, and must be applied to geometry that is not hidden (Autodesk Golaem: Rendering Workflow).
The diagram shows why a crowd can disappear without an error: the scene file itself holds only the proxy. If the plugin is not loaded or a path does not resolve, Redshift has nothing to render for the crowd and renders the rest of the frame.
2. Pointing Redshift to the Golaem procedural
Golaem installs rendering plugins in per-version folders. To use another Redshift build, Autodesk documents editing the module file lines for Redshift with the matching version folder (Autodesk Golaem: Rendering Plugins Installation):
When the module is loaded, it sets the variables each renderer needs to find the Golaem procedurals; when rendering outside Maya, such as from the renderer’s command line, Autodesk notes you must set those variables yourself (Autodesk Golaem). A classic installation needs no extra variables apart from a network license variable when one is used (Autodesk Golaem: Environment Variables).
3. How to prepare a Golaem scene for another machine (step by step)
Autodesk states that every render node must be able to load the Golaem Maya plugin and the renderer-specific procedural (Autodesk Golaem: Render Farm Deployment). The script below counts per-frame cache files against the shot range before you copy the project; Golaem cache names include the cache name and frame, so adjust the pattern if your naming differs.
Settings checklist (copy or follow line by line):
4. Missing crowds, grey characters and motion blur
Autodesk’s first check for a missing crowd is the CrowdRender menu in Rendering mode, then Check Render Settings; any line that shows NO must be fixed. For motion blur, the Crowd Render Proxy’s Auto Compute Motion Blur Parameters option matches the renderer’s settings, and it only works when motion blur is enabled in the renderer (Autodesk Golaem: Rendering FAQ). Deformation blur itself is explained in Alembic characters and deformation motion blur in Redshift for Maya.
When the crowd does not render as expected
Start from what is missing in the frame.
| What you see | Likely cause | What to change |
|---|---|---|
| No crowd at all, the rest of the scene renders | Golaem module or Redshift procedural not loaded on this machine | Install Golaem, check the .mod lines, run Check Render Settings |
| Crowd renders in Maya but not from the command line | Environment variables set by the module are missing outside Maya | Load the Golaem module for the batch, or set the variables yourself |
| Characters grey or with default shading | Shaders not in the scene or only on hidden geometry | Import the look-dev shaders and apply them to visible geometry |
| Parts of characters missing | Assets that belong together are split across asset groups | Keep assets that must appear together in one mesh asset |
| Crowd sharp while the rest of the frame blurs | Motion blur off on the proxy or in Redshift | Enable motion blur in Redshift and use Auto Compute Motion Blur Parameters |
| Some frames without crowd | Per-frame .gscf files missing for those frames | Re-export the cache for those frames and check the count |
Support has also moved: Golaem announced that from August 5, 2025 support for Autodesk Golaem is handled through Autodesk channels (Golaem: Rendering with Redshift), so check Autodesk’s Golaem pages for the Redshift versions your build supports.
5. SaaS or IaaS render farm for Golaem crowd shots?
Which farm type fits a Golaem crowd
Both can work only if Golaem and its Redshift procedural are installed on the render machine.
| Situation | Usually a better fit | Why |
|---|---|---|
| Farm already supports your Golaem and Redshift versions | SaaS | Upload the scene with its cache folders |
| Your Golaem version or module setup is specific | IaaS | You install Golaem and edit the .mod file on the render machine |
| Crowd still being laid out or re-exported | IaaS | Re-export caches and re-render on the same server |
| Studio pipeline with its own submit tools | Either | Pick the farm that supports your submit workflow |
Rule of thumb: a crowd renders only where Golaem loads; confirm that on the render machine before the batch.
Rendering a Golaem crowd on an iRender server
An iRender server is a full Windows machine with 32 GB RTX 5090 or 24 GB RTX 4090 GPUs:
- Upload the project with its character and cache folders to iRender Drive before you start a server; uploading is free and does not use rental time.
- Start a server, install your Maya version, the matching Redshift build and your Golaem version; they stay in your image.
- Open the scene, run CrowdRender › Check Render Settings and render the busiest frame.
- Render the full range, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.
Golaem crowd render checklist
Tick each item before you start the full range.
Frequently asked questions
1. How does Golaem render with Redshift?
Through a procedural plugin for Redshift. A Crowd Render Proxy in the Maya scene reads the exported character and simulation files, and the plugin generates the crowd geometry at render time.
2. Which files does a Golaem render need?
The Golaem Character File (.gcha), Character Geometry File (.gcg), one .gscs per simulation, one .gscf per frame, and the .gscl layout and terrain file when a layout is used.
3. Why does my Golaem crowd not appear in the render?
Usually the Golaem module or the Redshift procedural is not loaded, or a file path does not resolve. Open CrowdRender › Check Render Settings and fix any line that shows NO.
4. Why are my Golaem characters grey?
Shaders are read from the Maya scene, not from the geometry file. Import the look-dev shaders and apply them to geometry that is not hidden.
5. How do I use a different Redshift version with Golaem?
Edit the Redshift lines in the Golaem module file, REDSHIFT_PROCEDURALSPATH and REDSHIFT_MAYAEXTENSIONSPATH, to point to the version folder that matches your Redshift build.
6. How do I get motion blur on a Golaem crowd?
Enable motion blur in Redshift and use Auto Compute Motion Blur Parameters on the Crowd Render Proxy; the option only works when motion blur is on in the renderer.
7. Does a render machine need a Golaem license?
Golaem’s license documentation says production licenses are needed on artist workstations, not render nodes, and a render node can skip the license fetch with GLMCROWD_NO_LICENSE=1. Check Autodesk’s current Golaem licensing for your plan.
8. Can I render Golaem crowds with Redshift on iRender?
Yes. Golaem is not pre-installed; on a full Windows server you install your Maya, Redshift and Golaem versions once, upload the caches and check one frame before the full range.
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.
Sources: Autodesk Golaem: Rendering Workflow · Autodesk Golaem: Rendering FAQ · Autodesk Golaem: Rendering Plugins Installation · Autodesk Golaem: Render Farm Deployment · Autodesk Golaem: Environment Variables · Golaem: License Types · Golaem: Rendering with Redshift (support notice). Checked November 2026.



