Octo for Maya
Octo can write, test and run the routines that process Maya scenes without opening the interface: mayapy, maya -batch and Render. Maya runs natively on Linux; for Maya 2026, Autodesk lists support only for RHEL (Red Hat Enterprise Linux) and Rocky Linux, versions 8.10, 9.3 and 9.5. You approve the plan and each batch; it prepares the script and, after running, returns the result and the report of what failed for review.
Six possible deliverables, drawn from the research. In all of them, Octo proposes the approach, writes the script and tests it on a sample before the batch.
Writes a script for mayapy, the Python that ships with Maya: initializes Maya without the interface, opens each scene, lists the meshes with vertices, faces and position, and writes a JSON. Releases the license at the end, even on error, and exits with a nonzero code so the batch knows what failed.
Uses maya -batch (mayabatch.exe on Windows) to run MEL (Maya Embedded Language, Maya's scripting language) when the scene opens: delete construction history and save, or source a legacy MEL file. When it needs Python there, it uses the python("...") wrapper. Since it overwrites, it only runs after the backup.
Renders a frame range through Render, which is the rendering path (maya -batch is not), with an output folder and a log per range. Picks the scene's renderer or the specified one, and warns: Arnold on the command line without a batch license renders with a watermark.
Sets up Maya on a Rocky Linux or RHEL 9.5 server, a version listed by Autodesk in the Maya 2026 requirements: installs the required libraries, the license and Maya .rpm packages, checks the license service and finishes with a test without the interface. For Ubuntu or Debian, Autodesk offers no package; it proposes a virtual machine (VM) with Rocky.
To traverse a lot of geometry, it uses API 2.0 (maya.api.OpenMaya) inside mayapy; for the rest, maya.cmds. If the current code depends on PyMEL, it warns you: PyMEL no longer ships with Maya and is maintained by the community, without Autodesk support.
Splits the range across machines, a block of frames on each, as the documentation shows; for a real queue, it connects each node's Render to a manager (Deadline, OpenCue, Tractor or similar). First, it checks the renderer license on each node.
The same Octo cycle, applied to Maya. Each arm has a narrow role; the decisions are made by a person at your company.
Maya version, OS and distribution, installed renderers and plug-ins. Checks the flags with Render -help, because the common flags list comes from 2013 documentation.
The fields of the inventory JSON, the image folder per scene, the format (png, exr), the name of each log and the exit code the batch reads.
Renderer license per node, the license service on Linux and the terms of use for hosted batch. Isolates autoloading plug-ins, which can break the script, with -noAutoloadPlugins or a clean preferences folder.
mayapy for Python logic; maya -batch for quick or legacy MEL; Render when the output is images; OpenMaya for heavy geometry. Server on Rocky or RHEL 9.5.
Initializes Maya before importing maya.cmds and uninitializes on exit, also on error. A script that runs both in and outside the Script Editor guards the initialization with try.
Runs on a few scenes and a few frames and checks by the result: the JSON has the meshes, the images are in the folder with no watermark, the log has no missing-library errors.
With your OK and the backup done, it runs the scenes and frames and checks one by one what came out and what failed, without taking a success message as proof.
Distribution, version, libraries that were missing, renderers and flags confirmed on your installation. The next batch starts from this record.
Nothing runs in batch before your OK. Nothing is overwritten without a backup.
The criteria Octo uses to choose. Python in mayapy for logic, MEL when it's quick or legacy, Render when the output is images.
| Task | Recommended path | Alternative |
|---|---|---|
| Inventory, conversion, scene validation in batch | mayapy + maya.standalone.initialize() | maya -batch with python("...") |
| Quick MEL command on a scene | maya -batch -file scene.mb -command "..." | mayabatch on Windows |
| Run a legacy MEL file | maya -batch -file scene.mb -script file.mel | — |
| Render a sequence | Render -r <renderer> -s -e -rd | — |
| Rendering across several machines | Render on each node + a manager (Deadline etc.) | Frame blocks per machine, no manager |
| Linux automation server | Rocky or RHEL 9.5 + .rpm + mayapy | — |
| Heavy geometry logic | maya.api.OpenMaya inside mayapy | — |
| New Python code | maya.cmds + maya.api.OpenMaya | PyMEL via pip, without Autodesk support |
Three steps. Each one only makes sense after the previous one has shown results in your operation.
A proposal, not a promise
On a machine with Maya, on Linux, Windows or macOS, you ask in business terms and get the proposed batch, to review before it runs.
mayapy scriptA Rocky or RHEL 9.5 server with Maya installed from the .rpm packages, where batches run without tying up anyone's workstation.
Render on each node, connected to a queue manager, with the renderer license checked before setup.
Each point below has a source published by the vendor, the project or the responsible agency. The sources are in the next section.
4
points with a published source, each with its reference alongside.
.rpm packages.Source: Maya 2026 Help, system requirements.deb package. Converting the .rpm works for some, but remains unsupported.Source: support article “Maya 2026 fails to launch on Linux Fedora”mayapyuninitialize() before exiting; this also prevents the interpreter from crashing on shutdown.Source: “Initializing and uninitializing in Python” helpOcto prepares everything, but doesn't sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and generates the documents: spreadsheets, reports, drawings and drafts.
Deliverable: material ready to checkThe licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.
Step: review by the signerOcto does not sign. Designs, technical reports, ART/RRT (Brazil's professional responsibility records), accountability reports and any official document are still signed by the company's or agency's licensed professional: here, the designer or the engineer responsible for the project.
Sign-off: designer or responsible engineerAutodesk and PyMEL documentation used on this page.
The assessment starts by reading your scenes and your installation, without changing anything. You get a map of what can be automated and decide with it in hand.