-
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
Improve image/video export when all skeletons are exported together to export multiple animations #780
Comments
Each skeleton has different animations. To export "all" of them, we'd have to export all combinations. If
This is unlikely to be what you want. You said that the animations are the same, do you mean they use the same name? I guess we could try to detect this scenario. A workaround may be to use command line export to do all the exports you need. |
I want to render two skeletons at the same time and export their animation1~4 combine as one .mov. |
I understand. This could only work automatically by matching the animation names. We don't support that, but we'll leave this issue open to track the request and may implement it in the future. For now you can perform 4 exports using |
Thanks your answer, hopefully the future will add this function, and if use scripts and Current animation to export, it need to manual switch each animation, it so tired. |
I was thinking you could write a scripts that can generate (or modify) an export settings file to set which animations to export. However, I see that when exporting all skeletons together ( |
Hello, I have a project file with multiple skeletons and Animations,and skeleton's Animations are same. When using Export Video, I found that only when the "Export type- Animation , Skeletons-Separate",I can choose "Animation-All". I want to select the " Export type-Animation , Skeletons-Together , Animation-All" to export all animations. It seems that there is no such option I can choose.How to solve? Will a future update solve this?
here sample files:
test.zip
The text was updated successfully, but these errors were encountered: