Use Custom Mesh Attributes for SubdivisionSchema ... Chaser vs Adaptor ? #2757
Unanswered
SebSchmidtWetaFx
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
We've been using “mayaUsdExport” for a while using our internal export chasers, however I recently discovered a case where using the "adaptor" instead of "chasers" would make more sense. That said, I might have misunderstood the adaptor concept.
Due to legacy reasons our geometry does not use the
USD_ATTR_subdivisionSchemeattribute to describe what subdivision scheme is used. It rather uses a boolean (isSubd) which indicates that something should be using the CatmullClark subdivisionScheme:example of geo
The only way I found to support this was using our chaser and as part of the PostExport() to check all maya-mesh nodes for the mentioned
isSubdattribute and set the subdivisionScheme on the UsdPrim accordingly:Where this is causing issues is where I want to get the Normals exported for nodes that are meshes, as we are not using the 'USD_ATTR_subdivisionScheme' attribute there is nothing that triggers the relevant code-path within mayaUsdExport and we're not getting Normals exported (even when setting USD_EmitNormals).
While I can work around this and add the Normals export into the chaser-logic, I am wondering if there is a better way of achieving the same result (without changing the scene) but using Adaptors?
Thank you for your insight!
Seb
FYI: @HamedSabri-adsk
All reactions