Sign in to follow this  

Animation change

Recommended Posts

Hey team!! as part of a change I need to do for animation, I introduced a new internal class named RuntimeAnimation.

The rationale behind this class is to make a bit clearer how animations work.

Animation (the class) is here to define an animation and its main goal is to store the keys and associated values (type, loop, easing)

When you start an animation on a mesh by using scene.beginAnimation(mesh), all the animations stored on mesh.animations will be used to create an Animatable.

Animatable is a store of a list of runtimeAnimation which will use the animation as source and which will be used to interpolate values.


Before my change Animation class was used for both storing the data and running the actual interpolations which was misleading.


I DON'T think that this will break any existing code. But If I'm wrong please report your findings here.


(let me ping @Wingnut as I know he was playing a lot with animations)

Share this post

Link to post
Share on other sites

Thx DK, for both trying to improve the animation system, and for pinging me.

My old animation test scene is working fine, looking as healthy as ever.  I also toured many PG's that mentioned 'animatable', and they are all looking good, too. 

All seems well.  PARTY!  :)

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.