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

Highlights

This release installer includes the following improvements:

Features:

• Maya Reference now available by default
• Support for Display Layer interaction with USD objects
• Prims are now able to be referenced, templated in display layers
• Expanded support for USD types (Normal3f, Point3f)
• Settable default prim when caching to USD

UI/UX improvements including:

• Preserve session layer on save
• Progress bar for import/export/push/pull
• Outliner icons for shading types
• Remember previous selected options
• Extra tabs showing bound surface materials

Support:

• Improvements to translator framework including namespace support for on USD import
• General stability fixes

What's Fixed

Fixed Issues from GitHub
[Github 2339] Crash parenting to a deactivated prim MAYA-124205
[Github 1766] Load with descendants collapses expanded sibling hierarchies MAYA-123836
[Github 1767] When parenting a prim to a collapsed group, it auto-expands the group MAYA-123808
[Github 2121] MaterialX/USD : V2 lighting should support ambient lights MAYA-123806
[Github 1451] UFE cameras should draw in the Viewport MAYA-123547
[Github 2352] Session layer in Unshareable stage doesn't get serialized in Maya file MAYA-123361
[Github 2263] export overwriting a usd File that is currently being referenced crashes Maya 2023 MAYA-122664
[Github 1821] Import of USDSkel scene produces incorrect mesh transform MAYA-122628
[Github 2234] ALT + Arrow key shortcut does not work on USD data model MAYA-122562
[Github 2052] Cannot create a prim on a stronger layer MAYA-121681
[Github 1307] USD doesn't respect the namespace options on Import or Create Reference MAYA-111092

General Fixed Issues
Geometry moves to origin when saving Maya scene with session layer changes MAYA-124207
USD breaks callback registration for addRMBBakingMenuItems MAYA-124088
Exporting custom attribute for subdivision scheme doesn't work MAYA-123119

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.