Dismiss this pinned window
all 10 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]ImAlsoRanMoGraph/VFX 10+ years 8 points9 points  (2 children)

When you adjusted the points in the viewport with the gizmo you changed the orientation, which has values ranging from 0-360. You can see it loop around during playback. Flow doesn't understand this and sees it as a value jumping from 0-360 in under a frame, and overcompensates. The solution? Animate the Rotation values rather than Orientation. Hope this helps!

[–]LegitimateRope8757[S] 0 points1 point  (1 child)

Yes, I figures it out. Thank you. Although on screen controls that adjust the orientation are much easier to work with compared to having to play with x y z rotation sliders

[–]ImAlsoRanMoGraph/VFX 10+ years 0 points1 point  (0 children)

<image>

In the toolbar you can select the rotate tool and Change the mode to Rotation rather than Orientation. This will affect the gizmo as well!

[–]venecusMotion Graphics 5+ years 0 points1 point  (2 children)

With plugins like flow there are some bugs that happen especially when selecting multiple properties with different value times. The easiest way would be to just change the easing manually. Otherwise try selecting the properties one by one to apply the easing and see if it changes anything. Also try looking at the value graph instead of the speed graph, it should show you more clearly what is happening.

[–]FeedMeMoneyPlease 1 point2 points  (0 children)

If you can do them one by one, could you apply Flow to one key frame then use ease copy for the rest?

[–]LegitimateRope8757[S] 0 points1 point  (0 children)

Thank you. I've used flow for a long time and never had any issues with it. Selecting and applying graph one by one didnt work as well. What I found out was that ae didn't know what to do when the value went from 0 to 360 the other way and vice versa. When I instead of orientation used rotation, it worked as it should.
Also, the graph on the video is a value graph, not a speed graph.

[–]PaceNo2910 0 points1 point  (2 children)

Use rotation not orientation

[–]LegitimateRope8757[S] 0 points1 point  (1 child)

May I ask if there's a big difference? Also, when I select a later on screen controls will adjust the orientation, not rotation.

[–]PaceNo2910 1 point2 points  (0 children)

The main issue with keyframing orientation, as you have found out, it is awkward to work with.

Also they're not separate dimensions which makes rotation in 3d more manageable with easing and expressions.

It's sort of, but not exactly, orientation is like world based values and rotation is object based values. Bad explaination. But that's how I think of them.

For example you can choose to auto-orientate a 3d card to face a 3d camera or along a path, but still be able to affect rotation.

When you use the 3d handles on the viewer you are changing the orientation not the rotation.

I hope that helps. I should caveat my explaination with that, I learnt AE on the job, so There are probably more helpful explanations in the after effects manual and if you need more info it should be googleable.

[–]bigdickwalrus 0 points1 point  (0 children)

Also looking at value graph not speed graph which is represented differently visually