BR,

There is no doubt of the reason those options are options - they are time-consuming techniques that are usually not going to affect the outcome.

However, it's really wrong to assume they're never needed.

Here's what happens in my test case when none of those collision options are checked.

The square has four vertices. None of these ever comes in contact with the box polygons. Therefore it simply falls to the ground.

This is the most common form of poke through - caused when a relatively large cloth polygon passes through one or more small figure polygons that are completely contained within the cloth polygon boundary.

The solution should be to enable "object vertex against cloth polygon" (let's abbreviate this as OVACP.) And sometimes it works, and others not.

I don't have all my ducks in a row, but OVACP does not behave the way I expect. Is it a bug or are my expectations incorrect? That is the first question that needs to be answered, and it leads to many other questions.

If OVACP cannot be trusted, what's the point of tweaking the parameters - you're going to be dealing with poke through perhaps in any case and pushing the parameters to try to stop the poke through will likely make the cloth behave strangely in other ways. Finding out when OVACP fails, and how to deal with it is key in my opinion.

For those who have the option to model, understanding what makes OVACP work or not work is going to be very valuable information. How valuable is personal, and depends on the value one places on a day's work.

For those using a 3rd party mesh, being able to look at it and in a few seconds decide if you are going to able to use it clothified or not is also valuable. Right now, nobody can give any definitive information on this question.

(Related to this is our general knowledge that long, thin polygons will often create artifacts in Poser. We know to model for Poser and that means don't do that.)

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)