[Mio Tanaka]

Thanks for the concise yet really helpful step by step guides!

I’ve tried the technique and it’s looking good.
I will try finessing it and I might need some help. Will post again if that’s the case.

Thanks again!

[Mio Tanaka]

Hi, Thanks for your advice. I tried adding some bump, but it didn’t work. I shifted the position of close objects, so it wasn’t the cause either. I ended up exporting a pass for the screen.

[Mio Tanaka]

Hmm, interesting. As seeing your comment, probably it’s not as useful as layer index numbers… I’ll study more about expressions. Thank you, Dan!

[Mio Tanaka]

My mistake. What I meant was, I thought there’s no way to access Transform by using an index number, since the script gave me these. For Fill there’s (3), an index, whereas there’s no number for Transform. I hope I can get it across.

transform.rotation:
(“ADBE Vector Transform Group”)(“ADBE Vector Rotation”)

fill.color:
(“ADBE Vectors Group”)(3)(“ADBE Vector Fill Opacity”)

[Mio Tanaka]

I’ve tried the script and got these:

transform.rotation:
comp(“tree 2”).layer(4)(“ADBE Root Vectors Group”)(1)(“ADBE Vector Transform Group”)(“ADBE Vector Rotation”)

fill.color:
comp(“tree 2”).layer(4)(“ADBE Root Vectors Group”)(1)(“ADBE Vectors Group”)(3)(“ADBE Vector Fill Opacity”)

It seems there’s no index number for Transform and there’s no way you can access a transform property. But then again, why did the rotation gave me the value 3 in the image I posted…? Are there invisible two values before Transform?

[Mio Tanaka]

Dan, thank you for the reply again.

I tried using prop.propertyGroup(2).numProperties, and actually it says the correct value, which includes Transform property I was talking about.

But then again, when I used this to get an index value, it’s a short value by one…

value = thisProperty.propertyGroup(1).propertyIndex

Since it’s quite likely I’m misunderstanding something, here is the screen shot. Maybe you can see why…

[Mio Tanaka]

Thank you for the reply. I learnt a few more new things and I’ll check the script!

Hmmm, I guess my explanation wasn’t good enough. Let me explain it again.
What I meant was, by using ‘.propertyIndex’, each property’s index is like this:

▼Group
▾Path 1 —index 1
▾Fill 1 —index 2
▾Transform —index 2

Or if there are properties like this…

▼Group
▾Path 1 —index 1
▾Path 1 —index 2
▾Fill 1 —index 3
▾Transform —index 3

You can see the Transform’s index is the same as the property above’s, and I wonder if there’s not index number for Transform property at all.

Thank you,

[Mio Tanaka]

Thank you so much for them!

[Mio Tanaka]

Thank you, Darby and Dan, for the expressions.
Both worked perfectly and did what I wanted.
And I’ll look into the methods you two used and learn about it.

[Mio Tanaka]

Yes, it seems to be just a coincidence…
Thank you for the clearer and wiser expression.
It looks much more flexible.