You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug is now fixed and will be released into v0.3.7.
The mmSolver.api.Attribute.get_node() function did not return the unique DAG node name because it used the MFnDependancyNode class, which does not understand DAG hierarchies and assumes all DG nodes have a unique name (by definition of being a DG node).
Problem
The Solver UI will (incorrectly) display nodes with the same non-unique node names.
When 2 nodes with the same name are added to the Output Attributes, the Solver UI will collapse the nodes together.
Expected behavior:
When 2 nodes with the same name are added to the UI, both nodes should be visible and independent of each other.
Actual behavior:
The second node name is collapsed into the first node in the UI.
See the example images below.
Solver UI (the translate attributes are doubled up):
Outliner (shows the hierarchy with selected nodes added into the Solver UI):
Software Versions
mmSolver version: v0.3.6+
Maya version: Reported for Maya 2018, probably affects other versions too.
Operating System (OS): Reported on Linux, but also happens on Windows.
The text was updated successfully, but these errors were encountered: