Cannot open file on render farm: Maya texture reference resolution
0 reputation · 27 Jul 2025, 22:53 UTC
Goal
Ensure that external texture references in a Maya scene resolve correctly on a Linux render farm despite being created with absolute Windows paths on a local workstation.
Constraints
Rendering is performed in batch mode using maya -batch on nodes that lack the same drive letters or mount points. The scene was saved with absolute paths, and the dirmap rules defined interactively in the UI are not persisted to Maya.env or userSetup.mel. Additionally, Arnold’s ARNOLD_TEXTURE_PATH is set on the workstation but not on the farm, so texture lookup occurs independently of Maya’s internal search path.
Unresolved Decision
Should the studio enforce relative‑only referencing by default, breaking legacy workflows, or provide a farm‑aware path virtualization layer that abstracts OS‑specific roots? The current pipeline relies on custom submitters and environment modules, but no single documented solution exists.
Questions
- How can dirmap rules be made persistent across batch renders without modifying each job submission script?
- What is the recommended approach to synchronize Arnold’s texture search path with Maya’s internal path resolution on heterogeneous nodes?
- Should a studio policy mandate relative‑only referencing at scene save time to avoid “Cannot open file” errors, or is a custom path abstraction preferable?
maya