ACES 2.0 and OCIO in Maya 2026 with Redshift: Textures, Render Space and Output
Color mismatches usually come from three places. Check these before you send a scene out:
- Maya 2026: uses OpenColorIO only; the legacy SynColor system is no longer supported
- Redshift: follows the DCC color setup by default; renders in ACEScg
- View: the Maxon CG config uses ACES 2.0 as its default view transform
- Textures: color maps sRGB, HDR images linear, data maps Raw
- Output: linear EXR for comp; bake the view only into PNG or JPG
A Maya scene can look right on the workstation and wrong everywhere else: the render machine shows other colors, the EXR looks flat in compositing, or normal maps shade strangely. Almost every case comes back to color management: which OCIO config the scene uses, which color space each texture is read in, and whether the view transform is baked into the output.
This guide covers what changed in Maya 2026, how Redshift for Maya handles OCIO and ACES 2.0, which input space each kind of texture needs, how to save EXR and preview files correctly, and how to keep the same result on every machine that renders the scene.
Checked against Maxon’s Redshift for Maya Color Management page and Autodesk’s Maya 2026 documentation, November 2026.
1. What changed in Maya 2026 color management?
Autodesk updated OpenColorIO in Maya 2026 to OCIO 2.4.1 and dropped support for the legacy SynColor color management system (Autodesk: What’s New in Maya 2026); the 2026.1 update moved to OCIO 2.4.2 (Autodesk: Maya 2026.1). The OpenColorIO project lists 2.4.2 as the release where ACES 2.0 library support was finalized (OpenColorIO 2.5 release notes). Color management settings are stored in the scene file, and when the OCIO environment variable is set, the OCIO Config Path becomes read-only (Autodesk: Color Management preferences).
The diagram follows one frame: each texture is read in its own input space, Redshift renders in ACEScg, and the output is either linear EXR for compositing or a display-ready PNG or JPG for review. If any of the three steps uses another config on another machine, colors shift.
2. How Redshift for Maya uses OCIO and ACES 2.0
Maxon states that Redshift uses the DCC’s color management by default, and a custom config can be set in the OpenColorIO Configuration parameter or through the OCIO environment variable. Redshift ships two configs in its Data › OCIO folder: maxon-cg-v1.1_ocio-v2.4.ocio with ACES 1 and 2, more display spaces and wider file rules, and config.ocio with ACES 1 and an sRGB display only. The maxon-cg config uses ACES 2 as its default view transform, and ACEScg is the default render color space (Maxon: Color Management – OCIO ACES (Maya)).
The script prints the scene’s config path, rendering space and view transform, then lists file nodes whose names suggest data maps but whose color space is not Raw. Run it on the workstation and on the render machine; the first four lines should match exactly.
3. How to set up color for a Redshift scene in Maya (step by step)
Maxon’s guidance for textures is sRGB for color JPG, PNG and BMP images, a scene-linear space for EXR and HDR images such as dome backplates, and Raw for normal, roughness, metalness and displacement maps. OpenColorIO file rules can set these from file names, but Maxon notes they can be wrong, so check them (Maxon). The input spaces available depend on the config the scene uses (Autodesk: Input color spaces).
Settings checklist (copy or follow line by line):
4. Matching colors across machines and in compositing
For EXR output meant for compositing, Maxon says to save unclamped linear OpenEXR and turn off Color / Lut / Controls in Maya’s Post Effects settings for HDR file types; leaving it on bakes the ACES view transform into the file. LDR formats such as PNG and JPG take the view transform, which clamps highlights at 1.0. Maxon also says to use the same OCIO config through the whole pipeline, compositing included (Maxon). To split that output by layer and AOV, see Maya Render Setup layers with Redshift AOVs.
When colors do not match
Start from where the mismatch shows up.
| What you see | Likely cause | What to change |
|---|---|---|
| Render looks different on another machine | A different OCIO config or an OCIO environment variable on one machine | Point both machines to the same config file |
| Washed-out or too contrasty textures | Color texture set to Raw, or a data map set to sRGB | Set the File Color Space per map type |
| Bumpy or wrong-looking normals | Normal map converted as a color image | Set the normal map to Raw |
| EXR in comp looks tone-mapped and clipped | Color / Lut / Controls left on for HDR output | Turn it off and save linear EXR |
| Comp looks darker or flatter than the render view | Comp uses another view transform | Use the same config and view in comp |
| OCIO Config Path cannot be edited | The OCIO environment variable is set | Change or remove the variable, then restart Maya |
The same ideas apply in Cinema 4D; our guide to Redshift ACES and OCIO in Cinema 4D covers render space and view transforms there.
5. SaaS or IaaS render farm for ACES projects in Maya?
Which farm type fits an OCIO pipeline
Both farm types can render ACES scenes; the difference is who controls the config on the render machine.
| Situation | Usually a better fit | Why |
|---|---|---|
| Default Maya or Redshift config, no custom spaces | SaaS | Upload the scene and collect frames |
| Studio or custom OCIO config | IaaS | You copy the config and set the path on the render machine |
| OCIO environment variable required | IaaS | You set the variable on the server yourself |
| Studio pipeline with its own submit tools | Either | Pick the farm that supports your submit workflow |
Rule of thumb: colors match only when the config matches; render where you can confirm the config path.
Rendering an ACES Maya scene 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, including any custom OCIO config folder, to iRender Drive before you start a server; uploading is free and does not use rental time.
- Start a server, install your Maya version and the matching Redshift build once; they stay in your image. Setup details are in Redshift for Maya on a multi-GPU render server.
- Set the OCIO Config Path or the OCIO variable, run the check script and compare one frame with your workstation.
- Render the full range, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.
Maya color checklist
Tick each item before you start the full range.
Frequently asked questions
1. Does Maya 2026 still support SynColor?
No. Autodesk states that Maya 2026 updated OpenColorIO to 2.4.1 and that the legacy SynColor color management system is no longer supported.
2. Does Redshift use Maya’s color management?
By default, yes. Maxon states that Redshift uses the DCC’s color management setup, and you can override it with a custom config in the OpenColorIO Configuration parameter or the OCIO environment variable.
3. Which OCIO configs ship with Redshift?
Two: maxon-cg-v1.1_ocio-v2.4.ocio with ACES 1 and 2, extra display spaces and wider file rules, and config.ocio with ACES 1 and an sRGB display. Both are in the Data › OCIO folder.
4. What is the default view transform in Redshift?
With the maxon-cg config it is ACES 2.0 SDR-video. Maxon describes ACES 2 as giving softer contrast and better handling of extreme saturation and highlight clipping.
5. Which color space should textures use in Redshift for Maya?
sRGB for color PNG, JPG and BMP images; a scene-linear space for EXR and HDR images; Raw for normal, roughness, metalness and displacement maps.
6. Why does my EXR look tone-mapped in Nuke or After Effects?
The view transform was baked in. Turn off Color / Lut / Controls in Maya’s Post Effects settings for HDR file types and save linear EXR.
7. Why can I not change the OCIO Config Path in Maya?
When the OCIO environment variable is set, Maya makes the OCIO Config Path read-only. Change or remove the variable and restart Maya.
8. Can I render ACES scenes with Redshift on iRender?
Yes. An iRender server is a full Windows machine, so you can copy your OCIO config, set the config path or variable, and compare a test 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.



