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
Describe the bug
If I create a proxyAccessor to drive the xformOp properties on an Xform prim from a referenced Maya transform, it works as expected in the current session. However, once your save and re-open the scene, it no longer works.
Steps to reproduce
Steps to reproduce the behavior:
Create > Universal Scene Description > Stage With New Layer
Add an Xform prim
2a. Add a Cube prim as a child of the Xform prim (for visibility)
Reference a file with a single transform
Create a proxyAccessor using mayaUsd.lib.proxyAccessor.connectItems
Move the referenced transform; observe the Xform prim follows
Save and re-open the scene
Observe the Xform prim is at origin, and no longer follows the referenced transform.
An example setup is provided in the attached scene.
Expected behavior
A proxyAccessor to drive the xformOp properties of an Xform prim, driven by a referenced Maya transform, should still work after the scene is re-opened.
Describe the bug
If I create a proxyAccessor to drive the xformOp properties on an Xform prim from a referenced Maya transform, it works as expected in the current session. However, once your save and re-open the scene, it no longer works.
Steps to reproduce
Steps to reproduce the behavior:
2a. Add a Cube prim as a child of the Xform prim (for visibility)
An example setup is provided in the attached scene.
Expected behavior
A proxyAccessor to drive the xformOp properties of an Xform prim, driven by a referenced Maya transform, should still work after the scene is re-opened.
Attachments
scene.zip
Specs (if applicable):
The text was updated successfully, but these errors were encountered: