opacity: distance from camera

[Darby Edelen]

[Jeremy Allen] “So where’s the catch? What am I missing to make this work right? I’m thinking it has something to do with nesting a 3d comp and trying to set the values based on the distance from the camera in the outer comp. I’m not real familiar with the whole “length” and “toWorld” stuff either, so maybe I need to tweak that too, not really sure.. “

When you use the toWorld(anchorPoint) function it will return the location of the layer’s anchor point in the local composition’s world space. So if you’re animating the pre-comp with transformations collapsed in the final composition then the positions of the layers never change relative to their position in the ‘world’ of the pre-comp.

One solution would be to animate the layers inside of the pre-comp instead of animating the pre-comp inside of your final composition.

Darby Edelen
Designer
Left Coast Digital
Santa Cruz, CA

[Jeremy Allen]

Also, is there a way to delete expressions from several layers at once? I know you can copy an expression, select several layers, hit paste and the expression will be applied to all selected layers. But can you delete expressions from several layers just as easily? If so, I haven’t figured out how yet..

[Jeremy Allen]

Thanks for the help Darby. It seems like that is exactly what is happening. It makes more sense now.. The initial values are assigned and it never updates because they aren’t actually moving in the local comp. Thanks for clearing that up for me.

However, the reason I was using the nested comp was so that I could move all the images easily instead of animating each one individually. Maybe I could parent all the pics to a null and move that inside the “pics” comp. But then I’d have to go back and forth between comps to make sure the positioning was correct.

Is there anyway to modify the expression to work with the setup I have now, or is that just the way it is?

[Darby Edelen]

The best I can offer for this problem is that ‘ee’ reveals all properties with an expression applied to a layer.

Darby Edelen
Designer
Left Coast Digital
Santa Cruz, CA

[Darby Edelen]

[Jeremy Allen] “Is there anyway to modify the expression to work with the setup I have now, or is that just the way it is?”

I can’t test this right now because I’m rendering, but this may work. You need to add in the offset of the pre-comp’s position in the final composition to the anchor point value:


C = comp("MASTER").activeCamera;
offset = comp("MASTER").layer(thisComp.name).position - comp("MASTER").layer(thisComp.name).anchorPoint;
startFade = thisComp.layer("opacity controller").effect("start")("Slider");
endFade = thisComp.layer("opacity controller").effect("end")("Slider");
d = length(toWorld(anchorPoint + offset),C.toWorld([0,0,0]));
linear(d,startFade,endFade,100,0)


I’m not sure that this code will work (I know it won’t if your pre-comp is parented to any layers in the MASTER comp, so unparent it first if it is), but its the right idea.

Darby Edelen
Designer
Left Coast Digital
Santa Cruz, CA

[Dan Ebberts]

Layer space transforms with nested 3D comps are always tricky (to me at least).

Try this:

startFade = thisComp.layer(“opacity controller”).effect(“start”)(“Slider”);
endFade = thisComp.layer(“opacity controller”).effect(“end”)(“Slider”);
C = comp(“MASTER”).activeCamera;
CL = comp(“MASTER”).layer(thisComp.name);
CL.toWorld(toWorld(anchorPoint));
d = length(CL.toWorld(toWorld(anchorPoint)),C.toWorld([0,0,0]));
linear(d,startFade,endFade,100,0)

Dan

[Darby Edelen]

[Dan Ebberts] “CL = comp(“MASTER”).layer(thisComp.name);
CL.toWorld(toWorld(anchorPoint)); “

I hadn’t even thought to check and see if it would convert one world space to another… Dan, you rock my world (space)!

Darby Edelen
Designer
Left Coast Digital
Santa Cruz, CA

[Colin Braley]

[Dan Ebberts] “Layer space transforms with nested 3D comps are always tricky (to me at least).”

Dan, if they are always tricky for you they are definitely always tricky for the rest of us.

~Colin Braley
http://www.colinbraley.com

[Jeremy Allen]

First up, thanks to both of you for your time and patience. I really do appreciate your help. However…

I tried both of the new solutions and strange enough they both seem to do exactly the same thing. They both seem to work at first, but then as I scrub through the timeline, the opacity values only change 3% from far to near. So the furthest pic starts out at 12% and only goes up to 15% at it’s closest point to the camera. So at least the values are changing but not as much as they should be.

Am I trying to do something impossible here? The code makes sense to me and it seems like it should work, but something just isn’t right. Should I just put a camera in the pics comp and do it that way? I get the feeling that this won’t work at all if I parent the pics to a null for easy animation.

[Jeremy Allen]

Thanks for that tip Darby. I did figure this out: If you shift select all the layer properties that have expressions applied, and then option click on the stopwatch for that property, it will delete the expression for all the layers.

For example, you have 20 layers with expressions on Opacity. Click on layer 1 opacity, then shift click layer 2 opacity…keep going through all the layers. Now option click the stopwatch for layer 1 opacity and it will delete the expressions for all the selected layers. But you have to select the layers by the properties, it won’t work if you just select the layer names.

You probably already know this, but maybe it will help some others who don’t 🙂