[Darby Edelen]

Is there a texture applied in the Color channel as well? That would overwrite the chosen color.

Darby Edelen

[Darby Edelen]

This might be worth checking out:

https://www.plugins4cinema4d.com/rboole.html

It performs a boolean at render time and shouldn’t create the horrible topology that the standard C4D Boole object does.

It will only work with objects that have materials applied (it uses the materials to render the boolean).

Darby Edelen

[Darby Edelen]

Is there some reason you can’t simply use keyframe animation?

Darby Edelen

[Darby Edelen]

Usually that indicates that those attributes are selected. Cinema may be confused.

Darby Edelen

[Darby Edelen]

The short answer is that a half second delay between layers is a large delay when the wiggle has a frequency of 3. Try a delay of 0.1 or 0.05 instead.

Darby Edelen

[Darby Edelen]

[Adam Tanner] “The expression I use works great for changing the color of a fill on a solid, but I’m not sure how to make it deactivate the fill and add a ramp. Any ideas?”

My suggestion would be to only use the Ramp. Use a Tint effect after the ramp to re-color the ramp as necessary. If you set the “Map Black To” and “Map White To” outputs of the Tint effect to the same color you’ll get a solid color fill.

Darby Edelen

[Darby Edelen]

I see now that you have the layer that should be changing color in a pre-comp. I’d approach this differently in that case.

In the pre-comp trim the gray layer so that it exists at 0 seconds and ends before 1 second, then place the green layer so that it starts at 1 second.

Instead of applying an expression to the opacity inside the pre-comp, enable time-remapping on the pre-comp in the main composition and apply this expression to the time-remapping:

if(toCompVec([0,0,1])[2] > 0) 0 else 1

You can change the place of the 0 and the 1 if the layers are appearing in the wrong order.

Darby Edelen

[Darby Edelen]

Delete everything in your “try{}” statement and only keep the code in your catch():

if (toCompVec([0,0,1])[2] > 0) transform.opacity else 0

Darby Edelen

[Darby Edelen]

[Tayler Ursu] “if (toCompVec([0,0,1])[2] > 0) transform.opacity else 0”

That doesn’t do what you want?

It’s not clear what you’re trying to do. I assume you want the layer to be invisible when its back faces the camera, and that’s what the above quoted code should do. Everything in the try{} statement seems superfluous but perhaps you’re trying to do something more. I can’t tell what that would be from the code though, could you provide more detail as to what you’re trying to achieve?

Darby Edelen

[Darby Edelen]

Generally I’d use one of the built-in functions like posterizeTime() or temporalWiggle() to do this but it sounds like you have a very specific behavior in mind. Here’s one way to do what you’re asking, applied to the Time Remapping property (could be adapted for Timewarp as well, but I prefer Time Remapping):

min = 1;
max = 5;
step = 3;

min /= step;
max /= step;

f = timeToFrames(time);
t = 0;

for(x = 0; x < f; x++){
seedRandom(Math.floor(x / step), true);
t += random(min, max);
}

framesToTime(t);

The above will vary between moving forward ‘min’ and ‘max’ frames every ‘step’ frames. So in the code above every 3 frames the footage will vary in speed from between 1 frame per 3 frames and 5 frames per 3 frames.

Here’s another possibility:

step = 5;
seedRandom(Math.floor(time / framesToTime(step)), true);
posterizeTime(random(12, 24));
temporalWiggle(.5, 1);

The above uses temporalWiggle() to change the rate at which the time remapping value animates (speeds it up or slows it down). Because temporalWiggle() is a very fluid speed change it also varies the frame rate randomly between 12 and 24 fps every 5 frames.

Note: the temporalWiggle() function can cause the footage to move backwards if the amplitude (the second value) is set too high relative to the frequency (the first value).

Darby Edelen