-
Notifications
You must be signed in to change notification settings - Fork 2
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
Animation support. #14
Conversation
In the spirit of the higher-level nature of the library, I also thought it best to remove |
I'm not sure I agree with this. There are some counterexamples here: https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#animations. However,
I still think this is fine. The worst case is we'll have some duplicated data |
This implementation is still missing support for sampler outputs that use normalized integers instead of just floats, namely rotations and weights. See the last two tables in the section linked for more details. |
2354619
to
4fb0e24
Compare
Tests are failing with:
EDIT: Otherwise, LGTM |
4fb0e24
to
46ef599
Compare
@mrehayden1 How are you feeling about this? Are you ready to merge this? |
@sgillespie I've got a branch that adds skinning support too to merge in also now the PR to matrices is merged. Can we do it here or shall I open another PR? Update: Reading the code and from what I remember, skeletal animations is independent of skins (but not the other way round), so I would be happy to merge this. |
A preview of how animations and skinning are working. 5g9w8r_2.mp4 |
I'll leave that up to you--whatever is easier for you |
Okay. I've just opened a new PR for skinning. |
Great! If you resolve the conflicts here, I'll merge |
I think i pushed a merge commit before. Did that not resolve any conflicts? |
Ah, there's a merge commit, that's why I can't rebase. No worries, I'll do a regular merge |
Thanks! I'll make sure to rebase next time. |
Just opening a PR to help track what's left to do.
I've started testing this with some real animated models exported from Blender. So far so good, but we're missing support for accessors with normalized integer component types which I might add, but that hasn't been a problem so far.
Regression tests are also needed too I suppose.