Maya Script to Repath Textures & Change Render Output Path Without Opening Maya Files (2018–2026)
Budget: $70.0
FIXED /
⭐ 4.63 (17)
India
autodesk-maya
Maya Scene Automation Tool (Headless)
Project Overview
We are looking for an experienced Autodesk Maya Pipeline / Python Developer to build a production-ready command-line tool that can modify Maya scene files (.ma and .mb) without opening the Maya UI.
The tool will be integrated into our cloud render farm pipeline and must run reliably in headless environments using mayapy or Maya Batch.
Target processing time: Up to 4 minutes per scene, depending on scene complexity.
Supported Maya Versions
Maya 2018
Maya 2019
Maya 2020
Maya 2022
Maya 2023
Maya 2024
Maya 2025
Maya 2026
Supported File Formats
.ma
.mb
Requirements
1. Asset Repathing
Automatically detect and update external asset paths, including:
File Textures
Image Sequences
Scene References
Alembic Caches
XGen
Interactive Groom
Yeti
Arnold Stand-ins (.ass)
V-Ray Proxies (.vrmesh)
USD Assets
Audio Files
IES Profiles
OCIO Config
Any other external asset paths
Support configurable path mapping (Local → Network/Cloud).
2. Render Settings Extraction
Extract render settings and export them as JSON.
Include:
Renderer
Resolution
Frame Range
Frame Step
Output Format
Output Path
File Name Prefix
Render Camera(s)
Color Management
For Arnold, extract production settings such as:
AA Samples
Diffuse
Specular
Transmission
SSS
Volume
Adaptive Sampling
Ray Depth
Texture Settings
Bucket Size
Threads
CPU/GPU Mode
Denoiser
For V-Ray, extract:
Image Sampler
Bucket/Progressive Mode
Noise Threshold
Min/Max Subdivisions
GI Settings
Irradiance Map
Light Cache
Bucket Size
Denoiser
Distributed Rendering
Render Elements
3. Update Scene
The tool should update:
Asset paths
Output directory
Render filename prefix
Render settings (when required)
4. Save Scene
Save the modified scene as:
.ma
.mb
5. Headless Execution
The tool must support:
mayapy
Maya Batch
Command Line
Fully automated execution
No UI interaction
6. Logging
Generate logs containing:
Start & End Time
Processing Duration
Renderer
Camera
Resolution
Frame Range
Missing Assets
Missing Plugins
Warnings
Errors
Success / Failure Status
Support both text and JSON logs.
7. Performance
Process scenes in under 4 minutes (depending on complexity)
Handle large production scenes
Optimized for render farm automation
8. Licensing Requirement
The solution should work without requiring an interactive Maya UI.
Must run in headless mode using mayapy or Maya Batch.
Deliverables
Complete source code
Installation guide
Configuration documentation
Usage documentation
Command-line examples
JSON export examples
Logging implementation
Error handling
Sample test scenes
Test results
Apri su Upwork