Maya 2026 doesn’t save output with Deadline 10.4.1
On same ws Maya 2024 works fine.
which renderer with what output and settings? which OS?
If I get chance I’ll test a submission with 10.4.1.8
works ok for me
2026.0 on win10 using Maya Software with layers and saving png
what does the log file say? did it show where the output is written? is the output relative the project and is the project set properly?
which renderer and what settings? try a sphere with software render and png, then try arnold etc without layers and png, then try exr.
process of elimination
Has a solution for this issue been found? I am encountering the same problem since we recently upgraded to Maya 2026. The jobs show up as ‘completed’ but no images are output to disk. I am using the Arnold renderer.
I recently discovered an updated option in Arnold which seems to break the render in Deadline.
Uncheck the option ‘Abort On Error’ under ‘Diagnostics’ tab in ‘Render Settings’
1 Like
Thank you! Unchecking ‘Abort on Error’ worked in terms of getting the renders to output to disk.
However, it seems the jobs are still generating many errors, so I have to raise the error limit in Deadline significantly for a job to finish. It’s a good workaround for now, but I am wondering about the root cause of these errors. I’ll post if I find anything.
1 Like
There were two recurring errors in the logs:
- ERROR: Unrecognized node type ‘nodeGraphEditorInfo’; preserving node information during this session.
The solution for this was to delete all the nodes of type ‘nodeGraphEditorInfo’, there’s a code snippet here that does that: https://stackoverflow.com/questions/60888928/unable-to-open-scene-with-mayapy-using-maya2020
- The renders were appearing very washed out compared to how they looked in Maya. In the error logs, there was this error:
2025-10-02 12:44:22: 0: STDOUT: 00:00:09 905MB ERROR | [color_manager_ocio] could not read ‘<MAYA_RESOURCES>/OCIO-configs/Maya2022-default/config.ocio’ OCIO profile.
This is possibly due to an issue with the config.ocio file or the MAYA_RESOURCES env var being set incorrectly, I am working with our IT to troubleshoot this.
1 Like
There’s another post regarding this issue here
Renders fail after MtoA upgrade (Maya 2023 / Arnold) - Deadline - AWS Thinkbox Discussion Forums
I’ve added a new rule in Deadline Monitor, under “Configure Repository Options” / Mapped Paths, to have it replace
<MAYA_RESOURCES>with/usr/autodesk/maya2023/resources.
You should be able to add an entry for this as follows (adjust for your version)
1 Like
Fixing the path mapping worked!
I was still getting errors, and realized that of the 3 labs being used on our render farm, 1 of them was rendering frames without errors. For now, I’ve limited the farm to that lab, we may have to update Maya installs in the other labs. After limiting the pool, I finally got my job to run with 0 errors!
Thanks again for all your help @anthonygelatka!
1 Like