That's pretty much the problem. I have a Mover that I need to have 35 frames on a ConstantLoop, but it never loops. After going through the series of frames, it just sits on its last frame, and never returns to frame 0. I've done some tests, and it works just fine if NumKeys is set to 23 or fewer. Does anyone know why this is happening?
-
-
hmm never tried anything this long, such a lot of work! One workaround could be to devide your loop in half and have an identicle mesh as mover#2 pop up while your mover #1 pops down, triggered by closing event from mover#1 -
Hmm... I like that idea, but when I tried it, mover#1 didn't pop down, and mover #2 didn't pop up. They just drifted down and up; it was very obvious. Any more ideas?Comment
-
well do the opposite of the default movement type - I think default is glide by time. Its OK to have both movers occupy the same space btwComment
Comment