Jump to content
Search Community

Wodger

Members
  • Posts

    2
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Wodger's Achievements

0

Reputation

  1. Thank you both for your answer! Sorry I am a bit late to answer back. Since these things have a tendency to appear when deadline was yesterday, I opted for the quickest solution which was to limit the speed to where the problem is minimal. I also stops the animation before changing timeScale, something that seems to help keep timelines in sync. I will try to make a pen soon, since I find the problem interesting for other projects as well. It would also be great to get comments on possible better solutions to animate many objects along a path.
  2. Hi, Short version: I am trying to animate a set of electrons that move around a circuit. I use onReverseComplete to repeat when playing in reverse, but as the speed of the animation gets higher, the result is not good. Is there a better way to make the timeline repeat when using reverse? Longer explanation: My current implementation uses one timeline pr. electron with repeat: -1. All the timelines are basically the same, but the time of each one is offset, thus spacing them evenly around the circuit. The timelines are kept in an array which I loop through when i want to play, pause or adjust timeScale. This actually works great, even on mobile and even with the electrons moving insanely fast. The problem is that I need to reverse the animation at times and reverse animations does not repeat... In earlier animations I have done I have used a function onReverseComplete to set the time of the timeline to the end. In this animation setup though, it breaks down when the timeScale is high enough (starting at around 9 - 10). The different timelines come out of sync and the spacing gets uneven. At high enough speeds they start to clump together and I end up with just a few visible electrons. Any thoughts on how to fix it or better ways to do it? At the moment my solutions are either to reduce the timeScale to where the problem is negligible (not ideal, but quick to do) or to make a different animation that goes the other way and switch between them (possible performance issues, will probably introduce some new visual problems as well).
×
×
  • Create New...