[Mark Doctor]

I am always surprised that the AE community didn’t split immediately after eliminating the CS series. I suspect it will take some time until more users will see the benefit of actually owning the software.

Especially when more and more users can not keep up the pass. Even worse, renting CC to see your own old projects, means that you don’t own your projects or backups! CC being a ransomware taking hostage of your projects.

I guess and hope that the CS community will grow automatically and develop its own resources. This means that Adobe will be cannabalized by its own legacy, forcing them to create beter alternatives.

[Mark Doctor]

How about using the vanishingpoint from photoshop? It can be imported to AE. It has the same look and feel as camera-projecting.

[Mark Doctor]

Try searching for an animated flag tutorial and use the displacement map tool?

Greets Mark

[Mark Doctor]

Can you make a screenshot from your memory usage when a crash occurs?

Greets Mark

[Mark Doctor]

Its the oldskool methode, of stagging a bunch of text layers at a z-space offset.

Create a textlayer and add an index-scipt to offset the anchor z-space:

A = thisComp.layer("YourtextlayerName").index;
B = index;
C = B - A;

Duplicate the layer ~40x times and every duplicated layer will have its own unique z-space. Which in return also can be used for hue, saturation, opacity, etc. Combined with a slider to increase the magnitude, by multipling the “C” value. In this case I would sugest the solid overlay effect and add the script to the opacity.

[Mark Doctor]

Try this:

[Mark Doctor]

It works! Thank you for your time Dan ????

[Mark Doctor]

Solved! Key-framing a null wasn’t an option; The null would need a key-frame at every frame just like the camera, to keep up with the background parented to the camera.

//3D point expression:

A = thisComp.layer("BackGround");
AW= A.toWorld(A.anchorPoint);

//vector expression:
A = effect("Point A")("3D Point");
B = effect("Point B")("3D Point");

//vector to B
C = B - A;

// 1% vector
D = effect("Slider Control")("Slider")*C/100;

// point A & vector added
E = A + D;

[Mark Doctor]

As to fixing the problem for your project – is there a reason you can’t move the light farther back, or put the image layer closer to the white?

My suggestion would be to scale no smaller than 50%, and place the light and image as needed to accommodate that (or larger) scale. Alternately use a parallel light, though that might not work for the rest of what you are building.

The whole thing is a bit more complex. I have a footage that has been camera tracked and is constantly being mapped to different white solids at the right perspective from different positions. This enables me to move around with a secondary camera close to the position of the “real-world-tracked-camera”. In this scene we also find a 3D shape

The reason for the second cam is to zoom and shift the point of interest of the real-world-cam towards the 3D layer. The 2D solution of Just scaling the whole composition and animating the anchor-point, disables the “continuously rasterization” for the 3D shape and wasn’t acceptable because of the extreme zoom.

I’ve dropped the camera-mapping because the projected slide intersects with the white solids. So I’ve turned the footage in a large 3D-layer in the background parented to the real-world-tracked-camera and kept the second cam for zooming. Loosing the options of a dolly towards the 3D-shape, depth of field and more accurate reflection mapping.

[Mark Doctor]

Hi sorry for lacking this information, but I didn’t use any camera in this demo its the custom view of AE.
I just duplicated the comp and the ray-traced version uses the exact same light en doesn’t offer any extra settings that I can show (i also couldn’t make it fit my screen whiteout loosing more vital information).

I tested some other scenario and it seems that ray-tracing can’t cast sharp shadows either!?