USD version 0.20.0 is a feature release compatible with Maya 2023.3. Visit the official Autodesk MayaUSD GitHub repository to obtain this version or any subsequent releases.

Highlights

This release installer includes the following improvements:

Updates/enhancements on Display Layer support:

• Corrected handling of Display List vs Variants
• Correct texture/wireframe/bbox display when prims in a display layer

Support:

• Update to MaterialX 1.38.5
• General stability, bug and UI fixes

What's Fixed

Fixed Issues from GitHub
[Github 1817] Conflict checking when stripping namespaces and specifying roots MAYA-115170
[GitHub 2196] Build script is making an assumption on the generator when one isn't supplied MAYA-122322
[Github 2093] UFE: printing rename command with UFE strings returns "none" MAYA-124571
[Github 2365] Chaser factory context GetDagToUsdMap() raises error MAYA-125142

General Fixed Issues
Renaming: renaming a USD object to its own name will cause a new increment to be added MAYA-124971
Crash on Cache to USD with animated rigs MAYA-125835
Crash when 'Edit As Maya Data' a MayaRef prim after caching MAYA-125786
Duplicate as USD Data timeline options don't show what is currently applied MAYA-124951
Edit as Maya on a Material prim gives a warning and nothing happens MAYA-123848
Editing a USD reference as Maya data will reset the timeline to 0 - 100 MAYA-124106

Known Limitations

The following list of limitations remains in flux as development is ongoing.

USD stage creation workflow limitations

See Create a USD stage for more information

• Switching selected object variant can cause sync issues.

USD import and export workflow limitations

See USD import options and USD export options for more information

• The round-trip workflow is currently lossy (ie. contains a loss of information from compression).
• Mesh component level control is currently unsupported.
• Vertex/Edge Component tags are currently unsupported.

USD materials workflow limitations

See USD import options for more information

• Duplicate Shader Nodes in the Materials dropdown of the USD File Type Specific Options Menu: Loading the latest MayaUSD plug-in will provide the UsdPreviewSurface shader node. Loading a previous version of the plug-in will provide a pxrUsdPreviewSurface shader node. While both materials can import and export intrinsically to USD, loading both plugins into the same file will provide both nodes and create backward compatibility issues. The two nodes will correctly export to UsdPreviewSurface, but importing the scene back into Maya will choose the first registered node (ie. selection is dependent on plug-in load order).
  • Workaround: Have only one of the two aforementioned plug-ins loaded in Maya or ensure the first loaded plug-in is the preferred selection.
• USD core rendering backend HydraGL(Storm) is not fully supported in Maya (switching to Hydra render delegate from VP2 on a Maya scene can cause Maya to crash)
  • Workaround: To ensure Maya's native VP2 render delegate can support the materials of a file, verify that the file's meta data inputs are importing correctly in Maya by using USD View. Generally, to achieve similar material results to an original file, convert to the original materials used on import.

Push/Pull workflow limitations

See edit as Maya data for more information

• USD data is unaware of Maya data inside in the mixed-data model:
  • When Maya data is inside a USD hierarchy, its visibility isn't inherited from its USD ancestors.
  • When Maya data is inside a USD hierarchy, reframing the Viewport on its USD ancestors will not include Maya data. Transforms can misconfigure when animating pulled USD data.
  • Unloading Payloads to an ancestor of a pulled node breaks the pulled state.
• When pulled Maya data is orphaned, the orphaned objects can still appear/ be visible in the Viewport.
• Edit as Maya is unavailable on material prims. A warning is provided.

Maya reference limitations

See add a Maya reference for more information

• When a USD object is in a pulled state, a mixed-data model will be active, where the pulled object will be Maya data, yet still inside of the proxyShape node or prim. When in this state, current limitations bar selection, hierarchy and other general expected behavious. For example, if you select the USD parent node of a pulled object, the Maya data nested inside will not be a part of that selection, which will not allow operations such as hiding objects etc.
• The ‘Maya Auto Edit’ attribute on a MayaReference prim is currently not functional.
• Editing a Maya reference as Maya data can cause targets to switch while caching to USD.

Display Layer limitations

See work with prims as display layers for more information

• Display Layer visibility works with all instanced geometry except for point instancers. The visibility toggle is unsupported for point instancers.
• Importing Maya files containing stages and display layers into Maya is not supported. Display Layer assignments will break during the import process.