I’m guessing that was added so that the future call wouldn’t “fight” with the tick (one time fall on one side of it and another fall on the other, meaning that some ticks would see two future calls and some would see 0).  If this has been removed, I would check to make sure the animation still looks as smooth.

Eventually, I think we can create a solution that does not depend on the regular interval of updates.

From: davideaster [mailto:notifications@github.com]
Sent: Thursday, February 13, 2014 12:19 PM
To: virtual-world-framework/vwf
Cc: Burns, Eric
Subject: EXTERNAL: Re: [vwf] Branch/view interpolation (#130)


In support/proxy/vwf.example.com/spin-on-click.vwf.yaml:

>        var axis = this["spin-axis"];

>        this.rotateBy( [ axis[0], axis[1], axis[2], this["spin-rate"], 0 ] );

> -      this.future( 0.05 ).spin();  // schedule the next step

> +      this.future( 0.044 ).spin();  // schedule the next step

Is 0.044 a magic interval that works well with interpolation?

—
Reply to this email directly or view it on GitHub<https://github.com/virtual-world-framework/vwf/pull/130/files#r9717732>.