-
Notifications
You must be signed in to change notification settings - Fork 30
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
mutliple animation takes #67
Comments
FWIW: Standard practice in glTF viewers is to play the first animation by default, and (ideally) provide some means of selecting others. More complex composition is possible but perhaps out of scope here. |
I agree, I also think an |
Perhaps the desired animation could be specified in the element's attribute, then changed dynamically. |
These are great suggestions. We'll propose a JS API to select animation takes eventually, but an attribute might be a simple start. It does assume that the data format can name the animations. And I agree that by default it should follow the glTF viewer behaviour of playing the first animation. |
Agreed with starting with a simple attribute for specifying an animation name (given format support). Then, I would think that the attribute would only work if the proposed |
It's common for models to have multiple animation takes bundled into or referenced within the model file (and they can be cycled through on the fly based on page events, etc). If there are multiple animation takes embedded in the model, would the following
autoplay
attribute loop through the first animation take that is found?I think there should be an attribute for specifying model clips. For reference,
<model-viewer>
implements this with several different attributes as documented here. A-Frame's animation-mixer-component also does something simialar declaratively.The text was updated successfully, but these errors were encountered: