You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Gltf animation imported in Editor, loaded via Addressables and animated with Playable Graph Api will loop when reaching the end of an animation clip.
Gltf animation imported in runtime, loaded via Gltfast api (Animation method set to Mecanim) and animated with Playable Graph Api will stuck at the end of the clip (last frame).
Apparently, runtime imported animations do not have Loop Time enabled. I wasn't able to find a way to specify whether to enable it.
Files
Attach or link to .gltf/.glb files that trigger the bug.
The model contains 2 animations: anim1 and anim2. Exported from blender.
In addition, make sure to run those files through the glTF Validator first. If you encounter errors or warnings, try to make sure they are not responsible for the issue and file a bug report with the software that generated the glTF file as well.
Note: You have to ZIP archive them first in order for GitHub to accept the upload.
If your files are confidential:
Try to create a similar, but intellectual-property-free glTF that reproduces the bug in the same way (so any community member can have a look)
Otherwise, still create this issue and send the files (or a link to them) discretely via email
To Reproduce
Steps to reproduce the behavior:
Just load it up with the api in runtime and the animation clips does not have Loop Time enabled. Drag it directly into the project view would result it having animations with Loop Time enabled.
Expected behavior
A clear and concise description of what you expected to happen.
Same behavior between editor imported animation and runtime imported animations. Or at least a way to specify should the Loop Time be enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
glTFast version 6.2.0
Unity Editor version 6000.0.0f1
Render Pipeline and version URP 17.0.3
Platform: Editor
additionally (if significant for the bug):
Additional context
Add any other context about the problem here.
Now think about it this might be more like a feature request.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
Gltf animation imported in Editor, loaded via Addressables and animated with Playable Graph Api will loop when reaching the end of an animation clip.
Gltf animation imported in runtime, loaded via Gltfast api (Animation method set to Mecanim) and animated with Playable Graph Api will stuck at the end of the clip (last frame).
Apparently, runtime imported animations do not have Loop Time enabled. I wasn't able to find a way to specify whether to enable it.
Files
Attach or link to .gltf/.glb files that trigger the bug.
The model contains 2 animations: anim1 and anim2. Exported from blender.
test.zip
In addition, make sure to run those files through the glTF Validator first. If you encounter errors or warnings, try to make sure they are not responsible for the issue and file a bug report with the software that generated the glTF file as well.
If your files are confidential:
To Reproduce
Steps to reproduce the behavior:
Just load it up with the api in runtime and the animation clips does not have Loop Time enabled. Drag it directly into the project view would result it having animations with Loop Time enabled.
Expected behavior
A clear and concise description of what you expected to happen.
Same behavior between editor imported animation and runtime imported animations. Or at least a way to specify should the Loop Time be enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
additionally (if significant for the bug):
Additional context
Add any other context about the problem here.
Now think about it this might be more like a feature request.
The text was updated successfully, but these errors were encountered: