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
Is your feature request related to a problem? Please describe.
This came out of an attempt to use the schema api adaptors for PxrMeshLight. Instead of PxrMeshLight resulting in a new prim in usd, we instead just author it as an applied API on the mesh itself. We'd like to prevent the usd exporter from creating a prim for it because it interferes with the "merge shape and transform" logic.
The |SomeMesh|PxrMeshLight|PxrMeshLightShape would end up still being exported at /SomeMesh/PxrMeshLight which would mess up the mergeTransformAndShape logic. With the Primless registry, we're able to tell the writer to completely ignore the prim, which allows |SomeMesh and |SomeMesh|SomeMeshShape to be merged into just /SomeMesh.
Describe the solution you'd like
Part of #2557 was adding a new Primless registry. This told the exporter to not create a node which allowed the merge logic to behave as expected.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This came out of an attempt to use the schema api adaptors for
PxrMeshLight
. Instead ofPxrMeshLight
resulting in a new prim in usd, we instead just author it as an applied API on the mesh itself. We'd like to prevent the usd exporter from creating a prim for it because it interferes with the "merge shape and transform" logic.If we follow the example in:
https://github.com/Autodesk/maya-usd/blob/dev/test/lib/usd/plugin/bulletAdaptor.cpp#L416
We still end up with a node, which breaks this case:
The
|SomeMesh|PxrMeshLight|PxrMeshLightShape
would end up still being exported at/SomeMesh/PxrMeshLight
which would mess up themergeTransformAndShape
logic. With thePrimless
registry, we're able to tell the writer to completely ignore the prim, which allows|SomeMesh
and|SomeMesh|SomeMeshShape
to be merged into just/SomeMesh
.Describe the solution you'd like
Part of #2557 was adding a new
Primless
registry. This told the exporter to not create a node which allowed the merge logic to behave as expected.The text was updated successfully, but these errors were encountered: