November 19, 2026 Linh Nguyen

Maya and Redshift Pre-Flight Checklist: 10 Checks Before You Render on Another Machine

Pre-flight10 checks before a Maya + Redshift render elsewhere
From Autodesk and Maxon documentation

Most failed Maya renders on a new machine come from files, versions or plugins, not from the GPU. Check these first:

  • Project: set a Maya project so textures and caches use relative paths
  • Paths: no red X in the File Path Editor; no C:\Users\… paths
  • Package: Archive Scene, or copy the whole project folder
  • Versions: same Maya version, and a Redshift build that supports it
  • Plugins: redshift4maya and third-party plugins installed, loaded and licensed

A Maya scene is not one file. Textures, caches, references, plugins and the renderer all live outside the .mb or .ma, and each of them has to be found again when the scene opens on a render server. When one is missing, Redshift often renders anyway, which is why a broken texture or an unloaded rig can reach the final frames.

This checklist covers the ten things to check before a Maya and Redshift scene leaves your workstation: the project and paths, packaging, versions, the plugin and license, third-party plugins, render layers and cameras, caches, and GPU memory. Each check links to the Autodesk or Maxon page it comes from.

Checked against Autodesk Maya documentation (projects, File Path Editor, Archive Scene, command-line rendering) and Maxon Redshift for Maya documentation, November 2026.

1. Why do Maya scenes break on another machine?

Maya projects exist for exactly this reason. Setting a project creates a folder structure with scenes, sourceimages and other subfolders, and a workspace.mel file that holds the file rules; Autodesk notes that projects are useful when you work with a team or over several computers because the scene’s assets are organized in one location (Autodesk: Set a Project).

iRender
What a Maya Scene Needs on Another Machine
Schematic
shot010.mbsaved in Maya 2026Texturessourceimages\wood.exr ✓ relativeTexturesC:\Users\me\Desktop\hdr.exr ✗Cachescache\alembic\char.abc ✓Referencesscenes\rig_v12.mb (loaded?)PluginsYeti, Ornatrix, Golaem…RendererRedshift build + licenseGreen: found through the project on any machine · red: tied to one computer · amber: must exist on the render machine too
relative to projectabsolute pathinstall / load on render machine
Schematic · based on Autodesk project and File Path Editor docs

The figure shows the three kinds of dependency. Textures and caches stored inside the project are found on any machine through relative paths such as sourceimages\wood.exr. A file loaded from outside the project keeps an absolute path, like C:\Users\me\Desktop\hdr.exr, and breaks as soon as the scene moves. References, plugins and the renderer are not files you can package; they have to be installed and loaded on the render machine itself.

2. The 10-point pre-flight checklist (step by step)

Settings checklist (copy or follow line by line):

Settings checklist
File › Set Project
Project → set before working; textures in sourceimages, caches in cache
Paths → relative (sourceimages\…), not C:\Users\…
Windows › General Editors › File Path Editor
Red X → none left; Repath Files for broken ones
File › Archive Scene
Package → zip of the scene and its dependencies (or copy the whole project)
Render machine
Maya → same version as the scene
Redshift → build that lists that Maya version
redshift4maya.mll → Loaded + Auto load
License → Redshift license active on this machine
Plugins → installed and licensed (Yeti, Ornatrix, Golaem…)
Check → heaviest frame in the Redshift Render View, then a batch frame

1. Set the project

Use File › Set Project before you work on a scene. Maya then looks for textures in the project’s sourceimages folder first, and a texture loaded from there is stored with a relative path; one loaded from outside the file path rules becomes an absolute path (Autodesk: Set a Project).

iRender
Relative and absolute paths when a Maya scene moves
Schematic
Your workstationRender machinesourceimages\wood.exrrelative to the projectproject\sourceimages\wood.exrfound: the project travels with itC:\Users\me\Desktop\hdr.exrabsolute, outside the projectsame path does not existmissing texture in the renderFix before upload:File › Set Project → keep files in sourceimages → File Path Editor › Repath FilesFile › Archive Scene can also zip the scene with its dependenciesKeep every file inside the project, and repath anything that points outside itAutodesk: Set a Project; File Path Editor; Archive a scene
Resolves on any machineBreaks when the scene moves
Schematic, not to scale

2. Resolve every path

Open Windows › General Editors › File Path Editor. Missing files show a red X; select them and use Repath Files (Autodesk: File Path Editor). The editor lists references, textures, audio and image planes in one place.

3. Package the scene

File › Archive Scene puts the scene and its dependencies into a zip next to the file; its options can also include files of unloaded references (Autodesk: Archive a scene). Copying the whole project folder works too, as long as the paths are relative.

iRender
List missing and absolute texture paths
python
1# run in Maya: Windows > General Editors > Script Editor, Python tab
2import os
3import maya.cmds as cmds
4
5for node in cmds.ls(type="file"):
6 path = cmds.getAttr(node + ".fileTextureName")
7 if not path or "<UDIM>" in path or "<udim>" in path:
8 continue # UDIM sets: check the tiles in the File Path Editor
9 full = cmds.workspace(expandName=path) # resolves project-relative paths
10 if os.path.isabs(path):
11 print("ABSOLUTE ", node, path)
12 if not os.path.exists(full):
13 print("MISSING ", node, full)
14print("Project:", cmds.workspace(query=True, rootDirectory=True))
Absolute paths will break on another machineAutodesk: Maya projects and relative paths

4. Match the Maya version

Open the scene in the same Maya version it was saved in.

5. Match the Redshift build

Install a Redshift build that lists that Maya version on Maxon’s compatibility chart (Maxon: Redshift Compatibility Chart), ideally the same build you used for look-dev.

6. Load the plugin

In the Plug-in Manager, redshift4maya.mll must be Loaded and set to Auto load; the Redshift menu appears when it is (Maxon: Getting Started with Maya).

7. License Redshift on that machine

Maxon licenses Redshift GPU per machine; extra machines need their own license (Maxon: Redshift licenses).

8. Install third-party plugins

Yeti, Ornatrix, Golaem and similar plugins have to be installed and licensed on the render machine, in versions that match the scene.

9. Check layers, cameras and caches

Make sure the right render layers and camera are renderable; the command-line renderer can also set them with -rl and -cam (Autodesk: command-line flags). Caches (Alembic, nCache, simulation and groom caches) must cover the whole frame range and sit inside the project.

10. Check GPU memory on the heaviest frame

Render the heaviest frame and read the Redshift log or Feedback Display for out-of-core transfers (Maxon: Redshift Log Files); see our Redshift out-of-core guide.

3. What each missed check looks like in the render

TroubleshootSymptom to check

Which check catches which problem

Based on Autodesk and Maxon documentation

Symptom in the framesMissed checkFix
Pink, black or default-grey texturesAbsolute or unresolved paths (1–3)Set the project and repath in the File Path Editor
Scene will not open, or nodes missingDifferent Maya version or missing plugin (4, 8)Install the scene’s Maya version and plugins
No Redshift renderer, or the Redshift menu is missingPlugin not loaded (6)Load redshift4maya.mll and set Auto load
Watermark or failed renderNo Redshift license on that machine (7)Sign in or point to your license server
Wrong camera or a layer missingLayers and cameras not checked (9)Set renderable camera and layers, or use -cam / -rl
Hair, crowd or simulation missing on some framesCaches incomplete or outside the project (9)Cache the full range into the project folder
Frames much slower than the testScene out of core on the heaviest frame (10)Reduce memory or use 32 GB GPUs

The fastest way to catch most of these is to open the scene on the render machine, look at the File Path Editor and the Plug-in Manager, and render one heavy frame before the batch. After the batch, check the output with our Maya sequence QA guide.

4. Testing on the render machine before the full batch

Two short tests catch the remaining problems. First, render the heaviest frame interactively in the Redshift Render View and compare it with your workstation render. Second, run one frame through the command-line renderer, because a batch render reads the saved file and the render settings as stored, not what is open in the interface. Our Redshift for Maya on multi-GPU servers guide covers the Render -r redshift command, GPU selection and logs.

5. SaaS or IaaS render farm for Maya and Redshift scenes?

CompareNeutral guide

Which farm type fits a Maya scene

Both farm types render Maya with Redshift; the difference is who prepares the machine.

SituationUsually a better fitWhy
Standard Maya and Redshift versions, packaged projectSaaSUpload the archive and collect frames
Specific Maya version, Yeti, Ornatrix or GolaemIaaSYou install exactly the versions and plugins the scene needs
Scene still fails a check on another machineIaaSYou open the scene on the render machine and fix it there
Studio pipeline with its own submit toolsEitherPick the farm that supports your submit workflow

Rule of thumb: if every check passes with standard software, a submit-and-collect farm is simple; if the scene depends on particular versions or plugins, a machine you control avoids surprises.

Running the pre-flight 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 the checks above run exactly as on your workstation:

  1. Upload the project folder or the Archive Scene zip 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 your plugins once; they stay in your server image.
  3. Set the project, check the File Path Editor and the Plug-in Manager, and render the heaviest frame.
  4. Run the batch, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.

Maya + Redshift pre-flight checklist

Tick each item on the render machine before the batch starts.

ChecklistMaya + Redshift pre-flight 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 are my textures pink or missing on the render machine?

The scene points to files that do not exist there, usually through absolute paths such as C:\Users\…. Set the project, keep textures in sourceimages, and repath broken files in the File Path Editor.

2. How do I find missing files in a Maya scene?

Open Windows › General Editors › File Path Editor. Missing files have a red X; select them and use Repath Files. The script in this guide also lists missing and absolute texture paths.

3. What is the easiest way to send a Maya scene with all its files?

Use File › Archive Scene, which packages the scene and its dependencies into a zip next to the file, or copy the whole project folder when all paths are relative.

4. Do I need the same Maya version on the render machine?

Yes. Open the scene in the Maya version it was saved in, and install a Redshift build that lists that Maya version on Maxon’s compatibility chart.

5. Why is the Redshift renderer missing in Maya?

The redshift4maya.mll plugin is not loaded. Load it in the Plug-in Manager and set it to Auto load; the Redshift menu then appears in the main toolbar.

6. Will Redshift be licensed on the render machine?

Only if a license is active on that machine: Maxon licenses Redshift per machine, so render one frame there before the batch. On iRender, Prime accounts get Redshift licenses pre-activated on every server; otherwise sign in with your own Maxon license on each server.

7. How do I make sure the right camera and layers render in a batch?

Check renderable cameras and Render Setup layers before saving, or set them on the command line with -cam and -rl when you call Render.exe.

8. Can I run these checks on an iRender server?

Yes. iRender servers are full Windows machines with 1, 2, 4 or 8 RTX 5090 or RTX 4090 GPUs; you install Maya, Redshift and your plugins once and run the same checks 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:
, , , , , , ,

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
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →