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

MAYA-109415 Fix warning on blendShape export #1684

Merged
merged 1 commit into from
Sep 7, 2021

Conversation

JGamache-autodesk
Copy link
Collaborator

Got "Unrecognized node" error on blendShape export. The node was the
fCurve driving the weight.

Looked in mayaFindOrigMeshFromBlendShapeTarget() and found out that the
traversal would start on a random plug in the checked branch. Sometimes
the input geom would be found first, sometimes the fCurve would be
traversed as well.

Fixed the code to make sure the traversal starts at the inputGeom plug
that would have been used to compute fnGeoFilter.inputShapeAtIndex(...)
in the ignoreWarning branch.

Got "Unrecognized node" error on blendShape export. The node was the
fCurve driving the weight.

Looked in mayaFindOrigMeshFromBlendShapeTarget() and found out that the
traversal would start on a random plug in the checked branch. Sometimes
the input geom would be found first, sometimes the fCurve would be
traversed as well.

Fixed the code to make sure the traversal starts at the inputGeom plug
that would have been used to compute fnGeoFilter.inputShapeAtIndex(...)
in the ignoreWarning branch.
@JGamache-autodesk
Copy link
Collaborator Author

@ysiewappl , since you wrote the original code, I would appreciate if you could have a look. Thanks!

@ysiewappl
Copy link
Contributor

Looked in mayaFindOrigMeshFromBlendShapeTarget() and found out that the
traversal would start on a random plug in the checked branch. Sometimes
the input geom would be found first, sometimes the fCurve would be
traversed as well.

Yea, I think your fix of starting right from the corresponding element plug for
inputGeom rather than the entire blendshape node itself makes sense to avoid
cases like these where there are other paths that lead to a mesh. Thanks for
helping to fix this!

@JGamache-autodesk JGamache-autodesk added the ready-for-merge Development process is finished, PR is ready for merge label Sep 7, 2021
@kxl-adsk kxl-adsk merged commit 325074b into dev Sep 7, 2021
@kxl-adsk kxl-adsk deleted the t_gamaj/MAYA-109415/fix_blendshape_export_error branch September 7, 2021 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
import-export Related to Import and/or Export ready-for-merge Development process is finished, PR is ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants