-
Notifications
You must be signed in to change notification settings - Fork 44
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
Suggestion: Sample with discrete/constant interpolation of scale 0↔1 #77
Comments
This has been untouched for over a year. Is there anything to do here? If there is no response, then this issue will be closed by 27 Nov. |
Babylon.js has already fixed this, but a sample model could still be useful. |
By "constant", you mean There is a pending PR for the
if this is it... |
Yes, thanks – |
This is what the An archive with the GLB and the code (hand-edited output of gltfTransformifier) for generating it: InterpolationTestFix0004_scale0.zip If people agree, I can update #26 with this. |
total aside, but that is a wild and beautiful solution 🤯 |
OT: The name was inspired by BCELifier. It's a very rough "proof-of-concept" for now, but I try to allocate some time to maybe turn it into something useful. |
I have updated the PR at #26 (comment) with the latest state that was posted here, where the scale interpolations go down to (0,0,0). When this PR is merged, then this issue can probably be closed. |
The current version of the |
In a thread on the three.js forums we've come to the conclusion that a significant number of viewers cannot display constant interpolation of scale, particularly scale 0↔1.
The 'broken' three each show slightly different results — Spark AR doesn't appear to support constant interpolation at all, whereas Babylon.js plays the animation correctly once and then reaches a broken state when trying to loop it.
It's a useful technique for 'baking' simulations as flipbook-style animations, showing each mesh for a single frame, but does depend on correct support for animating scale with constant interpolation.
The text was updated successfully, but these errors were encountered: