16-05-2025, 08:10 AM
(This post was last modified: 16-05-2025, 08:14 AM by josemendez.)
Hi!
Concave MeshColliders are hollow: only their surface generates collisions. This means if any object (such as a cloth particle) gets inside or partially inside the collider, it won't be projected back out. What's worse, it will collide with the inner side of the MeshCollider. This makes collision detection of small objects against them quite brittle.
For this reason, Obi includes its own collision primitive for complex shapes: distance fields. They're both more robust and cheaper than MeshColliders, so I'd recommend using them instead.
16 substeps and 16 iterations = 256 iterations (16 iterations per substep, times 16 subteps), which will absolutely obliterate performance. Don't use more than 1 iteration unless needed, always increase the amount of substeps first as recommended in the manual:
Surface collisions are only useful for quite low-resolution cloth, which yours isn't. They won't help in your case.
kind regards,
Concave MeshColliders are hollow: only their surface generates collisions. This means if any object (such as a cloth particle) gets inside or partially inside the collider, it won't be projected back out. What's worse, it will collide with the inner side of the MeshCollider. This makes collision detection of small objects against them quite brittle.
For this reason, Obi includes its own collision primitive for complex shapes: distance fields. They're both more robust and cheaper than MeshColliders, so I'd recommend using them instead.
(14-05-2025, 05:39 PM)Andreia Mendes Wrote: *Add more collision iterations and substeps to the ObiSolver (up to 16 for both, rip my pc)
16 substeps and 16 iterations = 256 iterations (16 iterations per substep, times 16 subteps), which will absolutely obliterate performance. Don't use more than 1 iteration unless needed, always increase the amount of substeps first as recommended in the manual:
Quote:, it's best to start by setting all constraint iterations to 1 and the solver's substeps to a value that yields acceptable quality. Once you're happy with the amount of substeps, you may want to spend a few extra iterations on specific constraint types that could use some extra strength.
(14-05-2025, 05:39 PM)Andreia Mendes Wrote: *Enable surface collisions
Surface collisions are only useful for quite low-resolution cloth, which yours isn't. They won't help in your case.
kind regards,