Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleMaterialX Version Sync

What is the desired process to keep USD up to date with a given version of MaterialX.

PropertyDescriptionUSD levelUSD/MTLX levelMTLX levelStatusProposal(s)
API change handlingSome versions break API compatibility.
YYNeed to discuss this. Jonathan Stone noted future versions need to be more careful about possible compatibility breaking changes (API, definition etc).
  • Individual fixes as they come (e.g. PR-1633)
Compile time versionAllow compile time version exposure.

Y
  • PR to know version of MTLX at compile time PR-704

1586









Expand
titleProperties List


PropertyDescriptionUSD levelUSD/MTLX levelMTLX levelStatusProposal(s)
namespaceHelpful to qualify definitions with a given scope to avoid name clashes.
e.g. there may be a Adobe vs ILM namespace.



Issue 1614 logged
  • Encode namespace as part of definition identifier (no consensus) (PR 1631)
colorspaceColor management tagging for inputs as well as color management system specification.Y

  • Agreement to support as formal property. Needs scoping and definition.
  • Issue 1532 logged for MTLX export. Internal issue: USD-6703 (old - pre-agreement)
  • "Follow what is going on with MaterialX". (vague)
ui value propertiesHints for UI. e.g. ui min, max, step etc.Y

Separate proposal for this.
unit / dimension supportSupport for a real world unit or dimension for an given shader input. The type of the unit may be dynamic / data driven.


Issue 1632 logged. Internal issue: USD-6928.
tokensImport and resolving of token names used for geometric and file identifiers. Can include consistency of token delimiters
Y


fileprefx



Issue 974 logged. Admin: not closed
  • Resolved in PR 977.
versionDefinition versioning


tbd








...