USD for Maya v0.24.0 Release Notes

USD version 0.24.0 is the latest release available. Visit the official Autodesk MayaUSD GitHub repository to obtain this version or any subsequent releases.

Highlights

This build is compiled with USD 22.11 and MaterialX 1.38.5. This release installer includes the following improvements:

General Updates:

• Session layer staying in sync when removing, reparenting, or grouping prims while edit routing is enabled
• Preventing edits to persist across Maya sessions
• Support for edit routing
• Pulled Maya object inherits visibility from ancestor prims (routing edits for visibility toggle)
• Drag and drop a sublayer that is saved/loaded as a relative path
• Pin a stage in the USD Layer Editor

What's Fixed

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.
• It is not recommended/supported to use the same USD stage repeatedly, as it can cause operation sync issues. For example, there can be multi transform issues when rotating or scaling a secondary stage of the same USD file.

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.
  • Note: Normal map connection is lost on export of UsdPreviewSurface and this is also an issue while using MaterialX.
• 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.
• 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.
• 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 and display layer contextual menu for more information

• Importing Maya files containing stages and display layers into Maya is not supported. Display Layer assignments will break during the import process.
• Instances of point instancers are unsupported.
• Referenced display layers are unsupported.

Viewport display limitations

See the following Github discussion topic and USD data in the Viewport topic for more information

• When USD lights are created, nodes are added to draw lights in the Viewport. By default these light nodes are not ignored on render time and cause lighting issues at render time. These nodes can be filtered out by the translator using the following code:

  // Skip UFE nodes coming from USD runtime
  // Those will be handled by USD Imaging delegate
  MStatus              status;
  static const MString ufeRuntimeStr = "ufeRuntime";
  MPlug                ufeRuntimePlug = dagNode.findPlug(ufeRuntimeStr, false, &status);
  if ((status == MS::kSuccess) && ufeRuntimePlug.asString() == "USD") {
        return;        } 

• Some HUD display text (fps, poly count, camera names etc.) in the Viewport can be darker and blurrier than in VP2 when (mayaHydra Experimental) Hydra GL is selected as the Viewport renderer. See load and manage plug-ins for more information and visit the official Autodesk MayaUSD GitHub repository to learn more about Hydra.