CINEVERSITY

Hi Tom,

Here is an alternative, I believe that Dynamic and Simulation have their place, but I think a simpler and more controllable solution is better here.

The idea is to have a Spline defined (which you might have already) and use this in a Volume setup.
CV4_2025_drs_25_ANfg_01.c4d

This allows to define and animate the "thickness" of the material while animating a Spline Interface (see image)
Screenshot 2025-01-10 at 10.17.15 AM.jpg

This allows for a very fast animation setup.

An SDF Dilate Erode can be set up for a Global size change to create an even more detailed setup for the animation.

The cube is there as an example that the solution can be defined by a geometry Context (subtract)

Let me know if that works for you.

Cheers

Thanks for the file, KévinH,

The core problem is that you like to have two qualities in one. Having no Stretchiness at all, and then have full.
Please have a look here:
https://stcineversityprod02.blob.core.windows.net/$web/Cineversity_Forum_Support/2023_PROJECTS_DRS/20231019_CV4_2024_drs_23_SIcl_01.c4d.zip

I introduced a lot of Stretchiness and then limited it via a Vertex Tag. This is a quick one; you might explore it more. For this, I have created a Dummy figure to keep the calculation time short. Such a dummy can be set invisible and work for the Simulation while the actual Figure is visible.

As you can see, when you come to the last frame, large stretched polygons take over the head. That could be refined in the Vertex Map, but I left it as is, as it showcases the problem. Polygons can be pulled on, but the local "resolution" lowers, and SDS or Cloth-Surface will not fully remedy this. There are limits, or you can increase the mesh to the point that it will get dense.
As so often, I would use the Simulation to get to a certain point and animate from there.

All the best

Thanks a lot for your reply, AlexC,

My best wishes for the production!

You're very welcome, Maverick-Mongoose.

Thanks a lot for the lovely feedback about the Remi award; since ever I do anything with the people here on the forum in mind when I create. It evidently works to have a great audience :-), and be part of a great team!

I wanted to share one more option:

CV4_2023_drs_23_SIpn_31.c4d

Here I use a "cage" as a proxy/dummy object, which could be even more simplified. With this, any shoe inside the cage (or close to the surface) will stay as it is, how twisted you might go in the future with a model.

My best wishes

Thanks a lot for your input, MaverickMongoose.

Yes, there are always many ways.

My best wishes for your project.

Thanks a lot, Dave.

Ver kind of you.

Cheers!

Hi background-permit,

So far, I know that would be possible with the Point Cache; after the Point Cache has stored the data, the Cloth can be switched off.

https://help.maxon.net/c4d/2023/en-us/Default.htm#html/TCAGEOMCACHE-ID_TAGPROPERTIES.html#ID_CA_GEOMCACHE_TAG_CACHE_LIMIT

All the best

Hi history-growth,

A clean cut is perhaps more challenging than a chaotic tear. I'm not pretending that I have done it with the new Cloth in any production. So, my example follows the parameters and how to supply the information to the system—my best result from last night's exploration.

You are guessing correctly; the path of points and the combination with the Linear field is the key. I explored if more considerable distances or shorter ones 90º to the cut are better.

I find Dynamics/Simulations undoubtedly intriguing but more challenging to art direct. Sometimes I use the results of the dynamic (point cached) to harvest certain states and then use them as "Blend-Shapes" in a Pose Morph. This is a nice balance between the two qualities.

All the best

Thank you, James.

When you look at the reveal tutorial at 02:39, you will see that the selection is lost when the plane moves down. That is precisely what we have as a problem above. The Freeze takes care of that in the same way I have described it above.
While set to grow, it needs a starting point: the Sphere Field in this example.

What a bug or a feature is, I leave that to the developers and support. But let's say it works now as it should. 😉

I understand your concern, given that a larger part of our knowledge is now used to identify useable from sloppy information while searching for proper sources; let me say this: Typically, Noseman put's a lot of effort into it. We are in a team and exchange knowledge, and after that, we also have a QA in place. But things constantly change, and then something like the discussion above is needed. Hence why we connect tutorials with a forum thread so we can answer quickly.

In the Q&A forum, you will see me ~99.5% of the time answering only if I have a project file or if I was able to reproduce it. Answering from memory is, from my point of view, sloppy and blurry. It might be right, but is it working with the current release? It always needs a practical check.

I hope that answers all your questions.

If not, please let me know. If not related to a specific tutorial, please feel free to use the Q&A forum.

Enjoy!