-
Notifications
You must be signed in to change notification settings - Fork 70
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
only export keyframes for node animations #87
Comments
The code for this feature exists, it's commented out though. |
yes, see: #86 (comment) |
@oldmanauz I was the one who implemented this feature. I was unable to come up with a solution on how to export the keyframes, it didn't seem as simple as exporting every frame. |
@sercero I see your logic. Is it better to have a well documented part-implementation that might suit some than potentially never having a solution? |
I would prefer having that part implementation |
@oldmanauz, @paroj: of course I have no problem with more options, mostly my concern is that the option to export every keyframe is still present. Also, I acknowledge that there are cases when exporting only the keyframes is enough, so it is useful of course to have that option as well. Thanks! |
Im not fully happy with this. While I understand the need of it, there are serious drawbacks.
.skeleton
is less evil as that is a binary format not edited by humans..scenes
on the other hand seem to be designed to be human readable. But with unrolling animations you end with something like this:I think in this case, I would just for once advocate for a user-switch (default-off):
(we can also merge this as is and add that later)
Originally posted by @paroj in #86 (comment)
The text was updated successfully, but these errors were encountered: