Docs: Skin weight and skin index clarification #7719
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrdoob
added a commit
that referenced
this pull request
Dec 2, 2015
Docs: Skin weight and skin index clarification
|
Many thanks! |
|
I cannot find these precious explanations anymore in the documentation, neither on https://threejs.org/docs/?q=skinned#api/en/objects/SkinnedMesh nor https://threejs.org/docs/?q=skinned#api/en/core/BufferGeometry... Why? |
|
It's probably better to add to page to the manual in order to explain skinning/skeletal animation instead of putting such information to the API reference. |
|
Oh I understand... Second to you, what would be the ideal section for that in the manual: does this section already exist? |
|
After a quick look at the list in https://threejs.org/manual/, it seems there is no article about this topic yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves #7516.