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
I'm trying to export a simple animated mesh with few keyframes, but I noticed that the exporter bakes the keyframes for no obvious reason...?
Here's a screenshot, I'm using both linear and Bezier, but it kind of doesn't matter:
The Optimized Export, does reduce few keyframes, but there are so many "useless" ones who do no change values.
Thanks
The text was updated successfully, but these errors were encountered:
we will have a look on it.
What i can say so far is we are only exporting animation as LINEAR and optimizations are computed On the fly with in house function from frame to frame, which is lead obviously to numerical precision error and wrong "optimization" decision.
Solution are
to tag the frame with the type of animation (from MAX/MAYA point of view) and take advantage of this information for optimization.
introduce some simple DSP algorithm but this is a non sense here
for GLTF take advantage of LINEAR, STEP, CUBICSPLINE interpolation mode.
I'm mean taging the frame into the code, where we do not take the type of animation into account. The frames are processed as timeseries without knowledge of where the sampling is coming from (Linear, Bezier,..). This has the advantage to be generic but has border effect such the one you experienced.
related to #1021
I'm trying to export a simple animated mesh with few keyframes, but I noticed that the exporter bakes the keyframes for no obvious reason...?
Here's a screenshot, I'm using both linear and Bezier, but it kind of doesn't matter:
The Optimized Export, does reduce few keyframes, but there are so many "useless" ones who do no change values.
Thanks
The text was updated successfully, but these errors were encountered: