10-09-2018, 03:56 PM
(This post was last modified: 10-09-2018, 04:04 PM by josemendez.)
(10-09-2018, 03:47 PM)arrnav96 Wrote: On testing further, I tried keeping mass of sphere and slime equal, with respect to what you just mentioned.
I've tried keeping both in same phase as well as different phases. I've tried changing thickness of slime. I've tried changing stiffness of the slime. Literally everything is giving the same result - The sphere passes through.
The sphere STILL passes through after bending the slime. I've kept both their masses as "1". Also both use primitive colliders. The slime uses a Box collider for it's plane. The sphere uses a sphere collider.
I've attached the settings in their respective inspectors.
This is getting very confusing. I understand that physics engines have trouble with collision tunneling. But that's with huge mass ratios or very high velocities. I don't understand why such a simple simulation results in the object passing through.
Hi,
Changing the phases will have no effect over how collisions are resolved. It is used to simply filter out collisions with certain objects.
Thickness will simply alter the size of the collider.
None of these settings will change how the cloth behaves in any way.
You're using just 3 distance constraint iterations, and 1 solver substep. Try increasing both of them as I suggested in the previous message : 5 iterations, 2 substeps.
Cloth is made out of small spherical particles sewn together by distance constraints (use a ObiParticleRenderer to see them at runtime). If a relatively object is placed on top of the cloth, the object will displace the particles very easily and open gaps between them, trough which it can slip.
Increasing the amount of iterations or substeps will allow the solver to spend more time calculating in order to make the constraints that keep particles together more strong, so that it will resist heavier loads on top of it. Note that setting the "stiffness" parameter that all constraints have to the maximum will only allow the solver to make them as stiff as possible within the current iteration budget. If the budget is too low, you will have to increase the iteration count to give the solver a chance to reach the desired result.
This is how all game physics engines work, try this experiment in Unity: place a 1000 kg box on top of a 1 kg box, hit play to watch it sink and/or explode. To fix this, go to the physics manager and crank up the amount of solver iterations (the default is 6 which is too low for this scene). See:
https://docs.unity3d.com/Manual/class-Ph...nager.html