[Cesar Siena]

The project alone, without the assets, wouldn’t be enough for this, but I thank you very much for all the help! Kind regards

[Cesar Siena]

Thank you for replying.

Feedback

It worked(!) in 3D Head’s “X rotation” and “Y rotation” using the following command (last) lines below, but it didn’t work in “Z rotation”.

Small issue

The head gained a little twist when the expressions were applied, in a way that, to correct head’s position, the 2D null had to be dislocated far from the screen’center (in other words, I didn’t manage to center the 2D null after that – any ideas?)

The 2 expressions that worked were:

IN THE X ROTATION OF THE 3D HEAD
nullLayer = comp(“Comp2”).layer(“2D_null”);
xyz=thisLayer.fromWorld(nullLayer.toWorld([0,0,0]));
x=xyz[0];
y=xyz[1];
y

IN THE Y ROTATION OF THE 3D HEAD
nullLayer = comp(“Comp2”).layer(“2D_null”);
xyz=thisLayer.fromWorld(nullLayer.toWorld([0,0,0]));
x=xyz[0];
y=xyz[1];
x

IN THE Z ROTATION OF 3D HEAD
— DIDN’T WORK —
nullLayer = comp(“Comp2”).layer(“2D_null”);
xyz=thisLayer.fromWorld(nullLayer.toWorld([0,0,0]));
x=xyz[0];
y=xyz[1];
z=xyz[2]
z

IN THE Z ROTATION OF 3D HEAD

— WORKED —

simple pickwhip to 2D null’s rotation, without any layer transforms between different comps of different dimensions.

I already read Adobe’s information about lookAt and watched tutorials, but I presume that Java Script knowledge is necessary to fully understand that. I have also tryed fromComptoSurface with no results.

These are common doubts even of experienced animators. Maybe Adobe could improve it’s explanations and examples about it.

Any ideas to correct 2D null’s position described above?

Thank you very much, Filip! Best regards!

[Cesar Siena]

Thanks, Roei! Best regards

[Cesar Siena]

Thanks, Walter. This is a relief to avoid day-dreaming with utopic machines.

[Cesar Siena]

Thanks, Walter. The small educational oriented studio already works with plenty of RAM and SSD. Nowadays, even a NVMe disks RAID is affordable. The issue continues to be performance along the project (RAM preview). I remember an Adobe video on performance recommending 2x ou more Xeon. The video presented a machine with 32 cores (or threads?) and the host (presenter) worked flawlessly in real time. How do you manage that?

[Cesar Siena]

This is wise, Dave; I learned with you, experienced Ae people, doing that in the last years. The real delay is RAM previewing several times during the work, which can’t be postponed.

[Cesar Siena]

Interesting advice! Thanks!

[Cesar Siena]

No. I work on non-profitable educational Ae projects with CS6 in one environment/work place, in which there’s no budget for montly subscribing, but the machines will be updated. We don’t know if updating them with threadripper will work well with CS6. Although there are 3D programs there that will certain respond well, most of the work is done with Ae, so the hardware update will have to consider that. i7 8700 seems no future proof regarding new multi-core tendencies.

[Cesar Siena]

Thanks, Dave. I was looking for a non monthly paid alternative to work with legacy projects, with new equipment. I didn’t find tests with CS6 using newer chips. Thank you!

[Cesar Siena]

Thanks, Walter. I was looking for saving money when working with older projects in new renderings, with new equipment. CS6 would be a non monthly paid alternative, non third party workaround. I didn’t find tests with it using newer chips. Thank you!