MaterialX: What Actually Works
An open standard for describing materials and look development so they can move between applications and renderers.
Imogen Clarke
Why does it matter?
Materials often break when files move between tools, and MaterialX provides a shared definition that many applications understand.
What are the numbers?
- Origin developed at Lucasfilm and now an Academy Software Foundation project
- Node graphs materials are described as networks of nodes
- Code generation MaterialX can generate shader code for several languages
- USD MaterialX materials can be used in OpenUSD workflows
What should I do?
- Use MaterialX where pipelines share materials
- Test materials in each target renderer
- Keep material libraries versioned
- Document custom nodes
- Compare renders across applications
What should I avoid?
Avoid:
- Assuming identical results in every renderer
- Custom nodes without documentation
- Mixing proprietary and shared materials without planning
- Skipping validation
When should I get help?
Short answer Bring in help when material libraries must work across studios or renderers.
Where this comes from
- Academy Software Foundation — MaterialX
- Alliance for OpenUSD — OpenUSD
The figures and practices above come from the sources listed.
Working on something like this?
We take on 3D Design & Development work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
