November 11, 2026 Linh Nguyen

Golaem Crowds with Redshift for Maya: Files, Procedurals and Render Machine Setup

CrowdsRendering Golaem crowds with Redshift in Maya
From Autodesk Golaem documentation

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).

iRender
Golaem Crowd + Redshift: What the Render Needs
Schematic
1 · Files on diskCharacter Maker.gcha look, assets, shader names.gcg skinned geometrySimulation Exporter.gscs one per simulation.gscf one per frameSimulation Layout.gscl layout edits.fbx / .gtg terrain2 · Crowd Render Proxynode in the Maya sceneshaders from the scene,on non-hidden geometry3 · Golaem proceduralfor Redshiftbuilds geometry at render timeRedshift rendersOn the render machine: Golaem module + procedural loaded, and every file path above resolvesIf one is missing, the crowd does not appear in the render
cache and character filesshadersprocedural pluginrender machine check
Schematic · based on Autodesk Golaem docs

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):

iRender
Golaem module lines for Redshift
.mod
1# In the Golaem module (.mod) file: choose the Redshift procedural build
2# Replace XX with the folder name that matches your Redshift version
3REDSHIFT_PROCEDURALSPATH +:= procedurals/redshift/XX
4REDSHIFT_MAYAEXTENSIONSPATH +:= extensions/redshift/XX
Replace the paths, names and frame range with your ownAutodesk 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).

iRender
How Redshift finds the Golaem procedural
Schematic
A · Render from Maya (batch or Render View)Golaem module loadedwith the Maya pluginREDSHIFT_PROCEDURALSPATHREDSHIFT_MAYAEXTENSIONSPATHGolaem proceduralfound by RedshiftB · Render outside Maya (renderer command line)module not loadedvariables not setset the variables yourselfAutodesk Golaem Rendering FAQGolaem proceduralfound by RedshiftAnother Redshift build: edit these lines in the Golaem module file to the matching version folder.A crowd renders only where these paths point to the Golaem build that matches RedshiftAutodesk Golaem: Rendering FAQ; Rendering Plugins Installation
Set by the moduleSet by you
Schematic, not to scale

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.

iRender
Check the crowd cache before rendering
Python
1# Count Golaem per-frame cache files against the shot range
2# usage: python check_golaem_cache.py D:/Projects/crowd/cache stadium 1001 1240
3import glob, os, re, sys
4folder, name, start, end = sys.argv[1], sys.argv[2], int(sys.argv[3]), int(sys.argv[4])
5frames = set()
6for f in glob.glob(os.path.join(folder, name + "*.gscf")):
7 m = re.search(r"(\d+)\.gscf$", f)
8 if m:
9 frames.add(int(m.group(1)))
10missing = [f for f in range(start, end + 1) if f not in frames]
11print(".gscs files:", len(glob.glob(os.path.join(folder, name + "*.gscs"))))
12print("frames found:", len(frames), "missing:", missing[:20])
Replace the paths, names and frame range with your owniRender example script

Settings checklist (copy or follow line by line):

Settings checklist
Golaem install on the render machine
Golaem for Maya → same version as the workstation
Module (.mod) → loaded, Redshift procedural folder set
Redshift → version supported by that Golaem build
Files
.gcha / .gcg → character and geometry
.gscs / .gscf → one per simulation / one per frame
.gscl, terrain → if a layout is used
Paths → inside the project or via variables
Scene
Shaders → in the scene, on non-hidden geometry
CrowdRender › Check Render Settings → no line shows NO
Motion blur → on in Redshift and on the proxy

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.

TroubleshootGolaem + Redshift

When the crowd does not render as expected

Start from what is missing in the frame.

What you seeLikely causeWhat to change
No crowd at all, the rest of the scene rendersGolaem module or Redshift procedural not loaded on this machineInstall Golaem, check the .mod lines, run Check Render Settings
Crowd renders in Maya but not from the command lineEnvironment variables set by the module are missing outside MayaLoad the Golaem module for the batch, or set the variables yourself
Characters grey or with default shadingShaders not in the scene or only on hidden geometryImport the look-dev shaders and apply them to visible geometry
Parts of characters missingAssets that belong together are split across asset groupsKeep assets that must appear together in one mesh asset
Crowd sharp while the rest of the frame blursMotion blur off on the proxy or in RedshiftEnable motion blur in Redshift and use Auto Compute Motion Blur Parameters
Some frames without crowdPer-frame .gscf files missing for those framesRe-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?

CompareNeutral guide

Which farm type fits a Golaem crowd

Both can work only if Golaem and its Redshift procedural are installed on the render machine.

SituationUsually a better fitWhy
Farm already supports your Golaem and Redshift versionsSaaSUpload the scene with its cache folders
Your Golaem version or module setup is specificIaaSYou install Golaem and edit the .mod file on the render machine
Crowd still being laid out or re-exportedIaaSRe-export caches and re-render on the same server
Studio pipeline with its own submit toolsEitherPick 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

iRender
How iRender works: your computer controls your own multi-GPU server
IaaS render farm
Your PC or MacNo powerful GPU neededRemote desktopLive screen1:1 like your PCYOUR OWN GPU SERVERbare-metal · not sharedGPUGPUGPUGPUGPUGPUGPUGPU1, 2, 4 or 8 × RTX 5090 (32 GB) or RTX 4090 (24 GB)Threadripper PRO · 256 GB ECC RAM · 2 TB NVMe SSDFull admin access · your setup is saved between sessions1Register, top upFirst $50+ top-up doubled2Upload your projectiRender Drive, free3Start and connectRemote desktop, any OS4Render, shut downBilling stops, per minute✓ Your workstation, just more GPUs: no queue to wait, no farm plugin, no job submission, no settings changed
Your mouse and keyboardServer screen streamed back
Schematic, not to scale

An iRender server is a full Windows machine with 32 GB RTX 5090 or 24 GB RTX 4090 GPUs:

  1. 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.
  2. Start a server, install your Maya version, the matching Redshift build and your Golaem version; they stay in your image.
  3. Open the scene, run CrowdRender › Check Render Settings and render the busiest frame.
  4. 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.

ChecklistGolaem crowd 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. 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.

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:
, , , , , , ,

Linh Nguyen

Linh Nguyen works in customer support at iRender, helping artists render Blender and Houdini projects on multi-GPU servers. She has written more than 300 articles for the iRender blog, covering Blender, Houdini and practical GPU rendering.
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
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →