rotating a layer in 3D – AE is no good?

[Andrew Kramer]

Try changing the axis mode next to the tool bar on the right. See if this solves your problem.

Andrew Kramer

[Steve Roberts]

I don’t think that’ll work. It seems that changing local/world/view axes only works when using the rotation tool, not when scrubbing or setting the numerical values in the timeline. In other words, the rotational and orientational values in the timeline always use the world axis, and they reflect the calculated world axis result obtained by using the W tool to rotate in the other axes. Which is why a simple W change of the local axis results in a complex change to the values in the timeline: they’re always world axis values.

This makes sense from one point of view: there needs to be one set of values for the program to use. However, from a useability standpoint, it’s a bit of a problem.

What we need (in the short term) is an expression to convert things, I suppose. Dan? 🙂

[Michael Becke]

Thanks for the feedback Steve, I thought there might not be an easy workaround… maybe we’ll get an insightful post 😉

Thanks again,
Michael

[Michael Becke]

Thanks for the feedback Steve, I thought there might not be an easy workaround… maybe we’ll get an insightful post 😉

Thanks again,
Michael

[Sam Moulton]

Try changing the Z orientation then rotate on X and it will work. it would be nice if there was a way to change the render order like you can do in card dance so Z would render before X but as it is the order is orientation, x, y, then z. that’s why you have to use orientation

[Tobias Pfeiffer]

AE was the first program with 3d capabilities i used. because of this behaviour i thought im to dumb to understand and to orientate well in 3d space…i was wrong.
fortunately maya lets you choose what kind of axis you want to edit (local or world).

we need a fix or workaround for this.

mylenium or dan should read this 🙂

payton

[Mylenium]

[Michael Becke] “> First of all I think this is stupid, but most importantly it’s hampering my abilities to link the rotation values to a null object.”

Mmh, not sure what you mean. From my POV you’re simply going about this the wrong way. You’d have similar problems in a 3D program. Parent the layers to a Null and rotate the Null along Z, the layer itself along X.

Mylenium

[Pour Myl

[Mylenium]

[payton] ”
AE was the first program with 3d capabilities i used. because of this behaviour i thought im to dumb to understand and to orientate well in 3d space…i was wrong.
fortunately maya lets you choose what kind of axis you want to edit (local or world).

we need a fix or workaround for this.

mylenium or dan should read this :)”

Nope, actually this behavior is consistent even in most 3D programs. It only works in Maya and Houdini this way because a transform is an independant property/ node from the actual object/ item. Other programs like Cinema4D or Lightwave don’t take any precaustions to prevent this kind of gimbal lock (though at least the differentaition between local mode and world mode works).

Mylenium

[Pour Myl

[Tobias Pfeiffer]

good to know, thanks.
i thought every 3d package works this way.

i definitely prefer the maya way.

payton

[Mylenium]

[payton] “i thought every 3d package works this way.”

Unfortunately not. Most apps store their data as Euler world rotations and only dynamically translate them to local rotations when you select a tool that works with them or enable a global scene mode. Maya is pretty unique in this. It even allows you to have multiple pivots and transforms per item.

Mylenium

[Pour Myl