Hi bet-beach,

Yes, Cinema 4D is very flexible and versatile. Thank you for that.

Thanks for the Google files.

The UV-based movement (Distorter) can only push a single pixel in x or y (red or green), or just gray values, and then based on the distorter's global settings. To follow a brushstroke while the brush is rotated means to put the image on the head at one point, which might be possible, but I assume it would take a lot of developing time
https://help.maxon.net/c4d/2025/en-us/Default.htm#html/COM_REDSHIFT3D_REDSHIFT4C4D_NODES_CORE_DISTORTER-COM_REDSHIFT3D_REDSHIFT4C4D_NODES_CORE_DISTORTER_GROUP_0.html#COM_REDSHIFT3D_REDSHIFT4C4D_NODES_CORE_DISTORTER_INTYPE
Perhaps I miss something, as ideas often come with a new problem, but here I'm not clear how to follow that brush in any direction, what rotating (or broom in your video)

I found it easier to explore particles here, as that is what comes closest to dirt. Here are two sketches.

CV4_2025_drs_25_PAcm_01.c4d
CV4_2025_drs_25_PAcm_02.c4d
The Delay needs more attention.

The other way would be to set the animation brush (or broom) and render it from top view. Then "smear" in Photoshop along the path. If the brush crosses its own path, the next image is needed, based on the one just smeared (Smear Finger, 80-90%). Those images are then layered and unveiled with a vertex map, set decay to 100%, meaning nothing decays.

I hope that helps for your next meeting.

My best wishes

Hi bet-beach,

Please have a look here:
https://projectfiles.maxon.net/Cineversity_Forum_Support/2025_PROJECTS_DRS/20250910_CV_2025_drs_25_ANsm_01.zip

I would work with a very fine Noise to "diffuse the texture", here I used the colors first to set the texture apart, the noise can then move it in a way that diffuses it at the same time. Use the "Redshift Render View" and press play.

Check the values in the Distorter, to get more or less effect.

Perhaps you like to have the initial state undistorted and work with colored noise. Explore what fits best with your idea.

Please know, for security reasons, I touch only a few standard cloud services (WeTransfer, Dropbox, Google, Apple, and Adobe), hence I worked from your image only.

Please let me know if there are any questions. I'm happy to look into those.

Enjoy

Hi MaverickMongoose,

Thanks for the reply

Yes, from your perspective, but sometimes it might be useful to have the initial state as well.
I agree that the decision should be a checkbox and not require extra steps.

Enjoy your project

Hi MaverickMongoose,

Feels like something is using the Cloner state, not the Rigid Body results. If something is stuck, I typically start over in a new Project file to gain more insights. Thanks for the effort with the mp4!
However, the Constant Update is not checked.

Let's take another approach:
The Matrix Object, in Object and Axis mode, pulls current data, including the Rigid Body state. The colors can be set in the same way.

Example
CV4_2025_drs_25_MGvc_11.c4d

Please explore the option to mix the color (Vertex>Fields> Layer Control> Mode> Average, as well as Radius)
Example
CV4_2025_drs_25_MGvc_12.c4d

Of course, you can feed a new Cloner from the Matrix and use that result in the Volume. (Cloner 1> Matrix>Cloner 2)

Enjoy your Sunday

Hi MaverickMongoose,

Thanks for the images. The colors show that the Volume vertex map uses the Cloner colors without the Rigid Body "take over".

Caching the Rigid Body only works for me.

With cache and a rendered preview.
https://projectfiles.maxon.net/Cineversity_Forum_Support/2025_PROJECTS_DRS/20250906_CV4_2025_drs_25_MGvc_02.zip

Cheers

Hi MaverickMongoose,

Thank you for the file, and for using WeTransfer.

Switch the Ridge Body off, then have a look at where the Spheres are. With the selection of the nearest, these colors are exactly what you get.
Now switch the Rigid Body on and cache it. Now the information is available when the Vertex map takes it from the Cloner.

Let me know if that works for you.

Enjoy your weekend

Hi David,

There are no mistakes, only gained experience.

Enjoy!

Hi David,

Thanks for the feedback,

The material that uses the Selections to work only on the "small sides" of the object can be "dimmed" down in the Emission Settings, set the Luminance down (or in other materials, that is the weight parameter.
Transparent and immutable, it is both; it is a balancing act.

Cheers

Hi David,

Thank for clearing which one it is.

Please have a look here, it is a combination of setting RS Open PBR node> Geometry Thin Walled and using a Ray-Switch Node. Disable one or both, if you like to have both ends "luminescent".

CV4_2025_drs_25_RSng_21.c4d

Is this coming closer?

Enjoy your weekened

Hi David,

You're very welcome, and thanks for the reply.

A lot of information about Polygons are here:
https://help.maxon.net/c4d/2025/en-us/Default.htm#html/DMODELING-MESH_CHECK.html#MESH_CHECK_POLY

Call up a Polygon Object, set one side to 0cm, press "c", and check it. That is a bad polygon , often they are just produced with no influence to the visual results. IF so, you can select those with the Mesh Checker, and delete them.

Since there is typically no scene information on how they should be done correctly, repairing is a artist decision, not based on rules (DTDT, do-this-do-that).

I hope that helps a little.

Enjoy your weekend

Hi Dylanplsss,

Here is a simplified idea.

In short, the "taiyaki" doesn't come out of the machine; it is already in the Holder, but up and invisible. Then becomes visible and last will move into the Holder.

Please have a look here:
CV4_2025_drs_25_MGan_01.c4d

This works by defining three states. At the same time, blending those in the Cloner.

To trigger the change, go to Cloner > Clones > Blend, and then Plain Effector > Parameter > Modify Clone.

This moves the "taiyaki" as well, which can be adjusted (in the example the Sphere - taiyaki's proxy) is different in P.Z. So it feels like falling straight down.
This P.Z setting depends the hight from start to arival in the holder. I found it easy to adjust when a huge number of clones is created.

I have animated the process to showcase it:
CV4_2025_drs_25_MGan_02.c4d
On frame zero, change one of the four (yes, I changed the number to demo the workings more clearly) P.Z values to see how it change.

However, it avoids many minor details that would be necessary to synchronize such motions.

Enjoy your Weekend

Hi Dave,

Would this technique help? (Or do I miss what you like to have: Neon-plastic has that light on cut edges, see P.S.)
https://www.youtube.com/live/j0UBCJ1dQXo?feature=shared&t=1340

Typically, the fastest way would be a Post FX> Bloom, but it might affect other areas to look natural, which is perhaps not wanted.
CV4_2025_drs_25_RSng_01.c4d

Let me know if that works for you.

My best wishes for your project

P.S.: CV4_2025_drs_25_RSng_11.c4d

Thank you for your input and reply, atomician.
Enjoy your project.

My best wishes

Thank you very much for your tremendous patience and understanding, draft-buddy.

Your input has lead to a report, and I hope it is solved quickly, without your input… So, thank you.

My best wishes for your project.
.

Hi atomician,

Float here is any single number (vs. Vector or Matrix). You can "pipe" in, even Boolean values. Think of it as a family name used in Cinema 4D for numbers. Internally, it is changed to a "real" float.

The User Data interface might provide a good hint at how it is used. Float the group name, units for the evaluation what the input is.

The term Float is used (for example) for image formats, like the industry standard OpenEXR, whereby the numbers used here are exponential numbers, but also with such formats, no image or compositing app to my knowledge requires placing exponential formatting into the parameter fields to even change a single pixel.

The input in Cinema 4D is anything when set to float, single parameter for Real, or three for Vector, or 12 for Matrix. Each time it accepts Real, integer, or even other number-based data (Again, Boolean, 0 or 1 for false or true). So, I can't even see remotely a limitation here.
Example:
CV4_2025_drs_25_XPpn_02.c4d

Here is the manual: Float is not listed, just real
https://help.maxon.net/c4d/2025/en-us/Default.htm#html/5829.html?TocPath=XPresso%257CXPresso%2520Editor%257C_____0

You can report anything you like to Maxon, but you are the first in a few decades you ask me that. I do not see that this would trigger a change through the application; all documentation and the change would require recording all tutorials that newly use this term in the way it was used. Changing it now might be a very confusing change, given the tens of thousands of YouTube tutorials that might have it somewhere. I consider this an app-wide agreed understanding since the '90s. Yes, float as a term might be misleading, but when you set up a variable in Python, the first value provided defines the Variable, no labels needed.

All the best

Thanks for taking the time to reply, lawyer-platform.

If there is anything else, I'm happy to look into it.
If it is a new theme, please open a new thread. Thank you.

Have a great day!

Hi lawyer-platform,

Just checking in, seeing if you got what you need.

Cheers

Hi Tamin8r,

In the moment, all objects are treated by the same SDS; those are generated newly and seen as one object. The only way that comes to mind is to have the object that needs a separate light needs to have its own SDS.

Sorry, I searched for other options, but I'm not able to solve that. I assume that using the material Emission channel is not wanted here.

All the best

Hi atomician,

Yes, that is not clearly set up. Use the Float entry to create a new Real input.

Example:
CV4_2025_drs_25_XPpn_01.c4d

For anything Python, I'm sure you have visited the Developer Forum already. (Please note: for security reasons, this forum is strictly code-free, and everything Python is on the specialized forum.)

https://developers.maxon.net/?_gl=1jduutk_gcl_au*MTgxOTY2NjY5My4xNzU0NTg4NjU0

My best wishes

Thanks for the reply, working-long.

I'm glad it works for you.

If I get no other detail or a scene file where I can check the version, I assume the current version is used. I should have asked to get a file, which I usually do, sorry for that. I'm glad I pointed to 2025.3.3.

Enjoy your project.