...
| Expand |
|---|
|
| Property | Description | USD level | USD/MTLX level | MTLX level | Status | Proposal(s) |
|---|
| Support nodes with multiple outputs |
|
|
|
| issue 1581 logged. Internal issue: USD-6820 |
|
|
|
|
|
|
|
| | definition information association | Import does not capture the correct association between a definition and a nodegraph sometimes. |
|
|
| Issue 1629 logged | - Specific code fix proposed for conversion to MaterialX
| | definition variations | Definitions may be specified in a variety of different ways. Not all appear to be consumable properly. Some deal with definition discovery. |
|
|
| issue 1636 logged | - Refactor import discovery logic. This includes being more aligned with MaterialX Version 1.38.x (PR 1641)
| | definition search path | Related to definition discovery (definition not found in path) |
|
|
| Issue 1586 logged. Internal issue USD-6941 | - consider USD search path env variable on read for mtlx (partial, no concensus) (PR 1628)
| | load / reload | Robustness / repeatability of loading documents |
|
|
| - Issue 1504 logged. Internal issue: USD-6670 (data loss)
- Issue 1502 logged. Internal issue: USD-6669 (node missing)
|
|
|
|
|
|
|
|
|
|
...
https://github.com/PixarAnimationStudios/USD/issues?q=is%3Aissue+is%3Aopen+Materialx
https://github.com/PixarAnimationStudios/USD/pulls?q=is%3Apr+is%3Aopen+materialx
Documentation for Unsupported Features
...
...
Shading / Rendering Integration
- WIP: To decide what to add here. Leaving a call out for USD example contributions.
- want to include role of shaders and backends
- help to aid those that want to figure out how their renderer fits in
- custom shader generator integration examples would be useful here.
Issues
Issues found related to workflow of USDShade to MaterialX conversion. For code generation this includes the topic of how to get performant updates.
The underlying assumption appears to be requirement to always perform conversion and to make this process performant, but alternative approaches such as keeping correspoding MTLX in memory might be a consideration.
| Expand |
|---|
| title | USDShader to MaterialX Conversion |
|---|
|
| Property | Description | USD level | USD/MTLX level | MTLX level | Status | Proposal(s) |
|---|
| Unique nodegraph creation | Duplicate graphs being created during conversion
|
| Y |
| Issue 1659logged | - Append a nodegraph suffix (PR-1658). Remark left: suggest to create a unique child name using MTLX utilities. (makeUniqueChildName).
|
|
| Expand |
|---|
|
| Property | Topic | Description | USD level | USD/MTLX level | MTLX level | Status | Proposal(s) |
|---|
| selection hilighting | Display feature | HdStorm has no selection highlighting for geomteric primitives with MaterialX materials applied.
|
| Y |
| Issue 1614 logged | - Modify GLSLFX shadergen to apply
additional color overrides ? (PR-1647)
| | parameter update | Performance | Prevent compiles on parameter changes by changing GLSFX code generation to use templated code and parameter buffer updates. |
| Y | Y | USD Issue: MTX Issue: 710
| - MaterialX input parameters are no longer hardcoded in the shader but set from the parameter buffer
- Support float and integer types with sizes between 1 and 4. Make sure that all other types are still hardcoded, so that there are no gaps
- USD: PR-1664
- ADSK MTLX PR: 1320.
|
|
|
|
|
|
|
|
| | usdview slow on idel | Performance | Root cause not known yet. |
| Y |
| USD Issue: 1638 |
|
|