Open GoogleCodeExporter opened 8 years ago
GoogleCodeExporter
commented
8 years ago Well this is one of the most basic things you'd expected from a tweening
engine, I really thing it should be prioritized.Original comment by adjoi...@gmail.com on 25 Mar 2014 at 10:13
GoogleCodeExporter
commented
8 years ago It is not that basic, considering we're talking about speed-based tweens and
not regular ones, and I actually removed that option because I thought it would
create confusion (and couldn't find a good use for it). But I was probably too
strict, so I implemented it and voilà. Please test it out and let me know if
you encounter any issue :)Original comment by daniele....@gmail.com on 26 Mar 2014 at 12:37
Attachments:
GoogleCodeExporter
commented
8 years ago [deleted comment]There are a lot of places where it could be useful. Examples would be:
The firing animation of a missile, speed-based, where its slower at first and
faster later on.
Smoothed look-at, again speed-based since you don't need to make it happen in
an instant when the difference is great.
That's why I thought it's basic. The only way I found to do it was manually
computing time from the difference between Vector3s and Quaternions (iTween did
it automatically, which also made porting tweens a bit more hassle). But maybe
I missed something? Anyhow I'm really glad you took the time for implementing
it (and so blazingly fast too). Thanks a ton!Original comment by adjoi...@gmail.com on 27 Mar 2014 at 7:12
Original issue reported on code.google.com by
daniele....@gmail.comon 18 Dec 2012 at 4:24