Please go to the Collision Tab of the Simulation Tag (Attribute Manager).
Here, the Hierarchy Level needs something other than zero to get there. (I say "something" as I have no idea about your setup.)
Thank you very much for the file and for using DropBox.
Some of these Spheres fall on the zero-dimension edge of the plane. My suggestion would be to create a box as below. Please note that the box does not need to be seen to work. So you can visually present the flat-based box.
When I started learning Cinema 4D 25+ years ago, I found, after a while, the Command Manager. Back then, it was filled with "just" around 1,000 items. I went through that list and read the manuals three times over the years.
When I start a hand on class, I start with; I don't know everything. To ease everyone's mind. It is accurate, and no one knows Cinema 4D 100%. Even this morning, I was reminded of a feature I missed mentioning to a colleague's question.
Why I'm talking about it? Take the 1,000 items, combine those with each other, and get a six to seven-digit number of possibilities. Combine three or more of them, and it explodes in possibilities.
It is impossible to cover the whole application while being aware of all combinations. I think I'm close, but wait for the next update and then ask me again 😉
Which also means, there is lots to explore that no one has every combined.
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.
Thank you, yes Cloth in R25 is a different "engine", hence my hint with 2023-1.
I guess you have tested 2023-1, and the main obstacle is the rendering.
Using Alembic, you could animate everything in 2023-1 and render in R25.
Save your file, select your flag, and go to
Object Manager> Object> Bake as Alembic.
When the file appears in the Object Manager, disable the original Cloth.
Then select the Alembic Flag, and in the
Attribute Manager> Speed and Offset.
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.