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

Skinning fixes for 1.0.1 #647

Merged
merged 2 commits into from
Jul 13, 2016
Merged

Skinning fixes for 1.0.1 #647

merged 2 commits into from
Jul 13, 2016

Conversation

lexaknyazev
Copy link
Member

See #624

@pjcozzi pjcozzi added the 2.0 label Jul 9, 2016
@pjcozzi
Copy link
Member

pjcozzi commented Jul 9, 2016

All looks good to me. Will get more feedback on Wednesday morning, and merge then.

@pjcozzi
Copy link
Member

pjcozzi commented Jul 13, 2016

Thanks @lexaknyazev! Can you please provide a concise description for this that I can add to #605?

@pjcozzi pjcozzi merged commit 10b70f9 into KhronosGroup:1.0.1 Jul 13, 2016
@lexaknyazev lexaknyazev deleted the skinning-1.0.1 branch July 16, 2016 12:04
@tparisi
Copy link
Contributor

tparisi commented Jul 26, 2016

I think these changes all look good, clarifying language. Maybe we do one more pass before merging? @pjcozzi did you have a look?

@pjcozzi
Copy link
Member

pjcozzi commented Aug 10, 2016

@lexaknyazev did you see this:

Can you please provide a concise description for this that I can add to #605?

@lexaknyazev
Copy link
Member Author

The only change (not clarifications) could be described as

Skeleton hierarchies (nodes containing jointName) must be separated from non-skeleton hierarchies.

@pjcozzi
Copy link
Member

pjcozzi commented Aug 10, 2016

Thanks!

lexaknyazev pushed a commit that referenced this pull request Feb 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants