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

Hi camera-reply,

Yes, the QT VR gave an option like that, but it was just a series of images with a specific link to a position in the viewer. I bought the Studion Pro version in the late '90s, and I remember it vividly.

When you are familiar with the QT VR Studio, you might remember how to import all the single images and create the VR experience; Cinema 4D later simplified that process for everyone by rendering that sequence. As a result, QT VR had all qualities backed in, and only a specific number of images represented this—no real-time rendering.

Very different is the glTF approach, which is pretty much the common way to get 3D "interactive" into a website :

https://cineversity.maxon.net/en/series/gltf_exporter?tutorial=gltf_exporter

https://cineversity.maxon.net/en/series/exporting_ar_game_ready_models_using_gltf?tutorial=exporting_ar_game_ready_models_using_gltf

The current version of the documentation is here:

https://help.maxon.net/c4d/2025/en-us/Default.htm#html/FGLTFEXPORTER.html?TocPath=Configuration%257CPreferences%257CImport%252FExport%257CglTF%257CglTF%2520Export%2520Settings%257C_____0

Google glTF viewer, or use one of the iPad apps to test if the export works to your specifications.

Enjoy

Hi tie-version,

Please have a look here:
CV4_2025_drs_25_MGem_01.c4d

I created a little gap, inverted it, and used the Thicken generator to create good visibility.
As you mentioned, it is a background object, so the view is from the side rather than the top.

All the best

Thanks for the reply, Tanmir8r.

Yes, my impression is that if two or more conflicting settings collide, things get a little bit more complex to "tame". Since we have no analytic tools for Hair like we have with Simulation to a certain degree, the though below is more an opinion than a fact:

Keeping the beard's shape while colliding and not losing a natural "reaction" to the collision is not an easy task to solve, if at all.
Hence, my suggestion is to lower the value of one influence.

My best wishes for the project

P.S.: Just a little example

CV4_2025_drs_25_PAst_11.c4d
Or with Tracer

CV4_2025_drs_25_PAst_12.c4d

Hi diet-commision,

Please have a look for Displacement and Normal in this file
CV4_2025_drs_25_STbd_01.c4d

While AO can't work for this process, given the flat plane, you can explore this here, baked to the original object, but where would the AO information sit for the "vertical" part in the "A" (see model)?
CV4_2025_drs_25_STbd_02.c4d

I use OpenEXR files in linear and 32bit-float per channel. Baking here is done using the Standard Render Mode!

Please compare the settings you have with the provided files. Will that help? Otherwise, take that as a step one, and I move on with more data from your side until you get what you need as far as possible. Having said that here are a few notes:

AO was a fake to get a sense of Global Illumination way back in time. It responds only to geometry. Even if you place a bright light in a corner of the object, it will show dark AO effects. Global Illumination renders this more naturally, and adding AO to a Global Illumination render is like adding most of those effects twice to the visuals, which might defeat the intention of the whole aesthetic.

I'm strongly biased here (I know ); if we talk about anything towards photorealistic, whatever that might be (realistic, photorealistic, Hyperrealistic, the bandwidth is rather wide. But of course, if your work needs it, then it needs to be calculated after the displacement of the baked object; it can be stored like an XYZ Displacement can.

I would suggest baking to avoid low-level image formats like in the youTube source you shared; thanks for the timeshare, so I do not have to go through this.

I like to help based on project files, which usually give a clear problem, and then, in return, I can hopefully share a working file and, if needed, an explanation. This has proven over more than two decades the best working way. In the end, I would like you to feel savvy about this.

Cheers

Hi hang-single,

To my knowledge, the options are R25 and up.
https://www.maxon.net/en/requirements/redshift-requirements?srsltid=AfmBOopeOaulqhrmPdrk7Abvwp0Ex89LOJNc50RVZ_ZUs-RHLP4n0WZb
or here
https://help.maxon.net/r3d/cinema/en-us/#html/System+Requirements.html?TocPath=_____3

There was a version for R21, but since that was around 6 years ago, I'm not aware if that is available as a new license or if support is given for the current OS.
If it is available, make sure to know what version of Redshift 3D it is.

Please get in touch with Sales:
https://www.maxon.net/en/about-maxon/sales

All the best

You're very welcome, Mark.

My best wishes for your project.

Hi piece-quality,

Thanks for the file and for using Wetransfer.

Here is my "sketch":
https://projectfiles.maxon.net/Cineversity_Forum_Support/2024_PROJECTS_DRS/20250113_CV4_2025_drs_25_PAst_01.c4d.zip

The idea is to create a smaller version of your sculpture. Volume and Dilate Erode should be useful here. The amount needs to be the same size as the resulting volume of "particles" so they create the same surface dimensions.
From there, you can go with two Groups or put both Groups into a MultiGrou.

I introduce a small movement to get away from the shrunk surface and allow the Collider radius to work without making them jump.
So far, that needs a lot of particle and computing power.

I see the biggest problem in finding the balance between Collider radius, and resembling the original surface. I am under the impression that the sculpture melts away.

If that is not the case, create a much smaller inner shape and emit the particles from there, so they are not showing at all, but after the Field has moved over them, they break through the surface.

My best wishes for your exploration

P.S.: Not sure if that helps or just take some time from you, as I ahve not a 100% clear idea about your target, based on the headline.
https://cineversity.maxon.net/en/tutorials/walking_through_fields_using_fields_with_volumes_adding_chocolate_drips

Perfect, thank you, Dutchbrid, for the reply.

My best wishes for the project.

Hi Mark,

This is a Standard Render setup. It is not set up for Redshift, which is my best guess about the problem.

I have set up a redshift solution for the cards. You might set up details and what else you need.
https://projectfiles.maxon.net/Cineversity_Forum_Support/2024_PROJECTS_DRS/20250113_CV4_2025_drs_25_MGcr_21.zip

The 500 high is the limit, but it can be wider.
Please use Dropbox, Wetransfer, Google, Adobe, or Apple cloud services if you need larger images. Thank you. For security reasons, I am sorry to have no other option.

All the best

Thank you, Dutchbird,

Please let me know how that worked for you.

My best wishes

Hi Dutchbird,

I assume that the duplicate materials are all Node-based?

If they are the same, then they have the same name. If so, do this:

Create a backup copy, just in case.

• Create a copy that should replace all, and name that differently
• Select all the ones that have the same name (Magnifying glass)
• Right Mouse click on that selection, "Select material Tags/Objects."
• Go to the Attribute Manager where the Material Tags are now shown
• There is a Tag> Material field, drag the new copy into that field
• Check if all renders are as before
• Delete the unused materials

Is this working for you?

If I had an example file, I might suggest something else.

All the best

You're very welcome, charge-pot!

I'm glad you got what you wanted and created it on your own, meaning that it is something that you can expand for other projects. Perfect.

Thank you for the reply.

All the best