-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
instanceSkin.sources or instanceSkin.meshes? #188
Comments
I want to resolve #164 before taking decision on this one. AFAIR, What I had originally in mind was to have source being potentially something else , e.g a morph but according to @tparisi we'll have both in parallel, and then we could introduce an array in node to specify the order of processing. So once we agree on that on #164 with the upcoming morph proposal, then we can be more restrictive here and use mesh in place of source. |
ok with |
0.8 spec updated in f3495a5. |
The converter and schema are in sync. |
I'm still ramping up on skinning so I may be missing the semantics of using
sources
ininstanceSkin
to reference meshes, but wouldn'tmeshes
be a better name since it is consistent with nodes that have justmeshes
?Current naming:
The text was updated successfully, but these errors were encountered: