Hi Dr. Sassi,
So I tried a test where I deleted all animation, including all morph keys, everything, from the project, and zeroed all morph values. I changed all the cloth settings to your suggestions (expect sub-sampling which it kept at a value of 3). I didn’t add cloth thickness so I could see what triggers the tear. I ran the animation and no cloth tear.
Then I set only one morph value to 50% at frame 0 and set a key. Still no cloth tear.
Then I set the same morph (and only one) to a value of 50.001% at frame 40. Now the cloth now tears.
Then I set the same morph (and only one) to a value of 100% at frame 40. The cloth tears exactly the same as the morph change of .001%.
Then I made the dress have thickness of 1 cm (pretty big). The “thick” cloth tears exactly the same.
Then I set the cloth sub-sampling to the suggested value of 36. The cloth still tears, just not as much.
These tests, to me, rule out keys not being on a frame, and cloth thickness. In addition, even if I have the character move 30 cm in 14 frames, then spin around 180 degrees in only 14 additional frames (which is unrealistically fast) with cloth sub-samples at a value of 3, the cloth still doesn’t tear (and looked pretty cool), so that rules out the sub-samples are the root issue, My conclusion, is the cloth tag doesn’t like morph animation no matter how small or slow. Only using the Point Cache produces the same results as no morph keys, even with sub-sample still at 3.
I can use the Point Cache to move on, but it seems like there either something about my project file or a bug in Cinema 4D R21.207 (that I know can’t be fixed). Having to re-run the cache anytime I edit the animation will kind of suck. It would be interesting to see if the latest version of Cinema 4D does the same.
I think we can call this forum posting as closed. Thanks for the help.
Bruce