Thanks for the reply, Cit,

Yes, the Field Driver is very useful and versatile.
Please let me know if you have any questions about Joints, Fields, and Field Driver.
Please feel free to open a new thread at any time when the subject changes so it is easier to search and find.

My best wishes

Hi resort-sand,

Thanks for the files, and for using WeTransfer.

To get it smaller and smaller requires that the Length and the height of the words shrink equally. Which would also move them. This is not an option with MoGraph.

My suggestion would be to solve this with 3D and perspective.

https://projectfiles.maxon.net/Cineversity_Forum_Support/2025_PROJECTS_DRS/20250120_CV4_2025_drs_25_TXnf_01.c4d.zip

The setup has a little "cheat" with a Taper Deformer to improve the flow.

To see the full text, it needs to be rendered. The small text on the end requires at least a 16K render, I assume more.

The setup is a balance of camera distance, the field of view, and the Length of the Helix. The light on the camera has no falloff!

My best wishes for the project

Hi philosophy-chemical,

Thanks for your care. Yes, that is reported since a while and I have no idea why this not fixed. Sorry.

Typically, there is a strong connection between Apple and Maxon. If I have a chance to find someone who is not aware of that, I will make sure this is known.

If you have the impression that the developers need an extra nudge, please use the "Share Your Ideas" option here:
https://www.maxon.net/en/support-center

Or open a Tech Support ticket, which might be the better way. This is the official way to report technical problems and get help if possible.

Cineversity is more of a how-to or creative problem-solving platform; I cannot fix code here. Hence, we have the feature request or tech support option.

Thanks for understanding.

Enjoy your Sunday Evening.

Hi Cit,

Noise is, by definition, random, and yes, here and there, a noise algorithm might show repetition (tile-able). In the Noise Node of XPresso, I'm unaware of a "tile-able" noise pattern option.

The frequency is a parameter of how fast the point is moved inside the noise field to evaluate a certain position in the noise pattern.

How random would a value be the same every 24 or 30 frames?

To make this work, we can go different ways.

Example one, explores a Spline interface that is set up randomly. The Time> Frame provides the values that will be used to get the value of the spline, as the spline can have only one X and Y pair, creating a value.
CV4_2025_drs_25_XPnl_01.c4d

The second example moves the noise and arrives at the same point in frame 30, while the F-Curve Editor> Function> Track After> Repeat is enabled for a loop after the first 30 frames.
CV4_2025_drs_25_XPnl_11.c4d

The third one cheats the Noise Node into a repeated value after 30 frames by just lowering the Amplitude to zero. The Repeat option in the Timeline is active here again.
CV4_2025_drs_25_XPnl_21.c4d

I hope one or the other will work for your project.

Enjoy your Sunday!

Hi piece-quality,

One favor: If the theme changes, use a new thread for the next questions. Thank you.

Otherwise, any search in the forum is difficult, as threads are mixed, and finding the information people like to have is hard.

The Volume System does not have a UV system that follows changes. UV is based on the Polygons of the Mesh as the initial source; if the mesh changes, the UV information from the previous state is not the same.

If the texture is more about colors, perhaps a Vertex map might help. However, since the changes are not connected (frame-wise), there is typically no option to produce any default motion blur.

If you open a new thread, please share a simple Project file with your idea. (Images typically do not tell as much as a project file)

The Triplanar Node might help, even though I doubt it's useful here. However, this is a wild guess since I don't know much about your setup.

Enjoy your weekend

You're very welcome, guarantee-topic.

Have a great weekend.

Thank you very much for the file and using Dropbox.

The eyes and nose are on a surface area that is 100% weighted to the head joint, making it easy for the joint to be the "Driver" or Target for the Constrain Tag.

All Joints have Constrain Tags, here typcially with a Priority of Expression 25 or 26.

Going by the head joint, its priority is 25, the Constraint for the eyes and nose could easily work with Expression 26.

If you later on use the Priority Shift on the rig, this value needs to be adjusted accordingly. Which might be forgotten to do, and spotted later after rendering. My suggestions would be in this case, use Expression 100.

There are a few rules about priorities, like the object manager top-to-bottom process.
On top of that is a possibility for priority setting.
If the data has not been produced before (based on priority hierarchy), then the data is used from the frame before. This might not always show up in the editor view, as it has several refresh cycles while working; during rendering, there is a one-time calculation along each frame; once and all Priority Problems show up.

More in depth:
https://help.maxon.net/c4d/2025/en-us/Default.htm#html/TCACONSTRAINT-OBASELIST.html#EXPRESSION_PRIORITY

Enjoy your project

Sounds good, leininger609.

My best wishes for your project

Thanks for the reply, leininger609.

My understanding is that the particles are stored normally in the graphics card (GPU), hence the speed.
The Tracer works on a CPU level.
To get the Tracer working, the Particles must also be on the CPU level, which causes the one-frame gap.

You can see that when you switch off the option to download (or copy) them to the CPU:
Attribute Manager> Scene> Simulation> Particle> Download : off

No Tracer will be created from the Particles, as no download is provided.

The suggestion from above, caching them, downloads those and has the particle values available at the very beginning of the frame-based calculation. If stored on an SDD with a fast access time, you might not even feel a difference; in complex setups, it might be even faster.

I hope that provides the needed insights and allows you to improve your project file as much as possible.

Cheers

Hi leininger609,

The Tracer has to be below the Partilce objects, Priority-wise. I assume that is set up already.

The particles are produced, and the Tracer is a frame behind them, which can be fixed by caching the Particles (Particle Group has the option).

Cheers