Hi let-fall,

Thanks for your time. The idea was just to describe what doesn't work and what makes it work—a few lines.
Just enough that the developers can reproduce the problem and solve it for anyone who needs to work in version 2024.

But, so far, I can't find any entry of a reported problem that would match your findings. Since it was with 2024.4.1, which was not the latest of 2024 releases, let's see if anyone has troubles with 2025, and it will soon be no problem for anyone.
You found a workaround, so let's close this thread. Thanks for your reply.

All the best

Hi let-fall,

Thank you very much for the file and using Wetransfer.

The overall size is not changing; only the growth is. The object is "normalized" and then brought into the UV space (A normalized space 0-1).
When an object grows over time, the normalization will eliminate the size but not the internal growth, as in your example.

How to overcome this?

I have placed a Disc into the mix, whereby I deleted the Polygons while holding the Shift key to keep the points.
These points define the largest growth of the ornament. With this, the normalization is based on the points; what is inside the points is not important for the normalization.
Now, we can see the "ice crystal" grow, and we have no counterproductive normalization working on it.

Here is your file back
https://stcineversityprod02.blob.core.windows.net/$web/Cineversity_Forum_Support/2023_PROJECTS_DRS/20231208_CV4_2024_drs_23_ANsd_01.zip

My best wishes

Hi let-fall,

You're very welcome.

Please have a look here:
CV4_2024_drs_23_XPor_01.c4d

Cheers

Hi let-fall,

Thanks for the reply.

I needed to make it clear, as some scripts might harm users. This is not to say that I found the one to be questionable - again I do not even look into these. I do not take care of those; that would put too much on my plate. Anything coded and shared via link could be hacked or exchanged, altered after a while. Like any application running on open source, something I would not touch for a professional pipeline at all, as long as I don't know exactly what is going on. Thank you for understanding.

Cheers

You're very welcome, let-fall.

I'm glad we have the little helper tools to create things on the fly.

Please let me know if there is something else you need to connect parameters among the cameras.

Enjoy your weekend

Thanks for the feedback, let-fall.

To see how much parts of the scene slow down the scene redraw, go to Attribute Manager> Mode> Viewsettings> HUD> FPS.
This will provide a little entry in your editor-view while the play head is moving.

Please let me know the frame range where it is not to your liking. That was not clear in your drawing, which I appreciated having, BTW. Thank you!

For blocking the camera, it is often better to have a "Stand In", like a cube or capsule, animated similarly.

Speeding up a camera with position and rotation in it means you might lose the target out of sight. You could have a Target (perhaps with an Up Vector) Null animated close to your character to prevent that. With that, your precise animation path (position only, switch off all rotation tracks of the camera) can so be easily adjusted with a Time Track.
https://help.maxon.net/c4d/2023/en-us/Default.htm#html/10834.html

Another point that needs to be considered is the change of field of view, which is often used by complex shoots; If the camera motion is sped up, that might go out of sync.

Which is a straight line from 0 to 100% to have nothing changed. But if you set it up like an S-Curve, the more vertical part speeds up the camera, and the Target keeps the Object. Again that will not work if Position and Rotation are sped up simultaneously.
(As a side note, that is also a theme in next month's ASC [American Society of Cinematographers] magazine, the article about John Dykstra. There, the motion/motor-based camera.)

All the best