Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to register a prim to not be exported #2607

Open
mrawde opened this issue Sep 16, 2022 · 1 comment
Open

Ability to register a prim to not be exported #2607

mrawde opened this issue Sep 16, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@mrawde
Copy link
Contributor

mrawde commented Sep 16, 2022

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.

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:

|SomeMesh # transform
  |SomeMeshShape # mesh
  | PxrMeshLight # transform
    | PxrMeshLightShape # PxrMeshLight

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.

@mrawde mrawde added the enhancement New feature or request label Sep 16, 2022
@tanant tanant removed their assignment Nov 30, 2022
@santosg87
Copy link
Collaborator

This is something we are currently investigating the viability of adding support for. There is is definitely a good use case for this.

@neilh-adsk neilh-adsk moved this to Scheduled in maya-usd Nov 6, 2023
@Autodesk Autodesk deleted a comment from maya-usd-git-sync bot Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Scheduled
Development

No branches or pull requests

3 participants