Versions Compared

Old Version 3

changes.mady.by.user Bernard Kwok

Saved on

compared with

New Version 4

changes.mady.by.user Bernard Kwok

Saved on

Key

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

...

  • For multi-backend support for Vulkan, MDL, Metal, etc applications need to maintain multiple Shader Gen paths that can easily get out of sync and are hard to maintain.
  • MaterialX nodes as ground truth definitions of UsdPreviewSurface. 
  • UsdLux v.s MaterialX Light nodes
  • Customize shaders for selection, highlighting. 
  • For Hardware renderers customize shader stages, render state management 

Topics for review

...

Properties 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 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











Support multiple nodes with multiple outputs



issue 1581 logged. Internal issue: USD-6820







definition information associationImport 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 variationsDefinitions 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. (PR 1641)
definition search pathRelated 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)














Current list of all MaterialX related issues (not all applicable)
https://github.com/PixarAnimationStudios/USD/issues?q=is%3Aissue+is%3Aopen+Materialx

Namespaces and Versioning

https://github.com/autodesk-forks/MaterialX/blob/adsk_contrib/dev/resources/Materials/TestSuite/adsklib/archviz/adsk_metal.mtlx

...